# Set up Risotto by asking

Tell Risotto's Assistant what you want, and it builds it: access rules, departments, forms, runbooks and automations. Every change appears as an approval card showing exactly what will change, and runbook edits arrive as drafts with tracked changes.

[Book a demo](/demo)

## Say it the way you'd say it to a colleague

Risotto's Assistant takes the request in plain English and comes back with the change, ready for you to check:

- "Add an access rule for Figma: Editor access for 30 days, manager approval."
- "Create a Legal department for contract questions."
- "When Rippling reports a new hire in Engineering, add them to the Engineering groups in Okta."
- "Write a script that adds and removes people in our Sentry org, and use it on the Sentry Developer access rule."

[Runbooks](/product/runbooks) · [Automations](/product/automations)

## Code Mode for bulk work

Some jobs need hundreds of lookups, not one. In Code Mode, Risotto's Assistant writes a short TypeScript program and runs it in an isolated sandbox, scanning many tickets, users or records in one step and returning only what matters.

Reads run right away. Changes wait for an approval card that shows the code and every tool it will call.

## You decide how much the Assistant can do

Risotto's Assistant works inside the limits IT sets, and every action is logged under the person who ran it.

- **Ask first, by default.** Every change waits for approval.
- **Auto-accept when you're ready**, for non-destructive changes or for everything.
- **Tool rules always win.** A tool marked as needing approval asks every time, and script tools that write to your systems always need approval.
- **Tool approvals only go up.** The Assistant can add an approval requirement to a tool, and only a person can remove one.

[Security and trust](/security)

## For department supervisors, not only IT admins

Supervisors in HR, Finance, Legal or any department use Risotto's Assistant to build and change their own runbooks and ticket categories, within the departments they supervise and their own permissions. Admins keep org-wide settings.

[Solutions by team](/solutions)

## On an escalated ticket, it's AI Assist

When a request needs a person, Risotto's Assistant investigates the ticket and writes a plan your agent approves step by step.

[See AI Assist](/product/ai-assist)

## Frequently asked questions

### Can I set up Risotto by chatting with it?

Yes. Ask Risotto's Assistant for an access rule, a department, a form, a runbook or an automation in plain English. It shows each change as an approval card, and nothing saves until you approve it.

### Can the Assistant move my workflows from my current tool?

Yes. Describe a workflow, paste it in or attach a screenshot, and Risotto's Assistant builds the forms, approvals and runbooks to match, each waiting for your approval. [Deployment and pilot](/deployment)

### What is Code Mode?

Code Mode is how Risotto's Assistant handles bulk work: it writes a short TypeScript program and runs it in an isolated sandbox. Reads run right away; changes wait for an approval card that shows the code.

### Do I approve the Assistant's changes?

Yes. By default, Risotto's Assistant shows an approval card before every change. Admins can let some changes through automatically, but tools marked as needing approval still ask every time, and the Assistant can add an approval requirement to a tool but never remove one.

### Who can use the Assistant?

Risotto admins use the Assistant across the whole organization. Department supervisors use it within the departments they supervise and their own permissions.

## See the Assistant build a runbook live

[Book a demo](/demo)

Source: https://www.tryrisotto.com/product/assistant
