Approvals and trust levels

Every action an agent can take, such as sending an email, posting to Slack, creating a CRM record or changing a setting, has a trust level. The trust level decides whether the action waits for a person.

The three levels

• Always ask: every use pauses for a person's approval. Changing a setting and deciding at a process gate are always asked.
• Ask the first time: the default for most actions in connected tools, such as sending email from Gmail or Outlook, booking calendar events, posting to Slack, creating HubSpot or Pipedrive records, and saving to memory. The action waits for approval before it runs.
• Run when safe: routine, reversible work starts without waiting, for example analysing files in a Project's sealed sandbox.

Stricter, never looser

Each action comes with a default level, and two rules protect it:

• An agent may ask for a stricter level on a single task, for example asking for approval on something that would normally run by itself. It can never lower the level.
• Workspace owners and admins can make an action stricter for the whole workspace, but cannot set it looser than its default. In the settings, looser choices are disabled and say why.

Change the rules

Open Workspace settings -> Agent permissions:

• Before work begins sets whether CORA's plans pause for approval before she delegates.
• AI workers sets when CORA and each specialist may start routine work.
• Actions lists single capabilities, like saving information or updating another system.

Pick a level from the menu next to an item. The default is labelled, a dot marks a custom rule, and choosing the default again removes the custom rule. Only owners and admins can change these rules. Sensitive actions keep their own stricter rule, so the safer rule always wins.

Exact action previews

An approval is bound to what you saw. For a state-changing action, the approval shows the exact proposed change. A settings change, for example, shows each field's current and new value. Approving it approves those values only, and the action cannot widen the change afterwards.

When the approved action runs, CORA checks permissions again and checks that the old value is unchanged. If someone changed it after the preview was made, the task stops safely and a fresh proposal is needed.

You can approve or reject waiting actions in the chat where they were proposed or in More apps -> Inbox.