What is SCIM? SCIM, the System for Cross-domain Identity Management, is a standard API that lets your identity provider create, update and remove user accounts in your other tools automatically. Add someone to Okta or Microsoft Entra ID and SCIM creates their Slack and GitHub accounts; remove them and SCIM deactivates those accounts. It is the part of identity management that SSO leaves out.
The current version, SCIM 2.0, was published by the IETF in September 2015 as two documents: RFC 7643, the core schema, and RFC 7644, the protocol. It is widely supported, and widely kept on expensive plans.
SCIM in one paragraph
Each tool that supports SCIM exposes the same kind of API: a list of users, a list of groups, and standard ways to add, change and deactivate them. Your identity provider is configured with that API's address and a token. Whenever something changes in the identity provider (a new hire, a new team, a departure), it sends the change to every connected tool. Nobody opens an admin page.
When people say "SCIM" they nearly always mean SCIM 2.0. Older 1.x versions exist, but the identity providers and tools a small company meets today speak 2.0.
What it automates: create, update, deactivate
SCIM handles the account lifecycle, in three moves.
Create. A new person in the identity provider, assigned to the tool, gets an account in it before their first login, with their name and email filled in. Nobody waits on day one for an invite.
Update. A name change, a new manager, a move to another team: the attributes and group memberships follow. The standard has a ready-made set of work fields for this. RFC 7643 defines an "enterprise user" extension with an employee number, cost center, organization, division, department and manager, so a tool can know who reports to whom without anyone typing it in.
Deactivate. When someone is removed or suspended in the identity provider, their account in the tool is deactivated or deleted. This is the part people buy SCIM for.
It can also sync groups, so "Engineering" in your identity provider becomes a team or group in the tool, and membership stays in step.
How it works: the identity provider calls the tool's API
Under the hood SCIM is a plain REST API with JSON, and the identity provider is the one calling it. Setup runs in a fixed order.
First, you enable SCIM in the tool, usually on its admin security page, and it gives you a base URL and a bearer token. Next, you paste both into your identity provider, in that tool's provisioning settings. Then you map attributes: which field in the identity provider becomes the username, the email, the display name. Last, you assign people or groups to the tool in the identity provider, and it starts pushing changes.
The calls themselves are ordinary web requests. RFC 7644 defines /Users and /Groups endpoints, plus a few the identity provider reads to learn what the tool supports, such as /ServiceProviderConfig, /ResourceTypes and /Schemas. A POST to /Users creates someone. A PATCH changes part of their record. A PUT replaces the whole record, and a DELETE removes it.
Deactivation is usually not a delete. RFC 7643 gives every user an active attribute, a true-or-false flag for whether the account is in good standing, and leaves its exact meaning to the tool; the usual reading is that false means suspended. Microsoft's description of how Entra provisioning works, as we read it on 27 October 2026, says the same thing in practice: for SCIM apps, disabling a user is a request to set active to false. That matters for offboarding. A deactivated account keeps its files and history, and whether it still costs a seat is up to each tool's billing.
The tool never calls back; it just accepts changes. SCIM provisioning goes through setup, groups, failure modes and cost in more detail.
SCIM vs SSO
They are often sold together and often confused, but they do different jobs:
| SSO (SAML or OIDC) | SCIM | |
|---|---|---|
| Job | Logs people in | Creates, updates and removes accounts |
| When it acts | At the moment of login | Whenever something changes in the directory |
| Direction | The person's browser carries a message | The identity provider calls the tool's API |
| Removes leavers | No; it stops new logins only | Yes; it deactivates the account |
With SSO but no SCIM, a leaver cannot start a new login, but their account stays in every tool, holding a paid seat, until someone removes it by hand. With SCIM but no SSO, accounts are managed automatically but people still log in with each tool's own password. Most companies that can afford both use both. What SSO is covers the login side, and SCIM vs SAML walks through what each one leaves behind when someone leaves.
So do you need SCIM if you have SSO? If you want leavers removed from tools automatically, yes. SSO alone turns off the front door and leaves the room furnished.
Which tools support it, and on which plans
Support for SCIM is common. Support on a plan a small company would buy is not. From each tool's own help pages, read on 27 October 2026:
| Tool | SCIM is available on | Also required |
|---|---|---|
| Slack | Business+ and Enterprise | An identity provider that supports it |
| GitHub | Enterprise Cloud | SAML SSO for the organization |
| Figma | Organization and Enterprise (and Education, Government) | SAML SSO set up first |
| Zoom | Business, Education and Enterprise accounts | SSO, an approved vanity URL, a verified domain |
| Notion | Enterprise only | Business has SAML, but not SCIM |
| Jira, Confluence | Through Atlassian Guard Standard, an add-on | Guard is billed per user |
| Intercom | "Certain plans", per its help center | SAML SSO set up and enabled |
Two patterns stand out. SCIM is almost never on a cheaper plan than SSO, and it is sometimes on a more expensive one: Notion puts SAML on Business and SCIM only on Enterprise (Notion SSO has the detail). And most tools require SAML SSO to be running before they will accept SCIM, so you pay for both even if you only wanted the removals.
The identity provider has to support SCIM too. Okta includes provisioning (Lifecycle Management) from its Essentials suite at $17 per user a month, and sells it as an add-on on Starter (Okta pricing). Google Workspace can provision users into a list of supported apps, up to 3 apps on Business Starter and up to 100 on Business Standard and above, but it needs Google set up as the SSO identity provider for each app.
What SCIM does not standardize
SCIM is good at the question "should this person have an account?" It is much weaker at "what should they be able to do in it?"
The reason is in the standard itself. RFC 7643 gives users roles and entitlements attributes, but defines no vocabulary for either. A role is a free-text label, and each tool decides what it means, or ignores it. So "admin in Slack, editor in Figma, read-only in the CRM" is not something you can say once in SCIM and have every tool understand. In practice, many tools take group memberships through SCIM and leave admin rights and seat types to be set by hand.
The second gap is history. SCIM manages the accounts it created or matched. Accounts someone made by hand before you connected the identity provider, a contractor invited with a personal email, a shared login for a social account: none of those are in the identity provider, so SCIM never touches them. Turning SCIM on is the moment to find them, not proof that they are gone.
And SCIM only works where it is switched on. Every tool on a plan without it, and every tool that does not support it at all, stays manual. For most small companies that is the longer list.
Is SCIM free?
The standard is free; anyone can read the RFCs and build an endpoint. Using it rarely is. You need an identity provider that pushes SCIM, often on a higher tier, and each tool's SCIM is usually on its Business or Enterprise plan, which you pay for on every seat.
Here is what that looks like for a 15-person company that wants automatic removals from Slack, GitHub and Notion. Slack needs Business+ for everyone. GitHub needs Enterprise Cloud with SAML SSO. Notion needs Enterprise, which has no public price. And the identity provider needs a provisioning tier on top. The protocol costs nothing; the plans around it are the bill. SCIM provisioning prices a 20-person version of this.
Without SCIM: the options
If your identity provider or your tools' plans do not include SCIM, you still have to create and remove accounts somehow.
By hand, from a checklist. Free, slow, and dependent on someone remembering every tool. Our employee offboarding checklist makes it more reliable, and user provisioning covers the joiner side.
Just-in-time provisioning through SSO creates accounts on first login. It still needs SSO, and it never removes anyone; just-in-time provisioning explains where it helps.
Scripts against each tool's API work for a few tools with good APIs, until the person who wrote them leaves.
A tool that does the admin work for you is the last option. Automated user provisioning without SCIM compares the approaches, and SmashSSO is one of them, below.
Whichever you pick, the removal side is the one that bites. What deprovisioning is covers what "removed" should actually mean.
Where SmashSSO fits
SmashSSO does the job SCIM does, without SCIM. It reads your people from Google Workspace with read-only access, finds who has an account in each tool and with what role, and flags accounts that match nobody. Access bundles by role invite people to every tool in the bundle; role changes and removals run the same way. Where a tool has a member API, you can add a token and it uses that; for everything else, an agent does the change in your own Chrome, in tabs where you are already signed in as an admin, on the plan you already have.
The trade-offs are real: agent-run changes need that browser open, they are slower than an API and can fail when a tool redesigns its screens (a failed run says so and shows its last screenshot), and some tools' terms restrict automated use. Steps that would add a paid seat pause for approval. It is not SSO. It costs a flat fee from $199 a month billed annually, with no tool upgrades (pricing). The security page explains how it works in your browser.