Skip to content

Blog

SCIM vs SAML: login is not provisioning

SCIM vs SAML: SAML signs people in, SCIM creates and removes their accounts. What each leaves behind when someone leaves, and what each one costs.

· 8 min read

SCIM vs SAML is login vs accounts: SAML decides who can log in to a tool, and SCIM decides who has an account in it. SAML is a login protocol: at the moment someone signs in, your identity provider vouches for them. SCIM is a provisioning protocol: whenever your directory changes, your identity provider creates, updates or deactivates the account in the tool, whether anyone is logging in or not.

You need SAML to control the door, and SCIM to clear out the room. Most tools sell them on the same expensive plan, some sell them on different ones, and almost none sell SCIM without SAML.

The difference in one line

SAML answers "is this person allowed in right now?"; SCIM answers "should this person have an account at all?"

SAMLSCIM
Full nameSecurity Assertion Markup LanguageSystem for Cross-domain Identity Management
StandardSAML 2.0, OASIS, 2005SCIM 2.0, IETF RFC 7643 and 7644, 2015
JobAuthentication: logging people inProvisioning: creating, changing and removing accounts
When it runsEach time someone logs inEach time something changes in the directory
How it travelsA signed XML message, carried by the person's browserAPI calls from the identity provider to the tool, server to server
When someone leavesBlocks new loginsDeactivates the account
Without the otherAccounts pile upPeople still log in with each tool's own password

The rest of this post is about the bottom two rows, because that is where the money and the risk are. If you want either protocol explained from scratch, see what SAML is and what SCIM is; what SSO is has the bigger picture.

What SAML leaves behind when someone leaves

Picture a 25-person company with SAML set up for Slack, GitHub and Figma, and no SCIM. Alex leaves. The admin suspends Alex in the identity provider. What is left?

The account. Alex's Slack, GitHub and Figma accounts all still exist. Nothing told those tools that anything happened, because SAML only speaks when someone tries to log in. The paid seat. In tools that bill per active member, Alex keeps costing money until someone deactivates the account in each admin page.

Open sessions. If Alex's phone still has a Slack session, it can keep working until it expires, because Slack is not checking with the identity provider between logins. How SSO works explains why sessions outlive SSO.

Tokens and keys. API tokens, personal access tokens and SSH keys Alex created were never part of the SAML login, so suspending the login does not touch them in many tools. Group memberships and ownership. Alex is still in channels, teams and repositories, and may still own files, boards or integrations that break when someone finally deletes the account.

GitHub's own documentation is direct about it: without SCIM, SAML single sign-on alone won't deprovision users automatically, and an owner has to remove the person from the organization by hand.

Multiply that by every tool and every leaver, and you get orphaned accounts: logins nobody owns, on seats you still pay for. SAML did its job. It just was never the job you needed.

What SCIM adds

SCIM closes that gap by giving the identity provider a way to change the tool's member list directly.

Deactivation comes first. Suspend or unassign someone in the identity provider and it sends the tool a call to deactivate their account; in many tools that also frees the seat. Creation before day one is next: new hires get accounts in advance, with the right name and email, instead of waiting for their first login. Updates keep name changes, department moves and group memberships in step with the directory. And groups let directory groups become groups or teams in the tool, so access by role stays in step.

SCIM needs no browser and no login to happen. It runs when the directory changes, which is exactly when you need it. SCIM provisioning covers setup and failure modes.

What SCIM does not do is log anyone in. A company with SCIM but no SAML has tidy member lists and people still signing in with separate passwords.

Can SCIM work without SSO?

The standard does not require SSO. SCIM is an API for accounts, not for logins. Many tools require SSO anyway. Figma will not configure SCIM until SAML SSO is set up, and GitHub's SCIM for organizations depends on SAML SSO. So in practice the answer is "in theory yes, at your tools mostly no", and you should read each tool's documentation before planning around SCIM alone.

Coupling the two does have one upside: the identity provider stays in charge of both ends, so an account it creates is also an account it logs in, and nobody has a stray tool password to forget about. The cost is that you buy both even if you only wanted one.

Tools that sell them separately

In practice tools sell these two in one of three ways. All of the following come from each vendor's own pricing or help pages, read on 27 October 2026.

SCIM on a higher plan than SAML. Notion's pricing page lists SAML SSO on its Business plan and the SCIM API for provisioning on Enterprise only. So the plan that lets you control logins does not let you automatically remove anyone, and the one that does is "contact sales". That is the worst arrangement for offboarding, because it charges you twice for the part you actually wanted.

Both on the same plan. Slack puts SAML SSO and SCIM provisioning on Business+ and Enterprise, per its SAML and SCIM help pages. Better, but you still upgrade every seat to get either.

