User lifecycle management

Business basics2min read

User lifecycle management is the process of creating, updating and disabling user accounts and access throughout a person's relationship with an organization. In identity and access management (IAM), it covers onboarding, role changes and offboarding for employees, contractors or customers.

How it works

For employee accounts, an HR record often triggers changes through an identity provider. Role-based rules then grant or remove access in connected apps. Someone still needs to handle exceptions and apps outside that setup.

Offboarding should disable sign-in, revoke sessions and remove app access. Retaining business records is a separate decision from letting someone keep logging in.

Moving from support to sales

A startup employee moves from support to sales. Their old role uses four apps; the new role needs three, with two shared.

AccessBeforeAfter
Email and chat22
Support-only apps20
Sales CRM01
Total apps43

Required access is 4 - 2 + 1 = 3 apps. Just adding the CRM would leave five. Removing the old permissions limits unnecessary access to customer data without blocking the employee's new work.

What the standard says

The IETF's SCIM Core Schema, a standard for exchanging identity data, defines an active attribute for account status. Its precise meaning depends on the service provider.

Check whether deactivation ends existing sessions and removes downstream access, rather than just blocking the next login. Do not treat a central "disabled" status as proof that every app is covered.

Questions people ask

What is lifecycle management in IAM?

It is the joiner, mover and leaver process described above. IAM also covers authentication and authorization: proving identity and deciding which actions someone is allowed to take.

What is an example of identity management?

A new employee gets a company account, signs in with multifactor authentication and receives access to approved apps. Lifecycle management updates that access when their role changes or employment ends.

Sources

  1. IETF, RFC 7643, "System for Cross-domain Identity Management: Core Schema", September 2015.