trio.so
Explained

User Provisioning: How to Create, Change, and Remove Accounts Automatically

User provisioning and deprovisioning explained: joiner, mover and leaver steps, SCIM vs directory sync, and how to automate accounts from your directory.

Mountain landscape representing leadership perspective and vision
Written by
Atena Ladchartabi

Content writer, trio.so

Published on
Modified on

User provisioning is the process of creating user accounts and giving people the access they need when they join, changing that access when they move roles, and removing it when they leave. The removal half is called deprovisioning. Done by hand, it means creating the same person in a dozen systems and hoping someone remembers to delete them later. Automated user provisioning does it from one source, usually your HR system or identity provider, using directory sync and the SCIM standard.

If you create and delete accounts by hand every time someone joins or leaves, this guide shows the joiner, mover and leaver steps, how SCIM and directory sync differ, and what to automate first.

User Provisioning Meaning: What Is User Provisioning?

User provisioning, often referred to as account provisioning, involves the creation, management, and deactivation of user accounts. It includes granting each user the right access to data and applications within an organisation. It is a core part of identity and access management: each person gets the access their job needs, and no more.

Provisioning covers three kinds of access:

  • Account provisioning: creating the account itself in the directory, email and each app.
  • Access provisioning: adding the account to the groups and roles that decide what it can open.
  • Device provisioning: getting the person a laptop or phone that is set up and enrolled. See new hire onboarding for the full first-day list.

Types of Provisioning

  • Manual provisioning: an administrator creates each account and assigns rights by hand. Fine for a handful of people, error-prone after that.
  • Automated user provisioning: accounts and group memberships are created, changed and removed automatically from a source of truth, based on rules.
  • Self-service provisioning: users request extra access themselves, and an owner approves or rejects it.

Joiner, Mover, Leaver: The Provisioning Lifecycle

Every account goes through the same three events. The table shows what should happen at each one.

EventTriggerWhat happens
JoinerNew hire added in HR or the directoryAccount created in the directory, added to groups for their role, accounts created in each connected app, device prepared
MoverRole, team or location changesGroup memberships updated, access to the old role's apps removed, new apps added
LeaverLeave date reached in HR or account disabledSign-in blocked, sessions ended, accounts deactivated in every app, licences reclaimed, device collected and wiped

Movers are the step most companies get wrong. People collect access as they change roles and never lose the old access, which is how a long-serving employee ends up with rights to everything.

The Process of Provisioning and Deprovisioning

Provisioning: Setting the Stage for New Employees

  1. Confirm the person: the hire exists in HR with a start date, role and manager.
  2. Define the role: the role decides which groups and apps the person gets.
  3. Create the account: in the directory first, with a unique username and email.
  4. Assign access: add the account to role groups; connected apps create their own accounts from those groups.
  5. Prepare the device: ship or hand over a device that enrolls automatically when the person signs in.
  6. Secure the sign-in: require multi-factor authentication from the first sign-in. See multi-factor authentication.

Deprovisioning: Safeguarding Data When Employees Leave

Deprovisioning is equally important as provisioning, yet it is often overlooked. It is the process of revoking access and recovering resources when an employee leaves the company or changes roles. The steps include:

  1. Trigger event: a resignation, termination or role change starts the process, ideally from the HR system.
  2. Access revocation: block sign-in and end active sessions, so the person cannot keep using an open session or a saved token.
  3. Account deactivation: disable or remove the account in the directory and in every connected app.
  4. Data retrieval: hand over or archive the person's files and mailbox according to company policy.
  5. Asset recovery: collect the laptop and phone, then wipe or reassign them.
  6. Audit: record what was removed and when, so you can show it later.

Fast deprovisioning matters most for leavers who part on bad terms and for accounts in apps that are not connected to single sign-on, where blocking the directory account does not end access. For more, see deprovisioning in cybersecurity and the IT offboarding checklist.

Automated User Provisioning

Automated user provisioning uses software to create, update and remove accounts based on rules and a single source of truth. The most efficient setup for most companies:

  • One source of truth: the HR system for who works here, synced into the identity provider (such as Microsoft Entra ID, Okta or Google Workspace).
  • Role-based groups: groups in the identity provider decide which apps each person gets.
  • Connected apps: each app receives accounts from the identity provider through SCIM or a directory sync, instead of IT creating them by hand.

The result is consistent access for every person in the same role, a new joiner who is ready on day one, and a leaver whose access ends everywhere when the HR record changes.

SCIM vs. Directory Sync

Both move users and groups from the identity provider into another system, but they work in opposite directions.

