Skip to main content
When you make changes to a Feature Flag, a Config, a Constant, a Saved Group, or an SDK Connection in GrowthBook, those changes go through a publishing workflow before they reach your users. This page covers the full lifecycle: drafts, publishing, revisions, merge conflicts, and optional approval flows. The same revision and approval model applies to all of them. The sections below describe the flow for Feature Flags first. The Saved Groups, Configs and Constants, and SDK Connections sections call out where their experience differs, and Publishing Several Changes Together covers publishing drafts of different kinds as one operation.

Drafts and Publishing

When you change a feature’s definition (e.g., the default value or rules), GrowthBook automatically creates a new draft revision. This draft is unpublished and only visible within the GrowthBook UI, not to your users. Continue adding changes to the draft, and when you’re ready, publish them all at once with an optional commit message. Draft Modal

Revisions

Once published, a revision becomes locked and can no longer be changed. To undo changes and revert to a previous state, use the Revision dropdown to select the version you want to revert to, then click Revert. You can review the changes that will be applied before submitting.
Feature Revisions

Merge Conflicts

Your draft can diverge from the live version of a feature if someone else publishes changes while you’re still editing. GrowthBook can merge some changes automatically (e.g., if you change a rule in “dev” and someone else changes a rule in “production”). For changes that can’t be resolved automatically, you must fix the conflicts before publishing your draft. The conflict resolution process works similarly to version control systems like Git. For each conflict, GrowthBook shows a diff and lets you choose how to proceed. In the example below, the Default Value was set to foo when you first created your draft. In your draft, you changed the value to bar. At the same time, someone else published a new version, changing the value to hi!!. So, now you have to choose which change you want to keep.
Resolve Conflicts

Approval Flows

With Approval flows, you can require approval before publishing any change to an existing feature flag. Approval flows help reduce errors by making sure changes to features have been viewed and approved by someone else in your organization.

Settings

Enable Approval Flows for your organization under Settings → General → Approval Flows. Approval requirements apply per Project: the All Projects tab sets the default rule, and + Project override adds a rule for specific Projects that replaces the default for them. Each Project’s own settings page also shows its effective rule under an Approvals tab. Each rule for Feature Flags, Configs, and Constants has the following options:
  • Specific environments — Only changes affecting these environments require approval. Leave blank to require approval in all environments.
  • Required approver teams — A draft cannot publish until someone from one of these teams approves it. Anyone eligible can still approve alongside them. Leave blank to accept an approval from anyone with Review access.
  • Reset review on changes — If a draft is modified after being approved, the approval is revoked and a new review is required before publishing.
  • Block contributors from self-approving — Prevents anyone who edited a draft from approving it. The draft’s creator can never approve it, regardless of this setting.
  • Allow approve & publish in one step — Adds an “Approve & Publish” option so reviewers with Publish access can approve and publish a draft together.
  • Require approval for — Changes to rules, values, and prerequisites always require approval. Optionally also require approval for enabled environment changes (kill switches) and for metadata changes (description, owner, project, tags, etc.).
The Global section below the rules holds settings that span every rule. One of them concerns Targeting Projects:
  • Apply approval requirements from Targeting Projects (on by default) — A Feature Flag delivered into other Projects must also satisfy those Projects’ approval rules before publishing. A Targeting Project with a rule of its own must additionally be approved by one of its own reviewers, and those reviewers may review the draft. When off, only the flag’s primary Project’s rules and reviewers apply. Also available on the REST API as targetingReviewMode.
Approval flow organization settings

Environment-scoped approvals

Approvals are environment-aware. An approval only counts for the environments the reviewer can review: if a reviewer’s role (or team) limits their Review permission to specific environments, their approval covers only those environments, and a draft cannot publish until its approvals together cover every environment the draft changes. To set up a separate approver group per environment — for example, one group that signs off on production changes and a different group for staging:
  1. Create a team per environment (Settings → Members → Teams) and give each team a role with the Review permission limited to its environment.
  2. Add the reviewers to their environment’s team.
  3. Optionally add both teams to Required approver teams on the approval rule. Because each team can only review its own environment, a staging draft can then only be satisfied by the staging team, and a production draft only by the production team.
