This article helps you:
Learn how to use the approvals workflows for feature flags and experiments
Improve the governance of your experimentation program and decrease the risk of unintended changes by requiring approvals for critical changes to experiment configuration.
Experiment Approvals is only available to Growth and Enterprise customers.
Turn on approvals by going to Organization Settings > Experiment > Approvals.
Only users who have manager or admin roles can modify approvals settings.
Add the individual projects that you would like to require approvals for.
For each project, you can specify one of the following options:
Additionally, admin users can respond to pending approvals.
After approvals are enabled for a project, Amplitude recommends that you follow this approval process:
While the approval is pending, users can make additional changes to the flag or experiment configuration, enter or exit testing mode, or cancel the request at any time.
When the scheduled flag or experiment gains approval, the flag or experiment is considered live and requires approvals for critical changes.
When a flag or experiment is active, certain updates also require approval:
Field | Type of Change |
---|---|
Target Segments | Adding and removing segments, modifying conditions or bucketing. |
Variants | Any changes, including adding, renaming or removing variants. |
Variant Distribution | Any changes |
Exposure Event | Any changes |
Bucketing Salt | Any changes |
Sticky Bucketing | Enabling / Disabling |
When reviewing these approval requests, users can view the full list of changes in the approval banner.
When approvals are pending, the flag or experiment is locked. This prevents users with access from making other changes until the previous approval request is completed or cancelled.
September 17th, 2025
Need help? Contact Support
Visit Amplitude.com
Have a look at the Amplitude Blog
Learn more at Amplitude Academy
© 2025 Amplitude, Inc. All rights reserved. Amplitude is a registered trademark of Amplitude, Inc.