Stevin Manual/Features/Approvals Draft preview Updated November 19, 2026

Approvals

Stevin asks before it changes anything: which actions need approval, where you approve, who can approve, and how to let a trusted action run automatically.

Why approvals exist#

Stevin can really act in your tools, so risky actions need a person to check them. Approvals guarantee one thing: it does not change your data without consent.

Three kinds of action#

Every tool Stevin can use is classed by its effect, and the rules differ:

Class Examples Default rule Can it be made automatic
Read Look up an issue, read a document Runs directly Not applicable
Write Create a record, send a message, change a field Asks first Yes
Delete and irreversible Delete a record, delete a file Always asks first No

A delete cannot be undone, so it always pauses for approval, and nobody can change that.

What an approval request looks like#

Stevin stops and explains what it intends to do: which tool, on what, with what content. It acts only after a person confirms. You can decide in any of these places:

  • In your chat tool: on the approval card in the conversation.
  • In the console: the task waits under Needs review on the Activity page.
  • In a voice conversation: say "yes" or "no", or use the buttons on the Live page.

After you decide#

  • Approve: Stevin carries out the action and continues with the following steps.
  • Approve & always allow: approves it and lets this kind of action run without asking in future.
  • Reject: the action is not carried out and nothing is changed. A rejection is not remembered as a rule: the next time a similar action comes up, Stevin asks again.

A request that nobody handles keeps waiting. It is never carried out automatically.

Who can approve#

  • The person who started a task can approve the actions in their own task, as long as their role is allowed to approve tasks.
  • Some actions are escalated beyond the person who asked. An escalated action must be decided by an Admin or the Owner who is not the person who asked. That person can still reject it.
  • By default, Members approve their own tasks and Admins and the Owner approve anyone's. Viewers cannot approve. Change this with the Approve what a task is waiting to do permission on the Permissions page.

Being asked less often#

By default every write is asked about. For tools and actions you already trust, there are three ways to cut the questions:

  • Per action, as you go: choose Approve & always allow on a request.
  • Per tool: on an MCP server, an admin sets a write tool to Runs directly instead of Asks first.
  • Per role, for conversation-driven setup: on the Permissions page, an admin chooses how often Stevin asks before it installs an MCP server or switches on one of its tools from a conversation: ask every time, ask for anything new, or never ask.

Start with asking every time and loosen gradually once you trust its judgment for a given action.

Approvals in automations#

When an automation reaches an action that needs approval, it also stops and waits. An automation meant to run unattended should either use only read tools or have the write tools it needs set to run directly beforehand.

The record#

Every approval request and its outcome is part of the task it belongs to, and can be reviewed in Activity.

Last updated November 19, 2026 Suggest an edit