# BambooHR offboarding automation

When BambooHR marks someone terminated, Risotto ends their Okta sessions, suspends their Google Workspace account, moves their Drive files to their manager and tells IT.

[Book a demo](/demo) · [See the library](/library)

## More like this

- [Rippling new hire onboarding automation](/library/automations/rippling-new-hire-onboarding)
- [Revivn device return runbook](/library/runbooks/revivn-asset-retrieval)
- [Risotto and BambooHR](/integrations/bamboohr)
- [How automations work](/product/automations)
- [The full library](/library)

## Frequently asked questions

### What starts the BambooHR offboarding automation?

BambooHR marking an employee terminated, through the "BambooHR employee terminated" trigger, which carries their email, name and last day.

### Which steps in the BambooHR offboarding automation wait for approval?

It asks for approval on destructive changes, as the dashboard puts it: creates and updates run unless a tool requires approval, and deletes and revokes wait for an admin. So ending their Okta sessions waits for an admin to approve it.

### How do I build the BambooHR offboarding automation in Risotto?

Describe it to Risotto's Assistant: what starts it and what should happen. The Assistant builds it from the systems you've connected and shows you each change before it saves.

Source: https://www.tryrisotto.com/library/automations/bamboohr-termination-offboarding
