Skip to content
Scope an integration

Glossary

What is SCIM?

SCIM (System for Cross-domain Identity Management) is an open standard for creating, updating and deactivating user accounts across systems automatically.

SCIM, the System for Cross-domain Identity Management, is an open standard (RFC 7643 and RFC 7644) that lets an identity provider such as Okta or Microsoft Entra ID create, update and deactivate users and groups in a SaaS application through a standard REST API. It replaces manual user management and CSV uploads.

How does it work?

  1. The SaaS application exposes SCIM endpoints, typically /Users and /Groups, protected by a bearer token.
  2. The customer’s identity provider is configured with that endpoint and token.
  3. When someone joins, changes role or leaves, the identity provider sends POST, PATCH or PUT requests, or deactivates the user (often active: false).
  4. The application applies the change and returns the resource, so both sides stay in sync.

SCIM complements SAML SSO rather than replacing it: SSO controls how users sign in, while SCIM controls whether their account exists and what groups it belongs to.

Where it shows up in integrations

  • Enterprise deals SCIM is a common line item on enterprise security questionnaires, usually alongside SAML SSO.
  • LMS onboarding New hires get an LMS account and group membership on day one, without an admin uploading a CSV.
  • Offboarding Deactivation through SCIM removes access the moment HR or IT disables the user, which matters for compliance.
  • Group-based access Groups pushed by the identity provider map to teams, roles or course enrolments in the product.

Common pitfalls

  • Treating every identity provider the same: Okta and Entra ID differ in when they use PUT or PATCH, in the format of their PATCH operations and in the filters they send.
  • Hard-deleting users on deprovisioning instead of deactivating them, which loses history and audit data.
  • Matching users by email only, which breaks when someone changes their name or email address.
  • Not handling pagination and filtering on /Users, which identity providers rely on for reconciliation.