User Provisioning: What It Is and How to Automate It

User Provisioning: What It Is and How to Automate It

By Amaresh Ray · April 6, 2026

User provisioning is creating, changing and removing a person's accounts and access as they join, move and leave. This guide covers the joiner, mover, leaver flow, the five provisioning methods, deprovisioning risks and a checklist.

On this page

Last updated: November 21, 2026

User provisioning is the process of creating a person's accounts and granting their access when they join, changing that access when their role changes, and removing it when they leave. Automated user provisioning does this from a trigger (an HR record, an approved ticket or an identity provider group) instead of an admin clicking through each app by hand.

The removal half has its own name, deprovisioning, and it's the half that goes wrong. Most of this guide is about making both halves run from the same record so neither depends on someone remembering.

What is user provisioning?

User provisioning (also called account provisioning, access provisioning or IAM provisioning) covers every change to what a person can sign in to and what they can do once they're in. It includes:

  • Creating the core identity in your identity provider (IdP), such as Okta, Microsoft Entra ID, Google Workspace or JumpCloud.
  • Creating accounts in the apps that person needs.
  • Assigning groups, roles and licenses so they get the right level of access.
  • Updating all of that when they change teams.
  • Disabling the accounts, removing the groups and reclaiming the licenses when they leave.

The number of apps is what makes this hard. Okta's Businesses at Work 2025 report (March 2025) puts the average Okta customer at 101 apps. Each one is a place an account can be created and forgotten.

Provisioning vs deprovisioning

Provisioning grants access. Deprovisioning takes it away: deactivating the account, pulling group memberships, revoking sessions and tokens, and reassigning or reclaiming what the person owned. Treat them as one workflow. If granting runs through an automated path and removal runs through a checklist someone opens on the last day, you'll accumulate access you can't account for.

User provisioning vs SAML just-in-time provisioning

"Just-in-time provisioning" is a SAML feature. When a user signs in through SSO for the first time, the app creates their account from the attributes in the SAML assertion. Microsoft lists it as one of the supported provisioning approaches for Entra ID, as of November 2026.

It's convenient for joiners, but it does nothing for leavers. The account it creates stays in the app until something else removes it. That's why SCIM exists alongside SAML, and we cover the difference in SCIM vs SAML. It's also different from just-in-time access, which grants elevated permissions for a set window and then removes them.

The joiner, mover, leaver flow

Almost every provisioning event is one of three types. Naming them helps because each has a different trigger, a different owner and a different way of failing.

Joiners

A new hire needs an IdP account, a mailbox, their department's groups and the apps their role uses, ideally before day one. The trigger is usually an HR record or a new hire ticket. Joiners rarely cause security problems. They cause productivity problems, because a missing group means a ticket on the first morning.

Movers

A mover changes team, manager or role. They need new access, and they should lose some of the old access. The second part is what usually gets skipped, because nobody files a ticket asking to lose permissions. Movers are where privilege creep comes from: people who've been at the company four years and carry access from three jobs.

Leavers

A leaver needs everything switched off on their last day, or immediately for an involuntary exit. That means disabling the IdP account, removing groups, resetting MFA, transferring files they owned and reclaiming paid licenses. Leavers are where the security risk is, because nobody monitors an account whose owner has left. Our employee offboarding checklist with a Jira template lists every step.

User provisioning methods

There are five common ways to provision users. Most companies run three or four of them at once, depending on the app.

MethodTriggerGood forWeak spot
ManualAn admin acts on an email, Slack message or spreadsheetRare apps, one-off exceptionsSlow, inconsistent, no audit trail
SCIMIdP pushes changes to the app's SCIM endpointApps that support SCIMNot every app offers it, and some keep it for higher plans
IdP groupsAdding or removing a user from a group assigns or unassigns the appAny app assigned through Okta, Entra, Google or JumpCloud groupsGroup sprawl if groups aren't mapped to clear roles
HR-drivenA new, changed or terminated record in the HR systemJoiners and leavers at scaleMovers and app-specific requests don't start in HR
Ticket-drivenAn approved service desk ticketAccess requests, exceptions, anything that needs approvalOnly automated if the ticket actually triggers the change

Manual provisioning

An admin reads a request, logs in to the app's admin console and creates the account. It works when you have ten people. It stops working when the request is in Slack, the approval is in email and the change is in Okta, and nobody can say later who approved what.

Manual provisioning creates hidden standing access

The obvious cost of manual work is time. The less obvious cost is access that never gets removed. When admins are overloaded, they take shortcuts: broader groups, no expiry dates, "we'll clean that up later." If your process makes granting easier than removing, access piles up whether you mean it to or not.

SCIM provisioning

