Identity lifecycle management

Identity lifecycle management ties access to employment events. When someone joins, they get the access their role calls for without a week of tickets. When they change role (the mover case), their access is re-decided against the new role, not stacked on top of the old one. When they leave, everything goes, everywhere, on the day it should.

The mover and leaver cases are where it breaks

Joiner automation is the easy third: most tools can create accounts. Movers are harder, because the safe-feeling default is to add the new role's access and quietly keep the old, which is how ten years of tenure becomes ten years of accumulated grants (privilege creep by process). Leavers are the sharpest risk: disabling the identity-provider login does not touch the SaaS accounts, API keys, and shared credentials that were never connected to it. Whatever survives offboarding becomes an orphaned account.

What good looks like

A working lifecycle reads events from the HR system as the source of truth, maps each role to entitlements rather than app seats, and executes across every connected system, with the leaver case proven by a report of what was revoked, not assumed. That end-to-end shape is what Ploy's lifecycle page walks through.