Topic starter
01/07/2026 2:02 am
TL;DR: Manual joiner, mover, and leaver handling creates silent access drift, delayed provisioning, and incomplete offboarding across employees, contractors, and partners, according to Zluri’s guide on JML automation. The governance problem is not just speed. It is whether identity programmes can keep least privilege intact as roles change and access footprints expand.
Editorial analysis by NHI Mgmt Group, based on content published by Zluri: “The IT Admin's Guide to JML — Joiners, Movers, and Leavers Automation”.
Key questions
Q: What breaks when joiner mover leaver processes are handled manually at scale?
A: Manual joiner mover leaver handling creates inconsistent access, delayed productivity, and incomplete removal of entitlements when people change roles or leave.
Q: Why does poor mover handling create more long-term IAM risk than a slow onboarding process?
A: Mover handling erodes least privilege without stopping work.
Q: How do you know if JML automation is actually working?
A: JML automation is working when the access outcome matches the lifecycle event across all connected systems, with no unexplained exceptions.
Practitioner guidance
- Automate HRMS-triggered provisioning Bind joiner workflows to authoritative HR fields such as role, department, seniority, and location so birthright access is issued without manual tickets.
- Remove obsolete mover access at the same time as new access Design role-change playbooks so old-role applications, groups, and permissions are revoked when the new role is provisioned, not after a separate cleanup review.
- Set expiry on event-based access Require structured requests for temporary access and attach a default end date so project-based or exception access cannot persist indefinitely.
Bottom line: Joiner, mover, and leaver automation is fundamentally a governance problem because access changes must follow lifecycle events, not manual tickets.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 4 days ago by NHI Mgmt Group
01/07/2026 2:22 am
JML is not a workflow convenience, it is identity governance at operating scale. The article shows that joiner, mover, and leaver events are continuous, not exceptional, which makes manual handling structurally incapable of preserving consistent access decisions. The practical conclusion is that lifecycle governance must be treated as a core control plane, not an admin task.
A few things that frame the scale:
- Around 59% of companies report experiencing a data breach related to poorly managed offboarding processes.
A question worth separating out:
Q: How should teams govern contractor, vendor, and partner access in JML?
A: Treat external identities as part of the same lifecycle discipline, but do not assume HR will signal their start or end. Use structured requests, explicit expiry, and dedicated offboarding paths so access cannot outlive the business relationship that justified it.
👉 Read our full editorial: Joiners, movers and leavers automation is identity governance at scale
This post was modified 4 days ago by NHI Mgmt Group