Airtable SSO and SCIM Provisioning configuration

If you're rolling out Airtable SSO + SCIM, I'd sanity check 4 things before you turn it on for everyone:

• make sure the IdP email / unique identifier matches your existing Airtable users exactly, otherwise SCIM can create duplicate identities
• start with a small pilot group in a test workspace before enforcing SSO org-wide
• test the full lifecycle, first login, existing-user conversion, and offboarding / deprovisioning, because offboarding is usually where the surprises show up
• double check what SCIM is allowed to update for your users so profile fields, groups, and seat assignment behave the way you expect

I'd also keep JIT and SCIM behavior straight during the pilot so you can see whether new users are being provisioned the way you expect vs. just authenticating successfully.

If you share the IdP you're using, Okta, Entra, Google, etc., it's easier to call out the exact gotchas.

Thank you for your answer.

We are using EntraID in our case and the users are created with the same IdP 😉