# Flag and Experiment Approvals Workflow

After a successful closed beta, approvals is going GA. Customers can now require peer approvals or approval by a limited number of users for their projects to start or schedule flags and experiments and apply changes to critical fields.

Source: https://amplitude.com/en-us/releases/flag-and-experiment-approvals-workflow

---

<!--$-->

ExperimentSep 22, 2025

[\[All updates\]](/releases)

### Flag and Experiment Approvals Workflow

Shelly Wang

**Description:** After a successful closed beta, approvals is going GA. • Customers can now require peer approvals or approval by a limited number of users for their projects. • When enabled, approvals are required to: ◦ Start or schedule flags and experiments ◦ Apply changes to critical fields in live flags and experiments.

**Why:** • As more teams adopt experimentation, the need to ensure quality and oversight grows. Without an approval mechanism, companies face coordination issues, last-minute surprises, and a lack of accountability. This is especially critical in regulated industries or high-stakes product areas. • This was a highly requested feature by experiment customers.

**Where:** Set up approvals in Org Settings > Experiment > Approvals.

**When:** This will be released this afternoon for all Growth and Enterprise Experiment customers.

**Useful Resources:** [Help docs](https://amplitude.com/docs/feature-experiment/managing-flags-and-experiments-with-approvals).

<!--/$-->
