Topic starter
12/02/2026 3:43 pm
TL;DR: Movers are the most overlooked part of JML because role changes create hidden entitlement creep, unclear triggers, and cross-functional gaps that leave old access in place after responsibilities shift, according to Lumos. That failure mode turns routine job movement into a long-lived identity governance problem, not a one-time provisioning issue.
Editorial analysis by NHI Mgmt Group, based on content published by Lumos: “Why “M” Is the Hardest Part of JML”.
Key questions
Q: What breaks when mover events are not formalised in JML governance?
A: Mover events become invisible to automation, so access changes happen late or not at all.
Q: Why does access creep happen when employees move between roles?
A: It happens because role changes are often gradual, ambiguous, and cross-functional, while access governance assumes a clean handoff.
Q: How should security teams handle transitional access during internal moves?
A: They should separate temporary transition access from long-term entitlements, give the overlap a clear end point, and review it as part of the move itself.
Practitioner guidance
- Formalise mover as a distinct lifecycle event Trigger access changes from an explicit mover state, not from ad hoc manager requests or informal team reshuffles.
- Separate transitional access from permanent access Allow temporary overlap only for named duties during the transition period, and label those entitlements so they can be removed without affecting the destination role.
- Use contextual access policies for role variants Build access profiles around responsibilities, team context, and geography where a title alone is too coarse to govern what the person should still keep.
Bottom line: Mover governance fails when organisations treat internal role changes as informal exceptions instead of formal lifecycle events.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
11/10/2026 6:24 am
Mover governance is a lifecycle discipline, not a cleanup task. Organisations that treat movers as a side effect of onboarding or offboarding end up managing access after the fact. The real problem is that the identity state changes before the governance state does, which means over-permissioning becomes the default unless mover events are explicitly modelled. Practitioners should treat role transition as a first-class lifecycle state.
A few things that frame the scale:
- 69% of security leaders agree identity management must fundamentally shift to address agentic AI systems, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: How do managers and IAM teams prevent mover drift across departments?
A: They need a shared mover process that links HR, IT, security, and managers to the same event definition. When the organisational record, the ticketing workflow, and the access policy all move together, the chance of stale permissions surviving the transition drops sharply.
👉 Read our full editorial: Why movers are the hardest part of JML governance