←  All terms
S
Security & Compliance

SCIM

SCIM is a standard for automatically provisioning, updating, and deactivating user accounts across identity systems.

SCIM automates user and group lifecycle management between a central identity provider and connected applications. It helps organizations create, update, and deactivate accounts consistently while reducing manual administration and access errors. Clear role definitions, secure provisioning workflows, and regular review of permissions are important for a reliable implementation. The concept is closely related to Single Sign-On and Role-Based Access Control.

Read more

Single Sign-On

Role-Based Access Control

Governance

SAML

FAQ

SCIM

What are the prerequisites for using SCIM?
A central identity system as the source, an application with a SCIM interface, and an agreed attribute and group model are required. Not every application or plan supports SCIM. This should be clarified before planning, as should the way groups map to the application's roles.
When does introducing SCIM pay off?
With many users, frequent team changes or turnover, and requirements to revoke access promptly. With only a few accounts, manual upkeep is cheaper. A typical use case is deprovisioning: when a person leaves, the identity system removes access automatically instead of an account being forgotten.
How does SCIM differ from single sign-on?
SSO handles authentication, SCIM handles account management. SSO answers how someone signs in; SCIM answers whether an account exists at all and with which attributes. Without SCIM, accounts must still be created and deleted manually despite a central login. The two are often combined.