SCIM (System for Cross-domain Identity Management, defined in RFC 7644) is a standard API for creating, updating and deactivating users and groups. Your IdP is the client and the app is the server. When you assign a user to the app in the IdP, the IdP calls the app's SCIM endpoint to create them, and when you unassign them it deactivates them.

SCIM is the best option when an app supports it. The catch is coverage: plenty of apps don't support SCIM at all, and some only offer it on their enterprise tier.

IdP group-based provisioning

Here the IdP group is the unit of access. "Figma Editors" is a group in Okta; the Figma app is assigned to that group; adding someone to the group gives them Figma, and removing them takes it away. Under the hood the IdP may still use SCIM or SSO assignment, but the thing you manage is group membership.

This is the most practical model for most IT teams because every change goes through one system, and reversing a change is the same action backwards. It also makes time-limited access simple: remove the user from the group when the window ends.

HR-driven provisioning

The HR system (an HRIS) is the source of truth for who works at the company, so it's the natural trigger for joiners and leavers. A new record creates the IdP account, a termination date disables it, which is how HR-driven onboarding and offboarding works in Multiplier. Its limit is that HR doesn't know which apps a person needs beyond the defaults for their department, and it doesn't see access requests at all.

Ticket-driven provisioning

Here the trigger is an approved request in your service desk, such as Jira Service Management. The employee asks for an app and a role, the right person approves, and the approval itself makes the change in the IdP. This is the method that covers what HR-driven provisioning misses: movers, app requests, temporary access and exceptions.

Most access changes after day one start this way. It's only automated if the ticket triggers the change and records the result. If the ticket says "approved" and then waits for an admin, an admin is still doing the provisioning by hand.

What automating user provisioning and access changes actually requires

Automating user provisioning starts with one decision: where is the source of truth? If approvals happen in one place and entitlements are managed somewhere else with no link between them, the automation stays partial. The model that holds up is provisioning through the IdP, tied back to the request record.

The source-of-truth rule: provision through the IDP or don't call it automated

If access can be granted without going through your identity provider, some of your provisioning is still manual, however fast it is. The IdP is where group membership, lifecycle state and reversibility live. When approved roles map to IdP groups, the request becomes predictable: approved role equals mapped group, mapped group equals access, and revocation follows the same path backwards.

There are three links: request, decision, execution. If the request record doesn't trigger the change, and the change doesn't write back to the same record, expect audit pain later. Use these questions as a quick self-assessment:

  1. Can a user request access from the same place they request other IT help?
  2. Does the right approver get routed automatically based on the app or manager?
  3. Does approval trigger a real IdP action, not a reminder to a human?
  4. Does the result get recorded on the same ticket?
  5. Can revocation happen automatically when time expires or a review says revoke?

If you answer "no" to two or more, your provisioning is more manual than your dashboard suggests.

Deprovisioning risks

Deprovisioning fails quietly. Nothing breaks when a leaver's account stays active, so nobody notices until an audit or an incident.

Orphaned accounts

An orphaned account belongs to someone who has left. The IdP account may be disabled, but if an app was provisioned outside the IdP (a local login, an app without SCIM, a shared admin account) it stays live. Those are the accounts attackers look for, because nobody watches them.

Leftover access from role changes

Movers keep old access because removing it isn't anyone's job. Over a few years one engineer can end up with production access from a past on-call rotation and finance tool access from a project that ended. Group-based provisioning helps only if the mover workflow removes the old groups, not just adds the new ones.

Live sessions and tokens

Disabling an account doesn't always end existing sessions, API tokens or OAuth grants. A leaver workflow should reset MFA and revoke sessions in the IdP, not just flip the account to inactive.

Licenses you keep paying for

Every account you forget to remove is also a seat you keep paying for. Deprovisioning that removes the IdP group but not the paid license still costs you money every month.

Audit findings

SOC 2, ISO 27001 and SOX auditors test leavers. They pick terminated employees and ask for evidence that access was removed on time. If that evidence is spread across Slack, email and admin console screenshots, the finding is about your process even if the access was removed.

User provisioning checklist

Use this list to set up or audit your provisioning. It's grouped by event so you can hand each part to its owner.

Foundation checklist

  • One identity provider is the source of truth for every user.
  • Every sanctioned app is assigned through IdP groups or SCIM, or is listed as a manual exception with a named owner.
  • Each app role maps to a named IdP group ("Salesforce Read Only", "Salesforce Admin").
  • Access requests come in through one channel, such as a service desk portal, with app, role and reason required.
  • Approvers are defined per app (manager, app owner or both).

Joiner checklist

  • A new hire record or ticket creates the IdP account before the start date.
  • Department or role groups are assigned automatically.
  • The new hire can request anything else from a catalog of approved apps.

Mover checklist

  • A role change triggers a workflow, not just a title update.
  • Old department groups are removed when new ones are added.
  • Elevated or temporary access has an expiry date.

