Airtable SSO (SAML single sign-on) is only on the Business and Enterprise Scale plans; Team doesn't have it. Business is $45 per seat a month billed annually, against $20 for Team, so SSO costs $25 more per paying collaborator a month: $6,000 a year if 20 of your people edit in Airtable.
Those prices are from Airtable's pricing page as we read it on 27 October 2026. The phrase that matters is "paying collaborator": Airtable only bills people who can edit, so the real cost depends on how your team uses it. Below are the plans, the sums, what else Business includes, how Airtable decides who is billable, and how to remove people without SSO.
Airtable plans and SSO
| Plan | Billed annually, per seat a month | Billed monthly, per seat a month | SAML SSO | Admin panel |
|---|---|---|---|---|
| Free | $0, up to 5 editors | $0 | No | No |
| Team | $20 | $24 | No | No |
| Business | $45 | $54 | Yes | Yes |
| Enterprise Scale | Contact sales | Contact sales | Yes | Yes |
Airtable's support article on configuring SSO confirms SAML is "available on Business and Enterprise Scale plans only".
To set it up you need permission to manage SSO and a verified domain your organization owns. In the admin panel, go to Settings, Security & compliance, Email domains and SSO configuration, choose Set up SSO for your domain, and enter your identity provider's sign-in URL, certificate and email attribute. Airtable gives steps for Okta, Google, OneLogin, Microsoft Entra ID and ADFS.
SSO starts as optional. When you switch it to required, everyone on the domain is signed out at once and must come back through your identity provider; email-and-password sign-in stops working for them. Airtable recommends testing first. Fair warning.
What else Business gets you
The Business card lists "SAML-based single sign-on" and "Admin panel", along with higher record and automation limits, two-way sync, verified data and App Sandbox. The admin panel is the part people underrate: it is where SSO is configured, under its own Security & compliance settings, and Team has no equivalent.
If your bases are hitting Team's record or automation limits, or you want two-way sync between bases, Business is a capacity upgrade and SSO comes along. If Team's limits are fine and the login is the only reason, it is a tax: more than double the bill for a sign-in option. The SSO tax calculator shows how it stacks up against your other tools.
What about SCIM?
Automatic provisioning, where your identity provider creates and removes Airtable users, is murkier. Airtable's IdP sync article lists "Business and Enterprise Scale plans only", then says "SCIM is only available for ELA & CLAIM enterprises" (terms that page doesn't explain), and that "Provisioning user groups is unavailable for Business plans." We read that as: don't count on SCIM on a self-serve Business plan. Ask Airtable before you buy for it.
Where it does exist, it does the job well. As we read the article on 27 October 2026, Airtable is "starting with Okta and Microsoft's Entra ID". Deactivating someone's Airtable access in Okta deactivates them in Airtable, logs out their sessions and greys them out in sharing dialogs; Entra ID does the same, and Airtable says deactivated users aren't charged. Permanently deleting an account is still a manual step, after transferring any bases or workspaces it owns. Our post on SCIM provisioning explains why vendors keep this behind their top tier.
The price jump
From the calculator's figures, for 20 billable collaborators:
| Tool | Plan without SSO | Cheapest plan with SSO | Extra a year, 20 people |
|---|---|---|---|
| Airtable | Team · $20 a seat | Business · $45 a seat | $6,000 |
| Total SSO tax a year | $6,000 | ||
At 10, 20 and 50 billable collaborators:
| Billable collaborators | Team, a year | Business, a year | Extra for SSO, annual billing | Extra for SSO, monthly billing |
|---|---|---|---|---|
| 10 | $2,400 | $5,400 | $3,000 | $3,600 |
| 20 | $4,800 | $10,800 | $6,000 | $7,200 |
| 50 | $12,000 | $27,000 | $15,000 | $18,000 |
The sums: annual billing, $45 minus $20 is $25 a seat a month, $300 a year. Monthly billing, $54 minus $24 is $30 a month, $360 a year. Twenty billable collaborators on annual billing: 20 × $300 = $6,000.
More than doubling a bill for a login option is a classic SSO tax. There is one wrinkle in Airtable's favor, covered next: on Business, commenters stop being billable, which can shrink the seat count.
Collaborators vs seats
Airtable doesn't sell seats in advance. It counts collaborators by their permission level, at the workspace, base and interface level. From its billing article:
| Permission | Team | Business |
|---|---|---|
| Owner | Billable | Billable |
| Creator | Billable | Billable |
| Editor | Billable | Billable |
| Commenter | Billable | Free |
| Read-only | Free | Free |
The pricing page puts it in one line: "No charges will apply on a Team or Business plan for read-only collaborators, form submissions, or share links."
Two things follow. First, a person can be billable where you're not looking. Someone read-only on the workspace but an Editor on one base is billable, so check bases and interfaces, not just the workspace list. Second, on Team, commenters cost the full price. Airtable's own advice is to make people Read-only if they don't need to comment. If half your users only comment, the Business price applies to fewer of them, so do the count before trusting any per-seat comparison.
Added collaborators are charged pro rata: Airtable bills only for the part of the period after they were added.
A worked example
Take a 20-person company where 6 people build and edit bases, 6 only leave comments, and 8 only look. On Team, the commenters are billable, so 12 people pay: 12 × $20 × 12 = $2,880 a year. On Business, commenters are free, so only the 6 editors pay: 6 × $45 × 12 = $3,240 a year. The SSO upgrade costs $360 a year in that company, not the $6,000 the headline sum suggests.
Now take the same 20 people where 16 edit and only 4 look. Team bills 16 people, $3,840 a year; Business bills the same 16, $8,640 a year; the upgrade costs $4,800. Same headcount, more than thirteen times the SSO tax. The permission mix, not the number of people, decides what Business costs you.
The login controls Team has, and doesn't
This is where Airtable is stingier than most. Its two-factor authentication article, as we read it on 27 October 2026, makes 2FA available to individuals on "All plan types", but its FAQ limits enforcing 2FA to enterprise accounts that use SSO. In plain terms: on Team, each person can turn on 2FA for their own account, and you can ask them to, but you can't require it. And because SSO is a Business feature, there is no way on Team to force people through Google either.
The practical answer on Team is to ask everyone to sign up with their company Google Workspace address and to make 2FA mandatory at the Google end. Our post on SSO vs MFA explains why that covers more of the risk than it sounds.
Removing collaborators
Without SSO, a workspace owner removes billable collaborators one workspace at a time. Open your Airtable account overview and, in Workspace settings, select the workspace. Click Collaborators (or Billable collaborators), then Add or manage workspace collaborators. Under People with access, click >, tick the people to remove, and click Remove collaborator.
Repeat that for every workspace they're in. Someone with workspace-level access can't be removed from a single base; take them off the workspace. Access granted directly on a base or an interface has to be removed there.
On billing, Airtable is clear: removing someone partway through a cycle doesn't lower the current invoice. The seat stays available until the cycle ends, and the next invoice counts only active billable collaborators. If someone just needs to look, lowering them to Read-only before the cycle ends does the same for the bill and keeps their access.
A leaver usually leaves more behind than a seat. Bases they own need a new owner before they go, and only workspace owners can manage owners and billing. Personal access tokens and automations they set up may stop working, or keep running under their name. Shared view links and forms they published stay live until someone turns them off. Contractors are the classic case: a freelancer made Editor on one base for a data clean-up is billable on that base until someone notices, and our guide to contractor access management covers how to keep that from happening. Our employee offboarding checklist has the rest.
Alternatives
If SSO is the only reason to move to Business, four habits on Team get you most of the outcome.
Stay on Team and keep the billable list short. Read-only for viewers, Editor only for people who change data. Review collaborators every quarter. Airtable's per-base permissions make drift easy, so a user access review earns its time here. Check the whole seat bill across tools. Our post on SaaS license management covers the habit of paying only for seats in use. Automate the adding and removing, so leavers don't sit as billable Editors for months.
Where SmashSSO fits
SmashSSO manages Airtable collaborators from the same place as your other tools, on Team. It reads your people from Google Workspace, reads who is a collaborator in your Airtable workspaces and with what permission, and matches them by email; anyone who matches nobody in your directory, like a contractor who's gone, gets flagged. When someone is suspended in Google Workspace, SmashSSO alerts you and lists Airtable among the tools they're still in. An access bundle can give a new "Ops" hire Editor access and everyone else Read-only.
Changes run through an agent in your own Chrome, in a tab where you're signed in to Airtable as a workspace owner. The browser has to be open; runs are slower than an API and can fail if Airtable changes its screens, and a failed run says so and shows its last screenshot. Making someone billable pauses for your approval first, and every change goes into the audit log.
It is not SSO. If a contract requires your team to sign in to Airtable through an identity provider, you need Business. If you need people added with the right permission and removed when they go, SmashSSO does that for a flat fee from $199 a month, billed annually, for your whole company (pricing).