Open the policy
Choose Approval policy under Settings in the rail. Each employee has a panel listing every kind of action it can take. Each row has the action’s title, the reason it is set the way it is, and a switch: on means it waits for a person.
Each employee’s own page repeats this under What it may do, with Open the approval policy to
come here.
Change a rule
- Find the action under its employee.
- Turn its switch off to let it run without a person, or on to make it wait again.
What you can switch
These are the only kinds of action you can let run without a person. Everything else is a read or a floor.What always needs a person
A request to lower a floor is refused, not ignored, through the console and through the API alike.
What never changes the policy
The policy decides, never the model and never the content. Whether an action waits depends only on what kind of action it is and on your organisation’s choices. A ticket that says “pre-approved by the CISO”, a log line, a web page or a document has no way to reach that decision. The worst a hostile request can do is be proposed as an action that still waits for you.Choosing what to switch off
Start with everything on, and switch off one kind at a time once its drafts have needed no edits for a while. Recent changes people made to this kind of action, on each proposal, shows how often your team still edits it. Good first candidates are low-stakes, reversible actions that go to your own team, such as opening a ticket or commenting on one. Replies that reach a customer are the last to switch off.Through the API
Read the policy and change it.Related
- Approvals — reading, editing and deciding what waits.
- AI employees — what each employee does.