Approvals Across the Product
Approval gating isn't just the chat toggle — here's every place it can show up.
Auto mode in chat is the approval setting you'll run into most, but it isn't the only place Pushable can pause and ask before an action runs. Approval gating exists in three separate places, and each one is controlled independently:
| Where | What it controls | Where it lives |
|---|---|---|
| A conversation | Whether the agent asks before it takes any action that changes something in that chat | The Auto mode toggle in the conversation |
| An individual tool | Whether that specific action always pauses for approval, no matter what a conversation's Auto mode is set to | That tool's own settings, under Tools |
| A trigger or schedule | Whether an unattended run executes right away, or pauses and waits for you to approve a sensitive action | The trigger's or schedule's own approval setting, under Triggers or Schedule |
Tools That Always Require Approval
Some tools can be individually marked so that they always require approval when an agent uses them — even in a conversation that's running in Auto mode. This is separate from the per-conversation toggle, so it stays in effect no matter which conversation the tool is called from.
Triggers and Scheduled Runs
Runs that happen with no one watching — like a trigger firing off an incoming event, or a schedule kicking off at its set time — always execute automatically by default, since there's no one present to approve anything in the moment. If you want a trigger or schedule to pause for sensitive actions instead, use its own approval setting rather than relying on chat's Auto mode, which only applies to conversations.
See Managing Triggers and Approvals on Scheduled Runs for how to turn that setting on for a specific trigger or schedule.