Account provisioning is the process of creating, updating, and disabling user or service accounts and assigning the right access to them.
Account provisioning is the process of creating, updating, and disabling accounts while assigning the right access to them. In plain language, it is how organizations give people and services the accounts they need to start work and adjust those accounts as roles change.
Account provisioning matters because access mistakes at the start of an account’s life often persist for months or years. If accounts are created with too much privilege or not removed when they are no longer needed, the organization carries unnecessary risk.
It also matters because consistent provisioning helps security teams scale identity control across many systems instead of handling every application separately by hand.
Account provisioning appears in HR-driven onboarding, SaaS administration, cloud account creation, SCIM integrations, and Identity Lifecycle workflows. Teams connect it to Least Privilege Access, Access Review, and Service Account management.
Good provisioning includes both assignment and deprovisioning, not just account creation.
A new developer joins, so the organization automatically creates a corporate identity, grants access to source control and ticketing tools, and withholds production admin rights until there is a separate approved need.
Account provisioning is not the same as Authentication. Authentication verifies identity during sign-in, while provisioning prepares the account and permissions behind that sign-in.
It is also different from Access Review, which checks later whether the granted access should still remain.