The joiner-mover-leaver model is an identity lifecycle process for creating, changing and removing user access as people enter, move within, or leave an organisation. It ties account provisioning, entitlement updates, privileged access review and account deprovisioning to HR or workflow events so access matches job status and leaver accounts do not remain active.
What the JML model covers
The joiner-mover-leaver model is a lifecycle control for access, not just an onboarding checklist. It defines when access is granted, changed, reviewed and removed so that permissions follow employment status, role changes and departure events. In practice, it is the backbone for keeping account state aligned with the organisation’s current need.
At its best, JML creates a repeatable bridge between HR or workflow events and identity governance actions. That bridge matters because access drift usually begins when the process is partial, delayed or dependent on manual follow-up, especially for privileged roles and exception accounts.
Why JML matters for access governance
JML is important because access is dynamic. A new starter may need standard entitlements, a mover may need old access removed before new access is added, and a leaver should lose access quickly enough that dormant accounts do not become a path for misuse. The model helps prevent privilege creep, orphaned accounts and inconsistent approvals by making lifecycle state the trigger for access decisions.
It also clarifies ownership. HR, line managers, IAM teams and application owners each play different parts, but the process only works when authoritative source data, approval logic and enforcement are aligned. NHIMG’s IAM and IGA Basics is a useful companion when you want the broader access-governance model that sits behind the JML workflow.
JML across joiners, movers and leavers
Joiners need timely provisioning based on the role they are actually starting in, not on a generic template that leaves excessive access in place. Movers are often the hardest case, because the risk is not only new access being added but old access being forgotten, which can leave users with conflicting entitlements or lingering privileged rights from a previous job.
Leavers are the most obvious control point, but they are not the only one. A strong leaver process needs more than account disablement, because tokens, API keys, sessions, delegated access and connected application rights may outlive the user account unless they are explicitly handled. For that reason, Joiner-Mover-Leaver (JML) Guide is especially relevant for the operational detail behind lifecycle cleanup, while Access Governance vs Access Management helps distinguish policy decisions from runtime enforcement.
How organisations implement JML well
Good JML is usually event-driven, auditable and integrated with identity governance. The practical question is not whether access can be provisioned, but whether every access change has a clear trigger, owner, approval path and evidence trail. That is why mature programs tie HR events, access reviews and deprovisioning to one operating model instead of treating them as separate tasks.
The process also needs policy detail, such as how quickly leavers are disabled, how movers are recertified, how exceptions are handled and what happens when a source system is late or incomplete. NHIMG’s Top 10 IGA Mistakes is a useful reference for the failure patterns that often weaken JML in real environments, including neglected movers and weak reconciliation.
Risk and Threat Considerations
JML failures create direct security exposure because stale access is still valid access. When joiner, mover or leaver events are missed, delayed or only partially executed, organisations can end up with excess privilege, dormant accounts, unrevoked tokens or leftover administrative rights that attackers can abuse for persistence or lateral movement.
Failure mechanism: the lifecycle trigger is incomplete, the wrong system is treated as authoritative, or downstream applications are not reconciled after the HR event, so access remains active after the business need has changed.
Impact: a former employee, contractor or compromised account can retain access long after it should have been removed, increasing the chance of unauthorized access, data exposure and abuse of privileged pathways.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-53 Rev 5 and CIS Controls v8 set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | AC-2 — Account Management | JML is an account lifecycle control centered on provisioning, changes and removal. |
| IA-5 — Authenticator Management | JML often requires rotation or revocation of secrets, tokens and authenticators on exit. | |
| AC-6 — Least Privilege | JML prevents privilege creep by aligning access with current job need. | |
| Recommendation — Define account lifecycle triggers, approvals and disablement steps under AC-2. Revoke or rotate authenticators and other credentials when users move or leave. Remove unnecessary access on role change and enforce least privilege at each lifecycle stage. | ||
| CIS Controls v8 | CIS-5 — Account Management | CIS account management directly covers user lifecycle provisioning and revocation. |
| Recommendation — Operationalise joiner, mover and leaver workflows under a central account-management control. | ||
| ISO/IEC 27001:2022 | A.5.18 — Access rights | Access rights must be provisioned, reviewed and removed as roles change or end. |
| Recommendation — Review and remove access rights promptly when employment status changes. | ||
Practitioner Guidance
Governance implication: treat JML as an owned control with defined handoffs, not as an informal service desk habit. The process should specify who approves role changes, who validates removals, who owns exceptions and how evidence is retained for audit and review.
What to watch for: the clearest warning signs are late leaver revocation, mover requests that add access without removing old access, and applications that are outside the normal provisioning path. NHIMG’s Identity Governance and Access Reviews Executive Briefing is a strong fit when you need the board-level perspective on leaver gaps and review quality, while Access Control Policy Template supports the policy language behind joiners, movers and leavers.
Related resources from NHI Mgmt Group
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on November 16, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org