Even without required approver teams, environment limits alone keep the groups distinct: a reviewer limited to staging can never sanction a production change.

Requesting a Review

When Approval Flows are enabled, you must request a review before publishing changes. Add a detailed comment describing the changes so reviewers can understand the intent of your request.
Requesting a review for feature changes
Requested reviews appear in the Drafts tab on the Features overview page with a Pending Review status. Sort by date updated to see your most recent request at the top.
Pending review list in the Drafts tab

Reviewing

A reviewer needs the Review permission for Feature Flags in the flag’s primary Project, covering the environments the draft changes (see Environment-scoped approvals). When the flag is delivered into a Targeting Project that has an approval rule of its own, that Project’s reviewers may also review the draft; their approval satisfies their own Project’s requirement, not the primary Project’s. The person who created the draft cannot approve it. If Block contributors from self-approving is enabled, anyone who contributed to the draft is also prevented from approving it. See Permissions for details. Click the feature, then click Review and Approve to open the review modal.
Review and Approve button on a feature
From here, you can see the diff between the currently published changes as well as the comments.
Diff view showing changes between published and draft versions
Click Next to write your review in the comment box and select a status:
  • Comment — Add a note without formally reviewing the changes
  • Request Changes — Flag issues that need to be addressed before approval
  • Approve — Confirm that everything looks correct
Review status options: Comment, Request Changes, Approve
Once the changes are Approved, they can be published.
Approved draft ready to publish

Publishing with Approvals

After approval, anyone with Publish access to the affected environments can publish the draft. If the approval rule lists Required approver teams, the draft additionally cannot publish until a member of one of those teams has approved it. If the flag is delivered into a Targeting Project with an approval rule of its own, the draft also needs an approval from one of that Project’s reviewers. A user with Bypass draft approvals can publish without any of these, and so can API keys when REST API always bypasses approval requirements is on. Organization API keys with Review access can approve too. A key acting as itself is judged on its own role, never satisfies a required approver team, and can’t approve a draft it created or edited. A key that acts as User approves as the member it names, and its approval counts only where both the key and the member could approve. Since the key chooses who it names, it can draft as one member and approve as another, including a member of a required approver team. To stop that, make the key act as System, which always approves as itself, or give it a role without Review access. See Naming who asked.
Publishing approved changes with admin bypass option
Once published, a green “Live” badge confirms the version is published and active. Green badge indicating the published version is live

Visualize Changes with Compare Revisions

Get a detailed diff of the changes between published and draft versions by clicking the Compare Revisions button. Compare Revisions button

Saved Groups

Saved groups follow the same draft → review → publish lifecycle as feature flags. Every change you make to a saved group — editing values or conditions, updating metadata, or archiving it — is tracked as a revision so you can review, compare, and roll back changes over time.

Saved Group Revisions

When you edit a saved group, GrowthBook saves the change to a draft revision. Drafts are visible to everyone with access to the saved group, but they don’t affect SDK evaluations until they’re published — so you can stage and review your changes before they reach your users. Each edit dialog shows where the change will go. By default that’s the draft you’re viewing, your own open draft, or a new draft. This includes adding, overwriting, and removing ID List items. In the dialog you can add the change to another open draft, create a new draft, or choose Publish now if you can publish without a review (Bypass approvals and publish now when approval is required and you can bypass it). The submit button reads Save to draft, Publish, or Bypass approval & publish. In Edit Information, a change that goes live at once is saved with Save. From the saved group detail page you can:
  • Switch revisions — Use the revision dropdown next to the page tabs to view the live revision, a draft, or an earlier revision. A bar under the tabs shows the state of the revision you’re viewing, with Discard and Publish or Review & publish for a draft.
  • Create a new draft — Click New draft while viewing the live revision to start a new set of changes.
  • See details and references — The right rail shows the group’s details, what references it, and the selected revision. While a revision is a draft, you can edit its name and description there.
  • Review and publish — The Review & Publish tab shows what the draft changes and where it stands in review.
  • Compare revisions — Choose Compare revisions from the ⋮ menu to see a side-by-side diff of any two revisions.
  • Revert to a previous revision — On the Review & Publish tab, click Roll back on the live revision, or Revert to this revision on an earlier published one. You can save the revert as a new draft or publish it at once.
  • Discard a draft — Authors can discard their own draft if they no longer want to publish it.
  • Fix merge conflicts — If another user publishes changes while your draft is open, click Fix conflicts to resolve them before publishing. The conflict resolution flow works the same way it does for features.
