Sauce Labs · Offboarding workflow
Employee offboarding, end to end
A leaver crosses six stages: trigger, identity, devices, security and data, collaboration tools, verification. This page walks through the workflow with a sample case. Pick a case, switch the path, and step through the six stages.
88 of 140apps removed automatically (63%)
45 → 15-20 minIT time per offboarding
3SOC 2 audit cycles supported in Vanta
6stages, one tracking ticket
Interactive walkthrough
A walkthrough, not a live system. Sample data, generated names and ticket IDs. The 88 of 140 figure is estate-wide; each case uses its own subset.
Stage 01 / 06Ready
0:00Simulated clock
0/0Apps closed
0Manual exceptions
0/3Verification checks
Activity logno ticket
- Idle. Start the walkthrough to step through the six stages.
Design decisions
- Okta users are suspended, not deleted. This keeps the audit trail for SOC 2. Deleting a user breaks the SCIM link and makes a rehire harder.
- Druva backup runs before license removal. Once the Google Workspace license drops, the data is no longer reachable, so the backup has to land first.
- Every offboarding gets a Jira ticket automatically. The workflow creates it when it starts, so there is a record without anyone remembering to open one.
- Windows wipes wait for the device to connect. The JumpCloud wipe runs at 45 days and escalates to a Slack channel so IT can make sure the device checks in.
Orchestration started in BetterCloud and later moved to Okta Workflows. Jira was the IT helpdesk and held the tracking ticket. Apps that could not be automated were tracked from a Google Sheet.