Airtable Sync integration: Admin panel

Updated
  • Updated on Sep 2, 2025
  • Published on Sep 2, 2025
  • 3 minute(s) read
Prev Next

Plan availability

Enterprise Scale plans only

Permissions

  • Owners / Creators - In order to create or update synced tables, you’ll need to have creator permissions in the base where you are setting up the sync

  • Admins - Admin permissions are needed to perform any of the backend, admin panel actions required to enable or disable this feature. Certain settings may only be available to “Super admins” for Enterprise Hub customers.

Platforms

Web/Browser, Mac app, Windows app

What is an admin panel sync?

Airtable’s admin panel sync lets admins bring metadata information from an org or org unit into an Airtable base. This can help your admins use the full power of Airtable and Omni AI to operationalize and automate the various workflows it takes to manage an organization’s Airtable instance at scale.

Enabling or disabling admin panel syncing in admin panel

Note

You will need admin permissions to adjust the setting to allow admin panel syncs in your org’s bases.

  1. Navigate to https://airtable.com/admin.

  2. Click the Settings tab.

  3. Click the Integrations & development tab.

  4. Scroll down to the “Block admin panel sync” setting.

  5. Click the > symbol to the right of the setting.

  6. If your organization uses the Enterprise Hub feature, then you will be able to toggle “On” or “Off” access to any individual units’ ability to sync admin panel metadata.

Adding an admin panel sync to an Airtable base

  1. Navigate to the base where you want to create the admin panel sync or create a new base.

  2. Click the + symbol next to your list of tables.

  3. Then, under “Add from other sources,” click the XX more sources… option.

  4. From the window that appears, select Airtable admin panel.

  5. The next portion of the setup process will depend on whether your organization uses the Enterprise Hub feature:

    1. Enterprise Hub - Click the drop down menu to select the individual “Org unit” you want to sync into the base.

    2. Non-hub enterprises - No dropdown will appear and you can move onto step 6.

  6. Click Create tables.

Note

Larger organizations or org units may take a few moments to initially sync since there are multiple tables and large sets of metadata to sync into the base you are creating.

Understanding admin panel synced tables

After setting up and creating the tables that are synced to your admin panel instance, multiple tables will be created. You’ll find more about what each subsequent table contains below:

  1. Users

  2. Groups

  3. Workspaces

  4. Bases

  5. Interfaces

  6. Org units (Will only appear when your organization uses Enterprise Hub and the admin panel org unit selected in step 5 above is the “Root” org)

“Users” table fields

  1. User ID

  2. First Name

  3. Last Name

  4. Email

  5. Source URL

    1. A link to the individual user detail page in admin panel. Admin permissions are needed to access these pages.

  6. Seat Type

  7. Seat Upgraded

    1. Date and time

  8. Seat Upgrade Event

  9. Status

  10. Account Type

  11. Admin

    1. Check means “Yes” the user has admin permissions

  12. Last Active

  13. Email Verified

    1. Check means the user’s email is verified

  14. SSO Required

  15. Two Factor Auth Enabled

  16. Joined - Date and time

  17. Claiming Org Unit IDs

    1. Enterprise Hub only and each org unit the user belongs to is separated by a comma.

  18. Cost Center (SCIM)

  19. Department (SCIM)

  20. Division (SCIM)

  21. External ID (SCIM)

  22. Organization (SCIM)

  23. Title (SCIM)

  24. Manager Display Name (SCIM)

  25. Manager Value (SCIM)

  26. Org Units (Via Admin User IDs)

  27. Groups

  28. Workspaces (via Owner User IDs)

  29. Workspaces (via Collaborator User IDs)

  30. Bases (via Collaborator User IDs)

  31. Interfaces (via Collaborator User IDs)

  32. Interfaces (via Portal Collaborator User IDs)

“Groups” table fields

  1. Group ID

  2. Name

  3. Created

    1. Date and time

  4. Org Unit ID

  5. Member User IDs

  6. Member count

  7. Source URL

  8. Seat type

  9. Seat type updated

    1. Date and time

  10. Workspaces (via Collaborator User IDs)

  11. Bases (via Collaborator User IDs)

  12. Interfaces (via Collaborator User IDs)

“Workspaces” table fields

  1. Workspace ID

  2. Name

  3. System

    1. A "system" workspace is one that is managed by Airtable. We use this to show where the enterprise managed apps / components library feature is leveraged.

  4. Org Unit IDs

  5. Owner User IDs

  6. Collaborator User IDs

  7. Collaborator Group IDs

  8. Created

    1. Date and time

  9. Source URL

  10. Bases

“Bases” table fields

  1. Base ID

  2. Workspace ID

  3. Name

  4. Created

    1. Date and time

  5. Row Count

  6. Sandbox

  7. Source URL

  8. Collaborator User IDs

  9. Collaborator Group IDs

  10. Interfaces

“Interfaces” table fields

  1. Interface ID

  2. Base ID

  3. Name

  4. Created

    1. Date and time

  5. Source URL

  6. Portal Collaborator User IDs

  7. Collaborator User IDs

  8. Collaborator Group IDs

“Enterprise Org Units” (Enterprise Hub only)

  1. Org Unit ID

  2. Name

  3. Default

  4. Admin User IDs

  5. Created

    1. Date and time

  6. Source URL

  7. Groups

  8. Workspaces

Limitations and considerations

  • One-way syncing only - You cannot make edits from the Airtable base. Any edits will need to be made by users with admin permissions within your organization’s admin panel.

  • If an admin turns off the ability to sync admin panel metadata from the “Settings” page, then any existing syncs will stop syncing with an error.

    • New syncs will be prevented from being created.

    • We will NOT delete any previously configured tables.