An archived saved group shows a callout at the top of its page, a draft that would archive it shows a warning, and a draft that would unarchive it says so.

Saved Group Approval Flows

You can require approvals for saved group changes independently from feature flag approvals.

Settings

Enable saved group approvals from Settings → General → Approval Flows. The Saved Groups section has its own toggle, separate from the Features section:
  • Require approval to modify Saved Groups — When enabled, every change to a saved group must be reviewed and approved by someone else before it goes live.
  • Required approver teams — A draft cannot publish until someone from one of these teams approves it. Leave blank to accept an approval from anyone with Review access.
  • Require approval for — Approval is always required for changes to values and conditions. Use the Metadata changes checkbox to also require approval for edits to the description, owner, project, or tags.
  • Reset review on changes — If a draft is modified after it has been approved, the approval is revoked and a new review is required before publishing.
  • Block contributors from self-approving — Anyone who edited the draft is blocked from approving it, ensuring a separate reviewer must approve before publishing.
  • Allow approve & publish in one step — Adds an “Approve & Publish” option so reviewers with Publish access can approve and publish a draft together.

Requesting and Reviewing

When approvals are enabled, click Request Review on the Review & Publish tab instead of publishing. The request appears in the Saved Group’s revision list with a Pending review status. A user with Review access can open the request, inspect the diff, comment, request changes, or approve it. The draft’s creator cannot approve it. When Block contributors from self-approving is enabled, other contributors cannot approve it either. After approval, a user with Publish access in every Project assigned to the Saved Group can publish it. Bypass draft approvals allows the same user to publish without an approval.

Archiving and Unarchiving

Archiving and unarchiving a Saved Group always creates a revision. When approval flows are enabled, that revision must be approved before it takes effect. Archiving requires Archive & delete access; unarchiving requires Publish access. A Saved Group with active references from Feature Flags, experiments, or other Saved Groups cannot be archived until those references are removed.

Configs and Constants

Configs and Constants follow the same lifecycle. They share the Feature Flag approval rules, under Feature Flags, Configs & Constants in Settings → General → Approval Flows, matched on the Config’s or Constant’s Project. Their pages work like the Saved Group page: a revision dropdown, New draft, a status bar for the revision you’re viewing, a Review & Publish tab, and a right rail with general details and the selected revision. Edit dialogs save to a draft by default and use the same button labels. A Config’s fields, mixins, JSON, and validation rules can only be edited inside a draft. See Editing and approvals for Configs and Editing and approvals for Constants.

SDK Connections

SDK Connections follow the same draft → review → publish lifecycle. A connection’s settings and its SDK Webhooks are tracked together, so one revision can change a payload option, add a webhook, and remove another, and they all go live in the same publish.

SDK Connection Revisions

