People Lifecycle
Joiners, movers and leavers — orchestrated and evidenced. Access granted on day one and revoked the moment it should be, for contractors and vendor staff as much as employees.
The access that arrives on time and leaves on time
Orchestration and evidence for every joiner, mover and leaver — built around the populations where access actually goes wrong.
Roles, not people
Access, ownership and approvals resolve through a role roster, never a named person. When someone leaves or an MSP restaffs, one row changes and everything downstream stays valid.
Non-employees are first-class
Contractors, temp labor, interns, seasonal workers and vendor staff with system access are subjects in their own right — not an edge case — because that is exactly where ghost accounts collect.
Sensitive exits, sequenced right
An involuntary exit revokes access before any notification goes out, with the event's visibility restricted. The sensitivity is built into the workflow from the start, not bolted on afterwards.
Evidence over automation
Every grant and revocation is logged with the accountable role, timestamp and source. This is orchestration and evidence — no write access to your identity providers required — so the audit trail is the product.
A closer look
The order things happen in
An exit is not one action, it is a dozen in a particular order. Get the order wrong on a sensitive departure and the person is told before their access is gone.
Each entitlement carries its own revocation urgency, and the workflow turns that into dated tasks — immediate, same day, or scheduled — owned by the role accountable for that system. Hardware gets a recovery task that has to be closed. Data gets a disposition task.
On a confidential exit the notification is created blocked, waiting on the immediate revocation, and dated after the last one. It cannot go out early because the workflow will not let it, not because somebody remembered.
Walk a joiner and a sensitive leaver through the workflow and see the record each one leaves