SCIM provisioning connects your identity provider to each of your tools so that accounts are created, updated and deactivated automatically, following your directory. Assign someone to Slack in Okta or Microsoft Entra ID, and the identity provider calls Slack's SCIM API to create their account; remove them, and it calls again to deactivate it.
Setting it up per tool takes about fifteen minutes once you have the right plans. Getting the right plans is where the cost is. This post covers both, plus what goes wrong after setup.
What SCIM provisioning does
It keeps each tool's member list in step with your directory, at all three points of a person's time with you.
Joiners. People assigned to a tool in the identity provider get an account before their first day, with name and email filled in. Movers. Changes to names, departments or group memberships flow through; if groups are synced, moving someone from "Sales" to "Support" changes their teams in every connected tool. Leavers. Removing or suspending someone deactivates their account in every connected tool. In many tools a deactivated account stops counting as a paid seat.
It does not log anyone in; that is SSO's job. What SCIM is explains the standard itself, and SCIM vs SAML explains why login and provisioning are sold separately. For the wider picture of logins, identity providers and protocols, start at what SSO is.
Setting it up: endpoint, token, attribute mapping
The steps are similar in every identity provider and every tool.
Turn on SCIM in the tool. It usually sits under Security, Authentication or Identity in the admin settings, and some tools require SSO to be set up first. Copy the SCIM base URL and generate an API token. The token is a bearer token with admin rights over users, so treat it like a password. Add the tool in your identity provider, usually from its app catalog, and paste the URL and token into its Provisioning section. Most identity providers have a test button; use it.
Map attributes. At minimum: username, email, first and last name, active status. Check what the tool uses as the unique key. If it is email, a person's email change can create a duplicate. Microsoft's guide to how Entra provisioning works, as we read it on 27 October 2026, calls this the matching attribute and tells admins to review it before starting.
Choose what to push. Create users, update attributes, deactivate users, push groups. Turn deactivation on; it is the point. Then assign people or groups, and test with one person before assigning everyone.
Existing accounts in the tool that were created by hand need matching to the identity provider's users, usually by email. Accounts that match nobody are left alone, which is how ex-contractors survive a SCIM rollout.
What happens on each sync
It helps to know what the identity provider is actually doing, because the timing surprises people. Microsoft's guide describes Entra's version plainly, and the others work along similar lines.
The first run reads everyone. The provisioning service pulls every user and group in scope, looks for a matching account in the tool, creates the ones that are missing and updates the ones it finds. After that it runs in cycles, picking up only what changed since the last one. Entra's interval depends on the app, set in each app's tutorial.
A leaver is usually disabled, not deleted. When someone is unassigned, falls out of scope or is disabled in Entra, the service sends the tool an update. For SCIM apps, Microsoft says, a disable is a request to set the user's active property to false. A real DELETE follows only when the user is hard-deleted in Entra, which Entra does 30 days after a soft delete. So "removed in Entra" and "gone from the tool" can be a month apart, by design.
Failures retry, then stop. If calls to a tool keep failing, for example because the token is no longer valid, Entra puts the job in quarantine, slows it to once a day, and disables it if it stays in quarantine for more than four weeks. Unless someone set up email notifications, the first sign may be a leaver who still has access.
Google Workspace's automated provisioning, by contrast, syncs every few hours rather than continuously. Either way, SCIM is fast compared with a forgotten checklist, and slower than people assume.
Groups and roles
SCIM can push groups as well as users, and this is where it becomes useful for access by role rather than just presence.
Group push creates and maintains groups in the tool that mirror groups in the identity provider. Slack, for example, lets SCIM create and delete user groups. Watch the identity provider's own limits here. Entra assigns apps to groups only with a P1 or P2 license, per the Microsoft guide, and it cannot read nested groups, only the direct members of an assigned group. Microsoft Entra ID pricing covers what P1 costs.
Roles are less standard. SCIM has a "roles" attribute, but the standard defines no vocabulary for it, and many tools ignore it or accept only a few values. Admin rights are often still set by hand.
Licenses and seat types, such as a Figma editor vs viewer or a HubSpot sales seat, are mostly outside SCIM, or handled with tool-specific extensions.
Expect SCIM to handle who is in, and which teams they belong to, and to need help with what they can do.
What it costs: the identity provider side and the tool side
There are two bills again, as with SSO. Prices below were read on each vendor's page on 27 October 2026.
The identity provider side. You need an identity provider that can push to SCIM. Okta includes Lifecycle Management in Essentials, at $17 per user a month billed annually; on the $6 Starter suite it is an add-on, and Okta has a $1,500 yearly minimum (Okta pricing). JumpCloud sells User Lifecycle Management à la carte at $3 per user a month billed annually (JumpCloud pricing). Google Workspace has automated provisioning for a list of supported apps: up to 3 apps on Business Starter, up to 100 on Business Standard and above. It needs Google set up as each app's SSO identity provider.
The tool side. Each tool has to offer SCIM on your plan, and it almost always comes with SSO, on the same expensive plan or a higher one. Slack has it on Business+, GitHub on Enterprise, Figma on Organization, Zoom on Business; all four also need SAML SSO. For 20 people, moving those four tools to the plans that include SCIM:
| Tool | Plan without SSO | Cheapest plan with SSO | Extra a year, 20 people |
|---|---|---|---|
| Slack | Pro · $7.25 a seat | Business+ · $15 a seat | $1,860 |
| GitHub | Team · $4 a seat | Enterprise · $21 a seat | $4,080 |
| Figma | Professional · $16 a seat | Organization · $55 a seat | $9,360 |
| Zoom | Pro · $14.16 a seat | Business · $18.33 a seat | $1,000.80 |
| Total SSO tax a year | $16,300.80 | ||
Some tools go further. Notion has SAML SSO on Business but keeps SCIM for Enterprise, which has no public price. Jira and Confluence get SCIM through Atlassian Guard Standard, $4.35 per user a month on top of the products (Atlassian Guard pricing).
So "SCIM for 20 people" is rarely the identity provider's line item. It is the SSO tax, plus the identity provider, plus whatever the tools that keep SCIM on Enterprise charge. Notice too that the tool-side upgrade applies to every seat, while the thing you wanted, removals, happens a few times a year.
Failure modes
SCIM is reliable when it is running, and quiet when it is not.
The token expires or its owner leaves. Some tools tie the SCIM token to the admin who created it. Remove that admin, and provisioning silently stops. Errors nobody reads are the next problem: a failed push shows up in the identity provider's provisioning log, not in anyone's inbox, unless you set up notifications.
Unmatched accounts. Anything created outside the identity provider is invisible to it, so it is never deactivated. Deactivated, not deleted. Many tools only suspend the account. Data and ownership stay, which is usually what you want, but check whether the seat is still billed.
Partial coverage is the biggest one. SCIM covers only the tools that support it on the plan you pay for. Everything else is still manual, and that list is usually longer.
Can SCIM remove users automatically?
Yes, that is its main use, within the limits above. When someone is removed or suspended in the identity provider, it deactivates their account in every tool connected through SCIM, on the next sync. It does not reach accounts created outside the identity provider, tools without SCIM, open sessions the tool does not end on deactivation, or API tokens the person created. Offboarding still needs a short manual list for those; our employee offboarding checklist covers it.
The alternatives for small teams
If SCIM on every tool is out of reach, the options are plainer than vendors suggest.
A written process. A provisioning bundle per role and an offboarding checklist, done by hand. It is free, and fine for very small teams if someone owns it.
SCIM where it is free, manual elsewhere. Some tools include SCIM on mid-tier plans. Connect those, and keep a checklist for the rest.
A regular access review catches what slipped through, whichever method you use.
Automation without SCIM is the last option. Automated user provisioning without SCIM compares the ways to do it, and SmashSSO is one, below.
Where SmashSSO fits
SmashSSO gives you SCIM-style provisioning without SCIM or an identity provider. It reads your people from Google Workspace with read-only access, finds who has an account in each tool and with which role, and invites, changes and removes them by role from one place. Where a tool offers a member API on your plan, you can add a token and it uses that; for everything else, an agent works in your own Chrome, in tabs where you are already an admin, on the plan you already have. Roles and seat types are set as part of the same change.
The limits: agent-run changes need that browser open, are slower than an API, can fail when a tool changes its screens, and some tools' terms restrict automated use. Steps that would add a paid seat pause for your approval, and every change goes to an audit log. It is not SSO. It costs a flat fee from $199 a month billed annually (pricing), and how it works shows the flow.