Airtable

The Corma and Airtable integration keeps Airtable collaborators and owners under control as bases spread across teams. Airtable describes itself as the digital operations platform: one relational source of truth for every app, agent and workflow. In Airtable, billing follows permission levels rather than headcount, and access grows base by base, so the bill and the list of who sees what drift quickly.

Key takeaways

• On the Airtable Team plan, collaborators with Commenter permission or higher are billed; on the self-serve Business plan, Editor or higher; read-only collaborators are included.
• Removing a billable Airtable collaborator mid-cycle does not reduce the current invoice, but that seat is not billed at the next renewal.
• When an Airtable owner's account is deactivated, the external or integrated automations they own fail and the synced tables they created stop updating.
• Airtable SSO and SCIM provisioning are available on the Business and Enterprise Scale plans only.

Why does the Airtable bill follow permissions?

A billable Airtable license depends on a user's highest permission level across bases, interfaces and workspaces. Airtable's plans overview sets the threshold at Commenter on Team and at Editor on Business, with read-only collaborators included. A single Editor invitation to one base can therefore add a paid seat, and removing it mid-cycle only pays off at the next renewal.

Ownership is the other risk. A personal access token acts as the account of the user who created it, and when an owner is deactivated, their external or integrated automations fail and their synced tables stop updating. A workspace owner can only be deactivated if another owner exists or no other collaborators remain. On Enterprise Scale, service accounts let integrations run independently of any one user.

How Corma governs Airtable

• Billable seats in view: Corma shows who holds Airtable access and flags inactive users, so paid seats are questioned before renewal, one of the quickest wins in SaaS spend optimization.
• Ownership handed over first: a leaver workflow in the IT workflow builder asks the manager to approve a new workspace owner, and the rebuild of any external automations, before the departing owner's account is deactivated.
• Access on request: employees ask for Airtable in the self-service app store, and a manager approves before an account is created.
• Tokens checked at departure: the same workflow can add an approval step to move integrations off a leaver's personal access tokens, to a service account on Enterprise Scale or to a colleague's token. Read more on non-human identity security.

Frequently asked questions

Does Airtable support SSO and SCIM?

Yes, on the Business and Enterprise Scale plans. Airtable SSO uses SAML 2.0, with setup guides for Okta, Google, OneLogin, Microsoft Entra ID and ADFS. Airtable's IdP sync article names SCIM integrations with Okta and Entra ID, although its admin panel FAQ mentions SCIM deactivation for Okta only. Provisioning user groups is not available on Business. Learn how user provisioning works.

How does Corma connect to Airtable?

Through Airtable's APIs where your plan allows it, the Enterprise API being reserved for Enterprise Scale, or through Corma's browser-based agents, which work in the Airtable interface like an admin. Corma governs other collaborative workspaces the same way, such as Notion.

Where is Corma data hosted?

Corma runs on AWS, with web servers and databases in data centers inside the European Union. Data is encrypted in transit and at rest, and Corma is ISO/IEC 27001:2022 certified.

Want to see which Airtable collaborators you actually pay for? Book a Corma demo.