IT Glossary
User provisioning creates and manages accounts and access across apps. Learn how provisioning works, manual vs SCIM vs JIT, and how Corma automates it.
July 3, 2026
User provisioning is the process of creating, configuring, and managing user accounts and their access rights across applications and systems. It assigns the right resources to a user based on their role when they join or change positions. Provisioning can be manual, automated through SCIM, or triggered just in time at first login, and it is the first stage of the identity lifecycle.
Provisioning can happen three ways. Manual provisioning has IT create accounts by hand, which suits a handful of apps at low volume but is error-prone. SCIM-based provisioning lets the identity provider push accounts through an API, which works for apps that support SCIM. Just-in-time provisioning creates the account at first login, which fits SSO apps and reduces standing access.
A new sales hire should have Salesforce, Slack, and the CRM ready on day one. With automated provisioning tied to their role, all three are created before they log in, with the correct permissions. Manual provisioning, by contrast, leaves gaps (access requested late, or over-granted "just in case"). The recurring problem is the long tail of apps that do not support SCIM, which still get handled by hand unless a SaaS Management plus IAM layer covers them.
Provisioning creates and grants access when it is needed. Deprovisioning removes it when a user leaves or no longer needs it. Both are stages of the identity lifecycle.
It is provisioning driven by an identity source through standards like SCIM, so accounts and permissions are created automatically rather than by manual tickets.
Through alternative automation or, too often, manual work. Corma extends provisioning and deprovisioning to apps that lack native SCIM support.
