Review and approve changes
Work the queue of proposed changes, each with its risk tier and the reason it's waiting.
The Approvals page holds every proposed change that the safe-apply policy didn't auto-apply — plus any auto-approved change the apply worker demoted because it was no longer safe. This queue only ever holds copilot decisions; a dashboard action you confirm yourself applies directly.
In the dashboard
Open Approvals in the account. Each row shows the change, its risk tier, and the policy reasons it's here. Apply it, or reject it. Confirming a change in the dashboard counts as an operator decision and applies right away.
Over MCP
A human at an MCP client drives approvals with dedicated tools:
List what's waiting
Call gads_list_pending_actions and present each with its risk tier and policy reasons.
Decide
gads_approve_action applies it, gads_reject_action drops it, gads_revert_action undoes an applied change
where the prior state was snapshotted.
List the pending actions. For each, show the risk tier and why it's queued, then ask me to approve or reject.Approvals are the human's call. The copilot cannot approve its own proposals — the approval tools exist only on the MCP bridge, where you're driving.