Approvals
What happens when an automation needs a person, and the four places you can answer it.
An automation can include a step that stops and asks a person before the rest of it runs. When it reaches that step, the run pauses at Waiting for you and an Approve or Reject card is posted to the members chosen for it.
Until someone answers, the run stays paused. Nothing after that step happens.
Four places to answer
The same approval can be answered from any of these, and answering in one resolves it everywhere:
| Where | When it is the natural place |
|---|---|
| The card in your feed | You are already reading the feed |
| The feed item's own screen | You tapped the notification, which opens here |
| The automation's detail screen | You went looking for what is blocked |
| The run screen | You are reading the run and want to unblock it |
All four do the same thing, and answering is what lets the run continue.
Notifications
An approval request sends a notification. Tapping it opens the request directly, including when the approval belongs to an organization other than the one you currently have selected. See Notifications.
Once it is resolved
The card stops offering buttons and shows the outcome instead: Approved, Rejected, or Expired where nobody answered in time. That applies whether you answered it, a colleague did, or it timed out.
Who can answer
Owners, admins and users can answer an approval addressed to them. Guests cannot, which is also why guests do not get the Automations tab. See Roles and access.