Review and approve actions

Approvals separate a proposed action from controlled execution. Approval is available when the APPROVALS feature flag is enabled.

Required permissions:

• approvals:manage to approve or reject actions.
• runs:execute to execute approved actions.

Administrators, Managers, and Scrum Masters receive both permissions by default.

Open the approvals inbox#

1. Select Approvals in the sidebar.
2. Review pending runs in Approvals Inbox.
3. Select a run to open Review Run <id>.
4. Inspect each action’s target, type, proposed change, and context.

Approve one action#

1. Confirm that the action targets the intended project and item.
2. Review before and after state when provided.
3. Select Approve for that action.
4. Confirm that its approval state changes from proposed to approved.

Reject one action#

1. Select Reject.
2. Enter a reason when the screen requests one.
3. Confirm that the action changes to rejected and will not be selected for execution.

Approve or reject a run#

Bulk controls can approve all remaining proposed actions or reject the run. Use bulk approval only when you have reviewed every included action.

An already rejected run cannot be executed. A run with no approved actions also cannot enter execution.

Execute approved actions#

The execute endpoint checks workspace state, plan eligibility, run state, and approved action count. A live run requires a plan that permits live mode and a workspace that is not suspended.

If the API returns HTTP 403, your role lacks the required permission. Ask an organization administrator to assign the appropriate role or delegated permission; do not weaken execution safeguards to work around the denial.

Related guides: Execution safety and Roles and permissions.