Topic starter
06/11/2026 6:56 pm
TL;DR: JML automation breaks down when movers, source conflicts and partial leaver failures are not tested explicitly, according to Ploy. Practitioners need proof that access is recalculated, conflicts are surfaced and exits cannot close while anything remains open.
Editorial analysis by NHI Mgmt Group, based on content published by Ploy: “JML automation buyer checklist: test movers, source conflicts and failed provisioning”.
Key questions
Q: What should happen when HRIS and IdP data conflict?
A: When HRIS and IdP data conflict, the workflow should apply a field-level source-of-truth rule and stop the entitlement change until the authoritative field is clear.
Q: How can offboarding automation prove a leaver is finished?
A: Offboarding automation proves a leaver is finished by checking that the leaver state open is cleared only after accounts are disabled, tokens revoked, sessions terminated and any privileged access removed.
Q: How should JML automation handle changing roles?
A: JML automation should recalculate access on every role change, using the new job, department, manager and location attributes to add, remove or adjust entitlements.
Practitioner guidance
- Test field-level source ownership Require a named system of record for each identity attribute and verify how conflicts are flagged when the HRIS and IdP disagree.
- Run mover scenarios that remove old access Simulate department, manager and employment-status changes and check that access tied only to the old role is removed, not preserved.
- Verify leaver completion cannot close early Create a partial-offboarding case with one failed removal and confirm the workflow remains open until retries and manual tasks finish.
Bottom line: The main risk is not broken onboarding but lifecycle drift, where movers and partial exits keep access alive after the business reason has changed.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
06/11/2026 6:56 pm
Field ownership is the hidden governance boundary in JML automation. If two systems can both influence the same identity attribute, the programme has no stable authority model and the workflow can only guess. That is why the conflict test matters more than the happy-path demo: lifecycle governance fails when source data is ambiguous, not when a button is missing. Practitioners should treat field-level ownership as a control requirement, not an implementation preference.
A few things that frame the scale:
- Over 70% of organisations lack automated access risk analysis, user access reviews and provisioning and deprovisioning, according to Pathlock's 2025 Digital Transformation and Access Risk Report.
A question worth separating out:
Q: How can offboarding automation prove a leaver is finished?
A: Offboarding automation proves a leaver is finished by checking that the leaver state open is cleared only after accounts are disabled, tokens revoked, sessions terminated and any privileged access removed. The process should wait for confirmed completion events from the HR workflow, ticketing system or identity platform before closing the case.
👉 Read our full editorial: JML automation fails where movers, conflicts and exits diverge