Leaver checklist

  • The IdP account is disabled on the last day, or immediately for involuntary exits.
  • MFA is reset and the user is removed from all groups.
  • Files and group ownership are transferred to the manager.
  • Paid licenses are reclaimed.
  • Apps outside the IdP are deprovisioned by hand or by another tool, and checked off.

Evidence checklist

  • Every grant and removal is logged on the same record as the request and approval.
  • Access is reviewed on a schedule, and "revoke" decisions remove access instead of creating another ticket.

How Multiplier automates the access workflow inside Jira

Multiplier is an access management app that runs inside Jira Service Management. It turns the ticket into the trigger: requests and approvals happen in Jira or Slack, and Multiplier makes the change through your identity provider and logs it on the same issue. It connects to Okta, Microsoft Entra ID, Google Workspace, JumpCloud and on-prem Active Directory.

Joiners and leavers from Jira tickets

Multiplier's actions run as Jira workflow post functions, so they fire on the transition you choose, such as issue creation or approval. When HR submits a joiner, mover or leaver request, Multiplier handles the identity changes. See employee lifecycle management for the full workflow.

For a joiner, that can mean creating the user in Okta or Entra ID from the new hire ticket and then adding the groups their role needs. For a leaver, it can mean deactivating the user, resetting MFA and removing them from groups in one workflow. In Google Workspace it can also transfer Drive files and suspend the user. The Okta integration page lists every Okta action.

Provisioning through IDP groups makes changes authoritative

For app requests, employees pick an app and access level from a catalog in the JSM portal or Slack. Each access level maps to an IdP group. When the request is approved, Multiplier adds the user to that group, which provisions the app. Approvals can route to the requester's manager (using the manager from their Okta profile), and in Google Workspace to a group's managers or owners.

If the request is time-limited, Multiplier removes the user from the group when the access period ends, which revokes the permissions. Removal goes back through the same IdP group, which is what makes it reliable.

Apps without SCIM

For apps your IdP can't provision, Multiplier offers AI agents that use browser automation to log in to the app's admin panel, create and remove users and assign licenses. See disconnected apps.

What this looks like in practice

Synthesia's four-person IT Ops team supports 420+ employees with Multiplier. They processed 3,800+ access requests in a year and fully automated 75% of them, after replacing Slack channels and a Notion board. If you're starting from Atlassian group management specifically, our Atlassian user provisioning guide walks through that setup.

Multiplier costs $5 per user per month on Standard, which includes access requests, access reviews and employee lifecycle workflows. Advanced is $6 per user per month. Both come with a 30-day free trial. Start your free trial on the Atlassian Marketplace.

Frequently asked questions

What is automated user provisioning?

Automated user provisioning creates, updates and removes user accounts from a trigger instead of manual admin work. The trigger is usually a new or changed HR record, an approved access request ticket, or a change in identity provider group membership. The identity provider then makes the change in each app through SCIM or group assignment, and the change is logged. The goal is that removing access is as automatic as granting it.

What does IAM provisioning mean?

IAM provisioning is user provisioning described from the identity and access management side. It means using your IAM system, usually an identity provider like Okta or Microsoft Entra ID, to create identities, assign groups and roles, and push accounts into connected apps. It also covers the reverse: disabling identities and removing access when someone changes role or leaves. The terms are used interchangeably.

Is SCIM required for automated provisioning?

No. SCIM is the cleanest way to push accounts from an identity provider into an app, but it isn't the only one. You can provision through IdP group assignment, through an app's own API, through ticket-driven workflows that call the IdP, or through browser automation for apps with no API. Most companies use SCIM where it's available and one of these other methods for the rest.

How fast should deprovisioning happen?

Disable the identity provider account by the end of the person's last working day, and immediately for involuntary exits. App access removed through IdP groups or SCIM then follows within the IdP's sync cycle. Apps outside the IdP should be on the same leaver checklist, with a named owner. Auditors typically sample terminated users and check that access ended on or near the termination date.

Who owns user provisioning, HR or IT?

Usually both. HR owns the record of who works at the company and when they start or leave, so HR triggers joiners and leavers. IT owns the identity provider, the group mapping and the workflow that makes the change. App owners often approve access to their own tools. Problems start when the hand-off between them is an email or a Slack message instead of a ticket that triggers the change.

Can Multiplier provision users from Jira Service Management?

Yes. Multiplier runs inside Jira Service Management and provisions through Okta, Microsoft Entra ID, Google Workspace, JumpCloud and on-prem Active Directory. It can create users from new hire tickets, add users to the groups mapped to an approved app request, remove groups when time-based access ends, and deactivate users on offboarding. Every action is logged on the Jira issue. It has a 30-day free trial.