Platform / Joiner · mover · leaver
Joiner · mover · leaver
The gap between someone leaving and their access leaving — closed.
Case by case
Someone resigns on Friday at five.
HR is the trigger. Applications, admin credentials, network access and their agents go together — after you preview exactly what will change.
→ Minutes, not next Thursday.
Someone moves from finance to sales.
The old access is removed, not just the new access added — which is how toxic combinations quietly accumulate.
→ A move is not a promotion in access.
A manager grants access outside the process.
Drift is detected, flagged and put back. You are told it happened.
→ The first good quarter survives.
Under the hood
What you actually get
HR is the trigger; five ways in and four ways out make it real.
Five inbound channels
SCIM push, HMAC-signed webhooks, CSV or JSON file upload, scheduled database polling and SFTP file pickup — whichever your HR system can emit.
Joiner, mover, leaver policies
Triggers matched on department, role and title. Joiners get a baseline, movers lose the old access as the new is added, and leavers are fully deprovisioned.
Provisioning adapters
Adapters for LDAP, SCIM, REST and host agents fan a grant out to the target system, and reverse it on departure.
Leaver network cut
Offboarding deactivates the account, revokes entitlements, deprovisions downstream and tears down live network sessions over RADIUS change-of-authorization.
Dry run and re-evaluation
Preview the exact changes before anything is written, choose staged approval or automatic execution, and re-apply active policies nightly to catch drift.
Felt first by: IT operations, HR systems owners, and audit. · Take this on its own — every edge speaks the standards your estate already speaks, so replacing it later stays cheap.