# Suspended Okta account review automation

When Okta suspends an account, Risotto reads that person's Okta log for the day before, signs them out of Google Workspace, posts what it found in #sec-alerts and opens a ticket for security.

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

## More like this

- [Locked Okta account follow-up automation](/library/automations/okta-locked-account-follow-up)
- [Suspected phishing report runbook](/library/runbooks/suspected-phishing-report)
- [Risotto and Okta](/integrations/okta)
- [How automations work](/product/automations)
- [The full library](/library)

## Frequently asked questions

### What starts the suspended Okta account review automation?

Okta suspending an account, through the "Okta account suspended" trigger, which carries the person's email, who suspended them and when.

### Which steps in the suspended Okta account review 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. You can make every change wait, or none.

### How do I build the suspended Okta account review 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/okta-suspended-account-review
