Docs · Concepts

Gates and approvals

A gated action requires a person before execution continues. The approver allows or denies the request.

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.

Authority classes

Policy puts every action in one of four classes. Observe reads without changing anything. Change is low-risk and runs within the policy the company grants. Sensitive is gated: it waits for a named approver in the app queue or in Slack. Outside authority is refused, or sent to the company as a decision it has to make.

After a change runs, Deixic reads the setting back and records a receipt with the result.

The queue of gated requests lives on Actions. Decisions land on the Activity timeline.

How to approve or deny Run compliance execution Evidence and activity