Approval request settings
Overview
This topic explains how to customize the settings for your approval requests.
Approval settings
You can customize how approval requests are managed and enforced by making changes in an environment’s Approval settings.
You can customize who can approve a request and how many approvals are required before a requestor can apply a change. These settings can be useful when you want to use approval requests to track the changes you make to a flag, but don’t want to delay applying those changes based on who has approved them.
For example, you can prevent a proposed change from being applied if any reviewer declines an approval request for the Production environment. Or you may allow anyone, including the person making the approval request, to approve and apply a proposed change in the QA environment.
Segment changes affect only the environment in which the segment is defined.
Some flag changes, like turning targeting on or off or changing targeting rules, affect the flag only at the environment level. Other flag changes, like editing flag variations, affect the flag at the project level. If you make a change to a flag variation that affects an environment with approvals required, then the change will trigger an approval request. To learn more, read How required approvals work for flag variations.
Enterprise customers can customize an environment’s approval settings in the “Edit environment” panel for that environment. To learn more, read Configuring approvals for an environment.
The following actions do not trigger an approval request:
- Changing a flag’s name
- Changing a flag’s maintainer
- Changing a flag’s description
- Changing a flag’s tags
- Creating a flag
- Archiving a flag
- Deleting a flag
- Changing a segment’s name
- Changing a segment’s description
- Changing a segment’s tags
- Creating a segment
- Deleting a segment
To prevent members from making these kinds of changes, you can configure and assign custom roles that deny these actions. To learn how, read Custom roles.