Skip to Content

Guides

Approvals and change requests

Make an environment reviewed: everyone asks an admin for changes to what it serves, and admins approve or send them back.

3 min read

Some changes to a live environment deserve a second look: starting a test in production, reallocating a running one, pointing it at another audience. An admin can make an environment reviewed, and then everyone else asks for those changes instead of saving them.

Most teams review production and leave develop and staging open, where speed matters more than a second opinion.

Turning it on

Admins find the switch under Settings → Approvals: Changes need an admin's approval, per environment. Only admins can change it.

  • Turning it on doesn't touch what is already live, and requests that are already waiting keep waiting.
  • Turning it off lets everyone save directly again; requests still open can be approved or sent back meanwhile.

What needs approval

Anything that changes what the environment serves:

  • a test's or flag's state: starting, stopping, finishing or archiving an active one;
  • a live test's or flag's slug;
  • a test's allocation, default value, and its options' splits and values, including a multi-variant test's dimensions;
  • a flag's options' splits and values;
  • which audience a test or flag uses;
  • deleting one that is active;
  • creating a test or flag that is already active, and copying tests into the environment: only admins do those.

What stays free: creating and editing drafts, renaming, icons, goal events (they change what is measured, not what is served), and audiences that no active test or flag in a reviewed environment uses.

Asking

Without the right, saving such a change asks for approval instead: an optional note, then the request waits. The test, flag or audience shows In review in its list and on its page, with what is served now next to what is proposed, who asked, when, and their note.

A subject has one request at a time: asking again replaces it, so your admin always sees the latest version.

Reviewing

Admins find the request on the subject and in the review list, and can:

  • Approve: the change goes live right away, applied as the approving admin and recorded for the person who asked.
  • Send back, with a reason: nothing changes, and the asker sees why on the subject until they ask again or dismiss it.
  • The asker, or an admin, can withdraw it.

If what the change was asked against moved on meanwhile — an admin changed the test directly, or another request was applied — it shows Changed since, and approving is refused until the asker asks again. Nobody approves a change against a state they never saw.

Audiences

Audiences belong to the space, not to one environment, so an edit reaches all three at once. Editing one that an active test or flag uses in a reviewed environment needs that environment's approval.

Agents and MCP

The agent API and the MCP server follow the same rules: a write that needs approval answers review_required, with the change to send to askForChange, and an admin can list, approve, send back and withdraw requests. An agent may turn production's review on, never off: turning it off is a person's click in the dashboard.

Webhooks

test.review_requested, test.review_closed, flag.review_requested and flag.review_closed, with the request in data.request. See Webhooks.

Doing it later

To apply a change at a time instead of now, give it one: see Scheduled changes and ramps.

On this page

Marks in the margin

  • Note
  • Watch out
  • Updated

Scribes marked doubtful lines in the margin. That practice is called obelism.