SCIM only after SAML. Many tools will not turn on SCIM until SAML is working. Figma's help center says you have to set up SAML SSO with your identity provider before you can configure SCIM, which is available on its Organization and Enterprise plans (and Education and Government). On GitHub, SCIM for organizations depends on SAML SSO, which needs GitHub Enterprise Cloud. Even if all you wanted was automatic removals, you pay for and run SAML first.

Then there is the identity provider's side. It has to be able to push SCIM too, and that is often its own line item: Okta keeps Lifecycle Management for its Essentials suite and above, and sells it as an add-on on Starter. Okta pricing has the numbers.

The pattern is consistent: provisioning, the feature that actually removes leavers, is priced as an extra on top of login. For a small company whose real problem is offboarding, that is the expensive end of the SSO tax.

Which one to buy first

If a customer contract or an auditor names SAML, buy SAML for the systems in scope, and then check whether SCIM comes on the same plan. Often it does, and leaving it switched off would be paying for removals and doing them by hand.

If nobody requires SAML and your real worry is leavers, ask what you are paying for. SAML alone gives you a blocked login and a lingering account. SCIM gives you the removal, but most tools make you buy SAML to get it. That is a lot of money for one leaver a quarter. Compare it with what doing the removals properly by hand, or with a tool, would cost before you upgrade.

Size changes the sum. A 5-person team with ten tools can work through a leaver checklist in an afternoon, and the upgrade would cost more than the afternoon ever will. A 50-person team with monthly leavers, contractors and forty tools is different: missed removals start to show up as seats on invoices and as accounts nobody can explain in a user access review. That team needs the removals automated somehow. Whether that means SCIM on enterprise plans or something cheaper is a pricing question, not a security one.

Getting provisioning without SCIM

If SCIM on every tool is out of reach, you are left doing what SCIM does some other way. There are honest options.

A checklist, by hand. List every tool, and work through it for each joiner and leaver. It is free and reliable if one person owns it and nobody is in a hurry. Our employee offboarding checklist is a starting point.

SCIM where it is already included. Some tools give you provisioning on the plan you have. Connect those and keep the checklist for the rest.

Just-in-time provisioning. If you have SAML, some tools create accounts on first login. It handles joiners only; it never removes anyone. See just-in-time provisioning.

Scripts against member APIs. Fine for two or three tools with good APIs, fragile beyond that, and the knowledge leaves with whoever wrote them.

A regular review. Whatever you choose, a quarterly user access review catches what slipped through.

All of these are ways of doing deprovisioning without paying for the protocol.

Where SmashSSO fits

SmashSSO does the SCIM side without SCIM, and without SAML. It reads your people from Google Workspace with read-only access, matches them by email to the accounts in each tool, and flags accounts that match nobody. Access bundles by role, such as "Engineer", invite someone to every tool in the bundle with the right role; role changes and removals run the same way. When someone is suspended in Google Workspace, it alerts you and shows every tool where they still have access.

Changes run through a tool's member API where you have added a token, otherwise through an agent in your own Chrome, in tabs where you are already signed in as an admin, on the plan you already pay for. That browser has to be open; agent runs are slower than an API and can fail when a tool redesigns its screens, and some tools' terms restrict automated use. Steps that would add a paid seat pause for approval, and every change is in an audit log.

It does not log anyone in, so it does not replace SAML. If an auditor or a customer contract requires login through an identity provider, you need SAML for those tools. SmashSSO costs a flat fee from $199 a month, billed annually (pricing).

FAQ

Do I need SCIM if I use SAML?
If you want leavers removed automatically, yes. SAML only blocks new logins once someone is disabled in your identity provider; their accounts and paid seats stay in every tool. SCIM is what deactivates those accounts, or you do it by hand.
Can SCIM work without SSO?
The standard does not require SSO, but many tools do. Figma, for example, requires SAML SSO to be set up before SCIM, and GitHub's SCIM for organizations depends on SAML SSO, so check each tool's documentation.
Why do tools charge extra for SCIM?
Because the companies that need it most are large, and putting it on the top plan makes them buy the top plan. Some tools go further: Notion includes SAML SSO on Business but keeps SCIM provisioning for Enterprise.
What happens to SAML users who are never deprovisioned?
Their accounts stay active in the tool, often holding a paid seat, with their group memberships, files and any API tokens they created. They cannot start a new SSO login, but open sessions and tokens can keep working until someone removes the account.

Keep reading

Stop paying for a login button.

Sign in with Google Workspace, connect your tools, and see who has access to what in minutes.

Sign up with Google