Offboarding
Offboarding that closes every door on the last day
Offboarding is where access governance is won or lost. A leaver who keeps a login is one of the most common — and most avoidable — security findings there is, and “we think we got everything” is not an answer an auditor accepts. This is a practical look at IT offboarding: revoking access on time, making sure someone picks up the work the leaver owned, and proving both happened.
Why lingering access is the classic gap
Deprovisioning fails quietly. Someone remembers the obvious apps — email, Slack — and misses the vendor portal, the shared admin account, or the system where the leaver was the owner. Nothing breaks on the last day, so no one notices until an access review, an incident, or an auditor asks “show me this person’s access was removed.” The fix isn’t heroics; it’s a scheduled, tracked process where every grant is accounted for.
Scheduled revocations, timed to the last day
Useboards schedules each revocation against the leaver’s last day and cuts access off at 5pm in their own timezone — so a departing contractor in another region doesn’t keep access for an extra working day. The offboarding scan pulls everything the person can reach across your catalog, turns each into a tracked deprovisioning action, and won’t mark the offboarding complete until the last day has passed and every item is done.
Someone has to inherit the work
Revoking access is only half the job — a leaver often owns systems, approvals, and responsibilities that can’t just vanish. Useboards routes a replacement ticket to the owner of each affected entity (the system or resource owner, not a buddy — that model was deliberately removed) so a named, accountable person picks up what the leaver held. What a good offboarding accounts for:
- Access to every in-scope system, revoked and tracked — not marked done on trust.
- Timing tied to the last day, cutting off at 5pm in the leaver’s timezone.
- Replacement tickets routed to each entity’s owner so ownership and approvals move to someone real.
- Gated completion: the offboarding closes only when the last day has passed and every item is done.
For-cause exits and the audit trail
Not every departure can wait for a schedule. For a termination or a compromised account, “revoke all now” cuts access immediately rather than at the scheduled cut-off. Either way, every revocation, replacement ticket, and completion is written to an append-only, tenant-isolated audit log — so when an access review or an auditor asks whether a leaver was fully deprovisioned, the answer is a timestamped record, not a memory.
Frequently asked questions
When should access be revoked during offboarding?
A common practice is to remove access by the employee’s last working day, and immediately for for-cause terminations. Useboards schedules revocations against the last day and cuts access at 5pm in the leaver’s timezone, with a “revoke all now” option for immediate exits.
What happens to the systems a leaver owned?
Useboards routes a replacement ticket to the owner of each affected entity so a named person inherits the ownership, approvals, and responsibilities the leaver held. It routes to the entity owner rather than a buddy — that intermediary model was removed because owners are the accountable party.
How do we prove offboarding was completed?
Every revocation and replacement ticket is a tracked action, and the offboarding only reaches completion once the last day has passed and every item is done. All of it is recorded in an append-only, tenant-isolated audit log you can show during an access review or audit.
Can we handle an immediate, for-cause termination?
Yes. “Revoke all now” cuts access across in-scope systems immediately instead of waiting for the scheduled last-day cut-off — for terminations or a suspected compromised account — while still recording each revocation in the audit log.
Related
Close every door on the last day
Scheduled revocations, owner reassignment, and an audit trail that proves it.