Approvals
Actions that need a person wait in Approvals. An approver, admin or owner approves or denies each one, with an optional comment.
What waits hereLink to What waits here
A worker's action waits for a person when the autonomy mode, the Always ask list or a policy says so. Examples are a merge, a deploy, a message outside your organization, a spend above your limit and a hire.
DecideLink to Decide
Open Approvals. Each card says what the worker wants to do, why, and who can decide. Select Approve or Deny, with an optional comment. A critical action asks you to confirm again.
You can also decide from the CEO conversation and, when it is connected, with one tap on WhatsApp.
Who can decideLink to Who can decide
Owners and admins can always decide. An approval can name a role; by default it is approver. Members and viewers cannot decide.
StatusesLink to Statuses
Pending, Approved, Denied and "Past its expiry". An approval that is not decided in time expires.
When the kill switch is engagedLink to When the kill switch is engaged
Engaging the kill switch withdraws approvals that are not yet acted on. They must be given again after the release.
Checked against the product on 2026-10-05.
Was this helpful?
Related articles
- Autonomy modesThe autonomy mode decides how much workers do before they ask you. Auto is the default: internal work runs at once, and outside or risky actions wait for you.
- The Always ask listSome actions always wait for a person, whatever the mode or risk tier. By default the list has seven items.
- Risk tiersEach action has a risk tier: none, low, medium, high or critical. The tier and your autonomy mode decide whether a worker acts, acts and tells you, asks, or is stopped.
- EscalationsAn escalation is a decision a worker could not make alone. It comes with the options and the evidence the worker gathered. You answer, and the work goes on.