Approvals
Require sign-off from chosen people before a feature flag is turned on, turned off or changed.
Approvals stop a sensitive change from going live until the right people have agreed to it. When someone makes a change that a policy covers, the change isn't applied straight away. Instead it becomes a change request, and it's applied once enough approvers have approved it.
Approvals are set per project, under Settings → Project → Approvals. Only organization admins and owners can manage them.
Approvals are available on plans that include Change approvals.
What can require approval
A policy covers one type of action:
| Action type | What it covers |
|---|---|
| Enable feature flag | Turning a feature flag on. |
| Disable feature flag | Turning a feature flag off. |
| Update feature flag | Changing a feature flag's settings. You can limit this to changes in rollout percentage. |
Policies
To add a policy:
- Open Settings → Project → Approvals.
- Under Policies, select Add policy.
- Choose the Action type.
- Choose who can approve: Approver users, Approver roles, or both.
- Choose how many Approvals required: 1, 2 or 3.
- Optionally, choose who may skip approval altogether, under Bypass options: turn on Allow org admins and owners to bypass, or pick Bypass roles.
- Select Save.
In the same dialog, turn on Allow self-approval if the person who asks for a change may also approve it. They still need to be one of the approvers.
Conditions for updates
For Update feature flag, you can make a policy apply only to some changes. Under Require approval when, add the Rollout percentage field and choose a condition:
- changes: any change to the rollout percentage needs approval.
- new value is: approval is needed when the new value meets a threshold, for example a rollout above 50%.
- changes by: approval is needed when the value moves by more than an amount, for example an increase of more than 10%.
Without a condition, every update to the flag needs approval.
The policy list shows each policy's action, approvers, approvals required, self-approval and status. Use the menu next to a policy to edit or delete it.
Change requests
When someone makes a change that a policy covers, the app tells them that approval is required and creates a change request. Each approver gets an email asking for their sign-off.
To review requests:
- Open Settings → Project → Approvals.
- Under Change requests, filter by Status to find pending requests.
- Open a request from its menu to see what would change, then Approve or Reject it. A rejection needs a reason.
When the required number of approvals is reached, the change is applied automatically. The person who asked is emailed when their request is approved or rejected.
A change request can have one of these statuses:
| Status | Meaning |
|---|---|
| Pending | Waiting for approvals. |
| Approved | Approved, and waiting to be applied. |
| Applied | Approved and live. |
| Rejected | An approver turned it down. |
| Expired | Not decided in time. By default, a request expires after 14 days. |
| Failed | Approved, but the change could no longer be applied, for example because the flag was changed in the meantime. |
Can't find what you need? Contact support