Skip to main content
This is the for the Airtable Provisioning connector identified by the app id airtable_ics. It covers full user lifecycle management (create, activate, deactivate, delete) plus group membership and base and workspace access provisioning. For the standard read-and-deprovision connector, see Airtable (Legacy).

​
After this article

You’ll be able to connect Airtable to Lumos to sync users and groups, provision and deprovision user accounts, and manage group membership and base and workspace role assignments.

​
Capabilities

Groups, bases, workspaces, and permission levels appear in Lumos under the same names Airtable shows in its own UI.

​
Required plan and roles

  • Airtable account: the integration connects to an Airtable Enterprise account. You need your Enterprise Account ID to set it up.
  • Scopes: the connection uses Airtable enterprise API scopes.
    • enterprise.scim.usersAndGroups:manage: add, update, or remove users and groups, and manage attributes associated with users and groups
    • enterprise.user:read: view user profiles, email addresses, and associated metadata
    • enterprise.user:write: update user profiles, roles, or other attributes
    • enterprise.account:read, schema.bases:read, and workspacesAndBases:read: list workspaces and bases and read their names, so they appear under their real names in Lumos

​
Read-only access vs provisioning

Is read-only possible? No. This connector authorizes with the same Airtable enterprise OAuth scopes as the standard Airtable connector, including enterprise.scim.usersAndGroups:manage and enterprise.user:write, and no narrower read-only scope set is documented for it. What full provisioning requires. Your Airtable Enterprise Account ID and OAuth authorization of enterprise.scim.usersAndGroups:manage, enterprise.user:read, enterprise.user:write, enterprise.account:read, schema.bases:read, and workspacesAndBases:read. Follow the steps below. This covers full user lifecycle (create, activate, deactivate, delete), group membership assignment, and base and workspace role assignment and unassignment. Watch out for. Delete can’t remove the admin who owns the connection’s token, and it can’t remove the sole owner of a workspace that still has other collaborators (Airtable returns a 422 in both cases). If you only need read access plus basic deprovisioning, the standard Airtable connector is a separate, narrower connection, not a setting on this one.

​
Instructions

Phase 1: Find your Enterprise Account ID in Airtable
  1. Locate your Airtable Enterprise Account ID (available to Airtable enterprise admins in the Airtable admin panel).
Phase 2: Connect in Lumos
  1. Find the Airtable card in your Lumos integrations (reconnect an existing card or add a new one).
  2. Enter your Enterprise Account ID.
  3. Click Connect.
  4. Follow the instructions in the pop-up that appears to authorize the scopes and finish connecting.
If you connected Airtable before September 2026, reconnect the card once and approve the scopes again. Lumos now requests enterprise.account:read, schema.bases:read, and workspacesAndBases:read, and an existing connection doesn’t have them until it is reauthorized.

​
API Endpoints Used

​
Troubleshooting

Connection fails after entering the Enterprise Account ID. Verify the ID belongs to the enterprise account you administer and that the authorizing user is an Airtable enterprise admin able to grant the enterprise.* scopes. Bases and workspaces show generic names, or the sync reports a missing scope. The connection was authorized before Lumos began requesting enterprise.account:read, schema.bases:read, and workspacesAndBases:read. Reconnect the Airtable card and approve all requested scopes. Provisioning or deprovisioning actions fail with permission errors. Confirm the enterprise.scim.usersAndGroups:manage scope was granted during the OAuth authorization. Re-run the connection pop-up if scopes were declined.