Approvals
Approvals introduce a manual checkpoint into your deployment workflows. When enabled, specific actions require explicit approval from authorized users before Axio proceeds with the operation.
Why approvals?
They help teams enforce change control, meet compliance requirements, and reduce the risk of unintended or unauthorized changes in production environments.
How it works
When a workflow reaches an approval step, Axio pauses the execution and creates a pending request. Authorized users receive a notification and can review the details before approving or rejecting the request.
Workflow reaches
approval step
→ approval step
Request created &
notified
→ notified
User reviews
the request
→ the request
Approved /
Rejected
→ Rejected
Workflow
continues
continues
Approval request lifecycle
Requests can be in one of the following states.
| State | Description |
|---|---|
| Pending | The request is waiting for action from an approver. |
| Approved | The request was approved and the workflow can continue. |
| Rejected | The request was rejected and the workflow stops. |
Who can approve?
Approval permissions are managed using Axio roles and groups.
- Approvers must have the required permission for the stack or environment.
- Multiple approvers can be required, either sequentially or in parallel.
- You can configure approver groups instead of individual users.
