Approvals

What Henry does on its own, what it asks about first, and how you change that per tool.

Henry reads freely and asks before it writes. That is the default, and you control it tool by tool.

The default

• Reads run immediately. Searching your inbox, listing tickets, pulling a report: no confirmation.
• Writes stage a confirmation. Sending an email, creating a ticket, updating a record: Henry shows you what it is about to do and waits.
• Spending always asks. Anything that charges money or spends credits on your behalf requires a manual Confirm, every time. This is the one rule you cannot turn off.

What a confirmation looks like

Slack

A card posts below Henry’s message with Confirm and Cancel. When several actions of the same kind are staged in one turn, they combine into one card with Confirm all. The card also offers Confirm + always allow this tool and Confirm + always allow this integration. After you confirm, the card updates to show who approved it and Henry continues.

Microsoft Teams

An Adaptive Card with Confirm, Confirm all, and Cancel.

Web app

A card under Henry’s reply with Confirm, Always allow, and Approve all when there are several, plus Approve all & always allow.

Texting

Henry texts you what it is about to do. Reply YES to approve or CANCEL to drop it.

Agent Browser

When a browser task reaches something irreversible, such as placing an order or submitting a form, Henry stops and asks in the thread. An approval covers exactly that one action with those exact details.

You are never asked to approve items one at a time. Many calls of the same tool in one turn become one card and one click.

Changing the default

Every tool has a setting: Run automatically or Ask for confirmation. You can also turn a tool off entirely. Change it in three places:

1. On the card. Click an “always allow” button when you confirm, and that tool (or the whole integration) runs automatically from then on.
2. On the Integrations page. Open a connected account, go to the Tools tab, and set each tool. Tools are labeled Read or Write so you can see what you are allowing.
3. On a task. Scheduled tasks are approved once, at activation. After that their runs never stage cards. See Activating and running tasks.

A good pattern: leave writes on Ask for confirmation for the first week. Once you trust what Henry does with a tool, switch it to Run automatically from a card.

Who can approve

Only the person Henry is acting for can approve their own staged actions. Approvals are tied to your identity on every channel, which is why linking your Microsoft account matters in Teams and why texting is verified per person.

An approval cannot be reused. If Henry proposes a different action, or the same action with different details such as a different amount or recipient, it asks again.

Scheduled tasks

Tasks work differently because nobody is there to click. When you activate a task, Henry lists every write tool it will use and you approve them once. Runs then execute those tools unattended. If a run needs a tool you have not authorized, that step is blocked, the run reports it, and you can authorize it from the task page for future runs.