Every change to a connection or its webhooks is recorded as a revision. That includes changes that need no review and changes made through the REST API, so the connection’s history is complete and any published revision can be reverted. From an SDK Connection’s page you can:
  • Switch revisions — Use the revision dropdown to view the live revision or any open draft.
  • Create a new draft — Click New draft from the live revision.
  • Edit settings — Changes on the Overview tab collect in a bar at the bottom of the page until you click Save or Discard changes. Save writes them to the draft you are viewing. From the live revision, choose a draft under Save to, or New draft. Your own most recent draft is chosen by default.
  • Edit webhooks — On the Webhooks tab, adding, editing, or deleting a webhook is saved to a draft, or published at once when the connection needs no approval or you can bypass it.
  • Review and publish — The Review & Publish tab shows what the draft changes and where it stands.
  • Compare revisions — Choose Compare revisions from the ⋮ menu to see a diff of any two revisions.
  • Revert — Restore the settings and webhooks that an earlier published revision left. A webhook that a revert brings back is created again with a new signing key, so update whatever verifies its signature. Whether the connection is archived is not restored.
  • Discard a draft — Abandon a draft you no longer want to publish.
  • Fix conflicts — If the connection changes while your draft is open, changes to different settings and different webhooks merge on their own. You only resolve a conflict when the same setting or the same webhook was changed in both.

SDK Connection Approval Flows

You can require approval for SDK Connection changes independently from Feature Flags and Saved Groups.

Settings

Enable SDK Connection approvals from Settings → General → Approval Flows. The SDK Connections section has its own toggle:
  • Require approval to modify SDK Connections — When enabled, a change to a connection or its webhooks must be reviewed and approved by someone else before it goes live.
  • Specific environments — Limit the rule to connections in the environments you pick. An SDK Connection serves one environment.
  • Required approver teams — A draft cannot publish until someone from one of these teams approves it. Leave blank to accept an approval from anyone who can review.
  • Require approval for — Approval is always required for connection settings and webhooks, such as Projects, environment, and payload options. Use the Metadata changes checkbox to also require approval for a change to the connection’s name.
  • Reset review on changes — If a draft is modified after it has been approved, the approval is revoked and a new review is required before publishing.
  • Block contributors from self-approving — Anyone who edited the draft is blocked from approving it.
  • Allow approve & publish in one step — Adds an “Approve & Publish” option so reviewers who can publish can do both together.
A rule can apply to all Projects or be overridden for specific ones. A connection in several Projects follows the rule of each.

How Approval Changes the Workflow

  • While a connection requires approval, its settings and webhooks can only be changed in a draft in the app.
  • A draft that moves a connection to another Project or environment is reviewed under the rules of both where it leaves and where it lands.
  • Bypass draft approvals for SDK Connections lets a user publish without an approval.
  • The REST API can change a connection that requires approval directly only with bypassApproval: true. That needs the same access, or the organization’s REST API always bypasses approval requirements setting. See the SDK Connection Revisions API.

Validation

Custom Hooks can check an SDK Connection and its webhooks whenever they are saved or published, for example to require payload encryption in production or an Authorization header on every webhook.

Publishing Several Changes Together

Some changes only make sense together, such as a Config schema change and the values that depend on it, or a new SDK Connection setting and the Feature Flag that relies on it. The REST API can publish a set of draft revisions as one all-or-nothing operation:
  • What it accepts — Up to 50 revisions, at most one per entity, across Feature Flags, Saved Groups, Configs, Constants, and SDK Connections. Name each by its identifier and version, or by its revision id.
  • All or nothing — Validation, guards, and Custom Hooks run against the combined end state of the whole set. If any item is blocked, nothing publishes and one 422 lists every gate across every item, with the flag that clears each.
  • Dry run — Pass "dryRun": true for the full report with no writes.
  • Concurrent changes — If any target changes while the release is being prepared, it stops with a 409 and nothing publishes.
  • Failures — A failure after publishing has started rolls every item back, including an SDK Connection’s webhooks.
  • SDK payloads refresh once for the whole release. A webhook edited by an SDK Connection revision is sent only after the release has landed.
Checks on one item read the live state of SDK Connections, not what another item in the same release proposes. A release that upgrades a connection’s SDK version and publishes a flag that depends on it judges the flag against the current version. See POST /releases/publish-revisions for the full request and response.