The lifecycle process that updates access as people or systems join, change role, or leave. For identity programmes, it is the mechanism that prevents rights from becoming stale and shared access from becoming unaccountable. Strong JML discipline is a continuous control, not a one-time onboarding task.
What Joiner-Mover-Leaver Flow Actually Governs
Joiner-mover-leaver flow is the identity lifecycle control that keeps access aligned to a person's or system's current status. It starts with onboarding, continues through role and responsibility changes, and ends with timely removal of access when the actor leaves. The purpose is not just efficiency, but preventing stale entitlements, privilege creep, and unowned access.
A well-run JML process treats identity changes as normal operating events rather than exceptions. That matters because rights granted at entry often persist after a transfer, and transfer-related access often survives after exit unless someone explicitly removes it. For that reason, JML is one of the clearest examples of identity governance in day-to-day operations.
Why JML Breaks Down in Real Organisations
JML usually fails at the handoffs between HR, managers, IT, and application owners. If any source of truth is delayed, incomplete, or inconsistent, access changes arrive late or not at all. The result is often birthright access that is never trimmed, shared accounts that are never reassigned, and leavers who keep access longer than intended.
It also fails when organisations focus only on joiners. Onboarding is visible and time-sensitive, but movers are where hidden drift accumulates. Role changes can require removal of old permissions as much as addition of new ones, and if the removal step is skipped, the access model becomes broader over time even when no one intended that outcome.
For that reason, JML should be understood as a lifecycle assurance process, not a provisioning ticket queue. Its quality is measured by whether access reflects the present state of the identity, not by how quickly a new account was created.
What Good JML Looks Like
Strong JML design ties identity events to authoritative business signals and makes each state change reviewable. That means joiner, mover, and leaver triggers are explicit, approvals are traceable, and entitlement changes are reversible. It also means the process covers more than human workers, because service identities, agents, contractors, and other non-standard accounts can drift just as easily.
The most reliable JML programmes minimise manual interpretation at the point of change. They standardise roles where possible, define exceptions where needed, and make ownership clear for systems that cannot be fully automated. This is where Joiner-Mover-Leaver (JML) Guide is useful as a lifecycle reference, because it focuses on the operational details of provisioning, deprovisioning, and removing the access that leavers leave behind.
It is also useful to connect JML to broader identity governance. The IAM and IGA Basics guide helps place JML in the larger model of access requests, entitlements, reviews, and governance over both people and machines.
JML and the Controls It Depends On
JML is not a single control, but a process that depends on several controls working together. Provisioning determines what gets created, access reviews identify what should still exist, and deprovisioning removes what no longer should. If those controls are disconnected, the lifecycle breaks even when each individual step looks acceptable in isolation.
Practically, the control question is often whether old access is actually removed when roles change or employment ends. That is why organisations use policy, workflow, and review cadence to make JML repeatable. A useful companion reference is the Access Control Policy Template, which includes joiner and leaver statements, review cadence, and least-privilege expectations.
Where offboarding is the most failure-prone part of the cycle, the Employee Offboarding Security Guide is the most direct operational companion, because it covers revocation of sessions, tokens, and access across common enterprise platforms.
Risk and Threat Considerations
Weak JML creates durable exposure because stale access is often hard to spot and easy to exploit. The risk is not limited to former staff keeping an account, it also includes movers retaining broader rights than their current role justifies and privileged access lingering after a transition.
Failure mechanism: If joiner, mover, and leaver events are not synchronised with authoritative sources, access persists after it should have been reduced or removed. That can leave orphaned accounts, excess privilege, and unowned credentials available for misuse.
Impact: The organisation can lose accountability for who can access what, and a compromise may spread through credentials, sessions, keys, or shared access paths that should have been revoked at the lifecycle boundary.
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 | IA-5 — Authenticator Management | JML must rotate or revoke authenticators and other lifecycle-bound access material. |
| AC-2 — Account Management | JML is the lifecycle process for creating, changing, reviewing, and removing accounts. | |
| PS-4 — Personnel Termination | Leaver handling depends on promptly disabling access when personnel separation occurs. | |
| Recommendation — Revoke or replace authenticators and related access material when a joiner, mover, or leaver event changes authority. Tie account creation, modification, review, and removal to authoritative lifecycle events. Disable or remove access immediately at separation and confirm residual access is cleared. | ||
| ISO/IEC 27001:2022 | A.5.18 — Access rights | JML governs granting, changing, and removing access rights throughout the identity lifecycle. |
| A.6.5 — Responsibilities after termination or change of employment | Mover and leaver events require defined responsibility changes and exit handling. | |
| Recommendation — Review and revoke access rights whenever roles change or employment ends. Assign and execute clear offboarding and role-change responsibilities when employment changes. | ||
| CIS Controls v8 | CIS-5 — Account Management | JML operationalises account lifecycle management, especially joins, moves, and leavers. |
| Recommendation — Manage account lifecycle events so obsolete access is removed and current access remains justified. | ||
Practitioner Guidance
Governance implication: Treat JML as a cross-functional ownership problem, not a tooling problem. The business must define who can trigger lifecycle changes, who approves exceptions, and who is accountable when access remains after a move or departure.
What to watch for: Watch for role changes without matched removals, leaver events that occur outside normal hours or outside workflow, and systems where access is granted manually but never reviewed. Those are the places where JML usually degrades first.
Practitioner takeaway: If JML is healthy, access should change as fast as the person's or system's role changes, and be gone when that role is gone.
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 4, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org