Every step to securely offboard a departing employee across Microsoft 365 and Google Workspace — and how Passage runs the whole list as one gated, provable workflow.
A checklist tells a human what to do; it doesn't do it, and it doesn't prove it was done. The failure mode is always the same: a step gets skipped under time pressure, an account stays enabled, and months later an audit — or a breach — finds it. Passage turns this exact checklist into a leaver run: automated steps execute the disable/revoke/reclaim actions, human steps (device, mailbox) are tracked to completion with an owner, and a closure gate refuses to mark the run complete until every critical step is done or explicitly waived with a reason. See offboarding software for the full picture.
Each completed run emits a hash-anchored evidence record mapped to the access-control and termination controls auditors ask about — SOC 2 CC6.x, HIPAA §164.308(a)(3), NIST 800-171 3.1.x / 3.5.x, NIST CSF PR.AA, ISO 27001 A.5.18. You did the offboarding anyway; now it counts as audit evidence too. See the compliance mapping.
Disabling the account and revoking active sessions, done together. Disabling alone can leave existing tokens valid for a window; revoking sessions invalidates them so the user is truly locked out at once.
Disable first, delete later (if at all). Disabling preserves the mailbox, files, and audit trail while immediately blocking access. Many organizations convert the mailbox to shared and retain the disabled account for a retention period before deletion.
Local-first, no card, no implementation call.
Start free