Skip to content

SCIM and Automatic User Provisioning

Last checked November 15, 2026

SSO answers "can this person sign in?" SCIM asks something else. Does this person have an account at all? It's the part that handles new hires and people who leave.

Why accounts are a separate job

Say you hire a bookkeeper on Monday. With SSO set up, they can sign in to the accounting app. But the app still needs an account for them, with a name, an email and a role.

Someone could create it by hand in each app. That works until the team grows. Then it's slow, and it's easy to forget one.

SCIM automates it. It's a standard for automating the exchange of user identity information between identity domains, or IT systems.1

What SCIM does for joiners and leavers

Wikipedia gives this example. A company onboards new employees and separates from existing ones, and they're added to or removed from the company's employee directory. SCIM can then add or delete the matching accounts in outside systems.1

The result is that a new account exists in each outside system for each new employee. For former employees, the accounts might no longer exist in those systems.1

Notice the careful wording: "might." What actually happens to a leaver's account depends on the app and on how your admin set it up. Check each app's own help pages.

Joiners and leaversStaff list changesIdentity system sends the changeApp adds, updates or removes the accountAccount matches the staff list
One change in the staff list flows out to the apps.

It handles more than create and delete

SCIM can also share information about user attributes, attribute schema and group membership.1 An attribute is a fact about a user, such as a contact detail. A schema is the agreed list of fields. A group is a set of people, like "Sales."

Group membership is generally used to manage permissions.1 SCIM can pass those group changes along, so permissions don't have to be edited app by app.

The protocol itself is described as an HTTP-based protocol for provisioning and managing identity data. It supports resources such as Users and Groups.2

Why a standard helps

Without one, every connection is custom work. The source says that without a standard connection method, companies must write custom software connectors.1

A standard means an identity system and an app can agree on how to talk without a one-off build. That's the same idea as SAML, only for accounts rather than sign-in.

The current version, SCIM 2.0, was completed in September 2015.1

SCIM and SSO side by side

SSO SCIM
Question it answers Who is signing in right now? Which accounts should exist?
When it acts At each sign-in When people join, change or leave

They do different jobs, so one doesn't stand in for the other.

Questions to ask about your own apps

  • Does the app support SCIM, or only SSO?
  • Does a removed person's account get deleted, or only switched off?
  • Do group changes carry across?

Records and retention rules for staff data differ by country and sometimes by state. For those, ask your accountant or lawyer, not your software.

Cited material

  1. System for Cross-domain Identity Management, Wikipedia
  2. System for Cross-domain Identity Management: Protocol (RFC 7644), Internet Engineering Task Force