# Okta support runbook

For login, SSO and MFA questions, Risotto checks your own docs first, then Okta's help site, and replies with steps. Lockouts and admin changes go to IT.

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

## More like this

- [Okta group access request runbook](/library/runbooks/okta-group-access-request)
- [Okta password reset runbook](/library/runbooks/okta-password-reset)
- [Okta account recovery with risk checks](/library/runbooks/okta-account-recovery-with-risk-checks)
- [Manager-requested offboarding runbook](/library/runbooks/manager-requested-offboarding)
- [How runbooks work](/product/runbooks)
- [Risotto and Okta](/integrations/okta)
- [The full library](/library)

## Frequently asked questions

### When does Risotto use the Okta support runbook?

When an employee's request matches the runbook's description. The template starts with "can't log in, SSO not working, single sign-on issue, MFA not working", and you can rewrite it to match how your people ask, or apply the runbook to every request in a department.

### What does the Okta support runbook need?

Your docs connected to Risotto, such as Confluence, Notion or Google Drive. The template also sets up a web search tool that can only search support.okta.com. Research Answer and Escalate are built into Risotto.

### Can I change the Okta support runbook?

Yes. Start from the template in the runbook editor, then rewrite the steps in plain English, add tools with #, and choose which inputs you set and which the agent fills in. It runs once you publish it.

Source: https://www.tryrisotto.com/library/runbooks/okta-support
