Enablement paths in Enterprise Hub

  • Updated on Apr 30, 2025
  • Published on Apr 25, 2025
  • 4 minute(s) read
Prev Next

Plan availability

Enterprise Scale plans

Permissions

Super admins can/have:

  • Configure SSO and SCIM for their org.

  • Full visibility and admin rights over users and workspaces in the organization.

  • Visibility into on-domain users and any external user collaborating on an org-owned workspace, base, or interface.

  • Control Airtable licenses.

  • Ability to create new org units or grant super admin access, new org units through the admin panel that inherit the organization's default security policies.

  • Ability to configure SSO, SCIM, and domains.

  • Power to establish security policies that apply to all org units, by default. Rules for APIs and compliance tools such as EKM, DLP, and audit logs apply to the entire organization.

Org-unit admins have:

  • Visibility into specific org units where they are an admin.

  • Administrative rights for workspaces and user permissions on their org units.

  • Visibility into all org unit members, and any on-domain user or external user collaborating on an org unit-owned workspace, base, or interface.

  • Ability to grant org unit admin access.

User admins have:

  • Administrative rights over users.

  • Ability to manage groups and their memberships.

  • Ability to manage workspace, base and interface collaborations

Platform(s)

Web/Browser, Mac app, and Windows app

Related reading

This article is part 2 of 4 of the Enterprise Hub overview series. The following enablement paths outline simple scenarios. For more complex scenarios or customers who want consulting support for best practices, Airtable also offers a service package to help plan and carry out the steps. Please connect with your account manager or customer success manager.

Centralize multiple organizations into an Enterprise Hub with multiple org units

Note

  • Enterprise Hub requires all organizations to enable domain capture. Once enabled, all users with verified emails that match their orgs' email domains will become org members.

  • Admins need admin access to all relevant organization accounts for centralization to ensure you have the correct authorization and to access those account IDs. Check out our Finding Airtable IDs article to learn how to locate and confirm your account IDs.

Choose this option when your company currently has multiple Airtable orgs and wants to consolidate them into a single Enterprise Hub with multiple org units:

  • Organization A

  • Organization B

  • Organization C

Enablement steps:

  1. Identify an existing organization or create a new account to become your hub.

    1. Select an org with the most appropriate enterprise settings as the default option for the other organizations—other organizations will become the new org units and retain their enterprise settings.

    2. Settings and integrations: Make a plan for the new hub settings.

    3. Relevant IDs:

      1. The remaining enterpriseAccountIds of the desired org units.

      2. User emails of collabarators should become super admins.

  2. Schedule a date to enable Enterprise Hub for your accounts.

    1. Contact your account manager with your plan and preferred meeting timeframe.

  3. Airtable will enable Enterprise Hub after selecting a date based on the information and your specified future date.

    1. Confirm with your account manager about the exact date and timing.

To consolidate multiple orgs into a single Enterprise Hub with multiple org units:

  1. Review your existing settings to decide what to preserve at the hub level. Keep in mind that your “Security and Compliance” settings live under 1 account ID in your hub.

    1. For example, you picked “Organization A” as the hub. In that case, “Organization B” and “Organization C” no longer have their own “Security and Compliance” settings and instead reuse those configured at “Organization A.”

    2. Suppose you created a new organization—"Organization D". In that case, "Organizations A, B, and C" no longer have their own "Security and Compliance" settings and are configured from "Organization D."

  2. "Sharing & Data," "Integrations & Development," "AI Settings," and "Org Resources" are settings retained in all existing organization accounts.

    1. The super admin may later change them to "Use default setting" and defer to the hub setting.

  3. If you have existing API integrations like Get enterprise, update those API integrations to reference the appropriate enterpriseAccountId.

    1. If you select an existing organization account as the Hub, those API integrations should switch to using its account ID.

Update a single organization into an Enterprise Hub with a default org unit

Note

Enterprise Hub requires all organizations to enable domain capture. Once enabled, all users with verified emails that match their orgs' email domains will become org members.

Choose this option when your company currently uses a single organization but would like to set it up to manage multiple organizational units. Enablement steps:

  1. Identify an existing organization or create a new account to become your hub.

    1. Select an org with the most appropriate enterprise settings as the default option for the other organizations—other organizations will become the new org units and retain their enterprise settings.

    2. Settings and integrations: Make a plan for the new hub settings.

    3. Relevant IDs:

      1. The remaining enterpriseAccountIds of the desired org units.

      2. User emails of collabarators should become super admins.

  2. Schedule a date to enable Enterprise Hub for your accounts.

    1. Contact your account manager with your plan and preferred meeting timeframe.

  3. Airtable will enable Enterprise Hub after selecting a date based on the information and your specified future date.

    1. Confirm with your account manager about the exact date and timing.

Note

Check out our Configuring Enterprise Hub article to continue to the 3rd part Enterprise Hub overview series.