Concepts

Read-first and human approval

AI may read what a role allows. It may not change anything without a person saying yes.

Read-first

Every connector starts read-only. Write tools are added one at a time, per client and per tool, only after you agree them.

What needs approval

Any write or action: updating a record, sending a message, deleting, or moving money. Each write tool has a risk level, an approval rule and an approver role agreed before it goes live.

How approval works

1. The agent's action is paused, not run.
2. The approver gets a request with the context: who asked, which tool, what will change.
3. The approver approves, declines or edits the request.
4. If nobody answers in time, the request is declined.
5. The decision is written to the audit trail.

Two-person approval

Approval rules, including any requirement for a second approver (maker-checker), are agreed for each workflow.

Where approvals arrive

Approval channels and routing are agreed during onboarding. Each request identifies the action, the person requesting it and the decision required.