Before
HR or IT staff would likely review changed employee records, determine which employees were being offboarded that day, and move between collaboration and identity-management tools. They would look up each account, remove Slack access, suspend Google Workspace and Okta access, and send a status email manually.
How it works
- Retrieve changed employee records and evaluate each employee for offboarding scheduled for today.
- For qualifying employees, locate and remove the Slack account, then suspend access in Google Workspace and Okta.
- Send a detailed status email after the offboarding actions are completed.
Workflow details
- Employee discovery: The workflow runs a BambooHR custom report for employee records that have changed, retrieving identifying, employment, department, contact, supervisor, job title, and change-date information.
- Offboarding decision: It processes each employee record individually and checks whether the employee's offboarding is happening today. Only records that meet this condition continue through the offboarding sequence.
- Collaboration access removal: For qualifying employees, the workflow finds the associated Slack account using the employee's email address and removes the user from the workspace.
- Account suspension: It suspends the employee in Google Workspace, retrieves the corresponding Okta user, and suspends that Okta account to disable access across the configured identity systems.
- Status delivery: After the account actions are completed, the workflow sends an email containing the detailed offboarding status to the configured recipient.
What changed
Each qualifying employee record now triggers a consistent cross-system offboarding sequence. The date check, account lookups, access changes, and status notification happen automatically, with no human approval step defined in the workflow.
Work removed
Reviewing changed employee records one by one, deciding whether offboarding is due today, looking up Slack and Okta users, removing Slack access, suspending Google Workspace and Okta access, and composing and sending the offboarding-status email.
Expected outcome
The workflow is expected to remove roughly six recurring lookup, account-change, and notification actions per qualifying employee from the offboarding checklist.
