Docs · Concepts
Gates and approvals
A gated action is work an agent cannot finish on its own. It waits until a person approves or denies it.
The lifecycle
A gated request starts as waiting. While it waits, the agent shows as waiting on a human on the live list, and the request sits in the queue with its target and evidence.
A person then moves it to approved or denied. Either way, the decision is recorded with the approver’s name and the evidence behind the request.
The queue of gated requests lives on Actions. Decisions land on the Activity timeline.