SCIM provisioningDirectory sync
Who starts itThe identity provider pushes changes to the appThe app pulls users and groups from the directory on a schedule
SpeedNear real time, as changes happenAt each sync run
StandardSCIM 2.0, an open standard (RFC 7643 and 7644)Each directory's own API
Typical useCreating and deactivating accounts in SaaS appsKeeping a full copy of users and groups for reporting and policy

Many apps support both: SCIM for fast joins and leaves, directory sync for a full picture. For how to secure SCIM endpoints and tokens, see SCIM security.

SCIM vs. SSO

Single sign-on (SSO) controls how a user signs in. SCIM controls whether the account exists at all. You need both: SSO without SCIM leaves accounts behind in apps after people leave, and SCIM without SSO still leaves people with separate passwords.

What to Automate First

  1. Leavers. Automatic deprovisioning closes the biggest risk, so connect your most sensitive apps first.
  2. The apps everyone uses. Email, chat, file storage and your device management console.
  3. Role groups. Clean up groups in the identity provider before you connect more apps, or you will automate bad access.
  4. Movers. Once joiners and leavers work, make role changes update groups automatically.

What to Look for in User Provisioning Software

  • SCIM 2.0 support and directory sync with the identity provider you use.
  • Group-based assignment, so access follows roles.
  • Automatic deactivation, not just creation.
  • Logs of every change, for audits.
  • A link to device management, so a leaver's device can be wiped as part of the same process.

Managing this across many devices

trio.so syncs users and groups from Google Workspace, Okta, Microsoft Entra ID, OneLogin, PingOne, BambooHR and JumpCloud, and accepts SCIM 2.0 provisioning from Entra ID, Okta and OneLogin. When a user is deprovisioned in the identity provider, they lose access, and their company devices can be wiped from the console. See single sign-on.

The trio.so Integrations page, Connected tab, listing Microsoft Entra ID and OneLogin with SCIM provisioning and Okta and Google Workspace with directory sync, all active.
In trio.so, identity providers connect through SCIM provisioning or directory sync.

Frequently asked questions

What is user provisioning?

User provisioning is the process of creating user accounts and assigning access when people join, updating access when they change roles, and removing it when they leave.

What is deprovisioning?

Deprovisioning is the process of revoking access and recovering resources when an employee leaves the company or changes roles. It includes blocking sign-in, deactivating accounts, reclaiming licences and collecting and wiping devices.

What is the difference between SCIM and SSO?

SSO decides how a user signs in to an app. SCIM creates, updates and deactivates the user's account in that app. SSO alone does not remove accounts when people leave.

What is automated user provisioning?

Automated user provisioning creates, changes and removes accounts automatically from a source of truth such as an HR system or identity provider, using rules, role groups, SCIM and directory sync.

Which tools support centralized user provisioning?

Identity providers such as Microsoft Entra ID, Okta, OneLogin and Google Workspace provision users centrally to apps that support SCIM or directory sync. HR systems can feed the identity provider so accounts start and end with the employee record.

Related reading: SCIM security, identity management, deprovisioning in cybersecurity and the IT offboarding checklist.

Ready-to-use Templates

Must-have Template Toolkit for IT Admins

Explore All
Template Toolkit

Create and remove accounts from your directory

trio.so syncs users from Google Workspace, Okta and Entra ID and takes SCIM 2.0 provisioning, so leavers lose access the day they leave.

Start free trial

Manage Every Device From One Console

trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.

14-day free trial. No credit card required.

trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.

Smiling womanAbstract geometric patternAbstract geometric patternSmiling womanSmiling woman

Frequently Asked Questions (FAQ)

Have questions? We've got answers. This section covers some of the most commonly asked questions related to this topic.

User provisioning is the process of creating user accounts and assigning access when people join, updating access when they change roles, and removing it when they leave.

Deprovisioning is the process of revoking access and recovering resources when an employee leaves the company or changes roles. It includes blocking sign-in, deactivating accounts, reclaiming licences and collecting and wiping devices.

SSO decides how a user signs in to an app. SCIM creates, updates and deactivates the user's account in that app. SSO alone does not remove accounts when people leave.

Automated user provisioning creates, changes and removes accounts automatically from a source of truth such as an HR system or identity provider, using rules, role groups, SCIM and directory sync.

Identity providers such as Microsoft Entra ID, Okta, OneLogin and Google Workspace provision users centrally to apps that support SCIM or directory sync. HR systems can feed the identity provider so accounts start and end with the employee record.

Related

From the blog

The related industry news, interviews, technologies, and resources.