How approvals work in chat
When a protected action comes up, the session pauses and asks. The mode does not remove approvals: Ask mode writes nothing, but a protected connector or tool read still asks, while reads of the workspace itself never do. Allow once and Deny are the visible buttons. Open the arrow next to Allow once for Always allow or Always deny; each is labelled with the tool’s name and sets a standing decision. Pending approvals appear in the Waiting on you strip above the composer until you answer them, and the transcript marks the waiting turn.Before you approve a tool
- Confirm the named tool matches the task.
- Check the target: organization, repository, channel, document, or account.
- Prefer one-time approval while you are still learning a workflow.
- Deny requests whose purpose or scope is unclear.
- Verify the result on the provider after a write action.
Change your mind later
Standing decisions are listed under Capabilities → Tools. Filter them by Always allow, Always ask, or Always deny, or search by tool name. Each row has a Revoke control that takes the decision back, so the next request asks again.Keep the layers separate
- Modes are the permission contract for the whole session: what Ask, Plan, and Agent may change.
- Sessions and modes shows approvals in the flow of a session.
- Connection authorization decides what the connected provider permits; see Connect apps.
Good to know
- Skills, agent instructions, and workspace settings shape behavior. None of them grant provider access.
- The four approval choices are Allow once, Deny, and, under the arrow beside Allow once, Always allow and Always deny for the named tool.
- Standing decisions live under Capabilities → Tools, where each row has a Revoke control.
- Pending approvals wait in the Waiting on you strip above the composer until you answer them.