# Setting up Reviews for Team Workflows

> For AI agents: a documentation index is available at [/llms.txt](/llms.txt). Append `.md` to any page URL for markdown, or send `Accept: text/markdown`.

Reviews require approval before changes to feature gates, dynamic configs, segments, and experiments reach production. As a Project Admin, you turn on reviews for a project, then add reviewers or teams who approve or reject each submitted change.

## Turning on change reviews for a project

As a Project Admin, you can configure your project to require reviews for any changes. To enable reviews for your project, navigate to the **Project Settings** page, switch to the _Reviews_ tab, then toggle the review requirement on.

![Project settings reviews configuration interface](https://docs.statsig.com/images/guides/setting-up-reviews/45a439b5-7cf7-4f32-82d0-596c089f2359.png)

- You can optionally allow different roles to bypass the review requirement and self-approve review requests by customizing the permissions available to user roles:

![User role permissions configuration screen](https://docs.statsig.com/images/guides/setting-up-reviews/4b7db056-a6be-4a76-99c9-08f8dc053ed8.png)

- When you make any configuration changes to a feature gate or experiment, the console prompts you to **Submit for Review**. You can add reviewers when you submit the change.

![Submit for Review modal prompting for reviewer selection](https://docs.statsig.com/images/guides/setting-up-reviews/166678241-272adade-ca60-4942-bd04-a1413d54864c.png)

- Reviewers see a notification on the Statsig console. When they select **View Proposed Changes**, they see a diff of the _current version_ in production and the _new version_. Reviewers can then **Approve** or **Reject** the submitted changes.

![proposed changes](https://docs.statsig.com/images/proposed_changes.png)

![example review](https://docs.statsig.com/images/example_review_page.png)

## Teams

To create a predefined group of reviewers, you can create Teams.

![Teams creation interface](https://docs.statsig.com/images/guides/setting-up-reviews/1b1c72a9-ac98-4590-8690-c39d2e68489a.png)

You can now use these predefined **Teams** when you submit any changes for review.

![Team selection for review submission](https://docs.statsig.com/images/guides/setting-up-reviews/166684577-29598c7f-fcba-4c7e-848d-9a45b031bd79.png)

## Enforcing team reviews

You can restrict who can make changes to your Project by (a) turning on **Reviews Required** for your Project, and (b) adding designated **Teams** or **Reviewers**. Add the Teams or Reviewers when you create the Feature Gate or Experiment.

For (a), refer to the **Turning on change reviews for a project** section to enable project-wide reviews. For (b), as an owner of a Feature Gate or Experiment, you can add designated **Teams** or **Reviewers** at any time. Adding designated Teams or Reviewers ensures that only those groups or members can review and approve subsequent changes. When another member tries to edit these designated review groups or reviewers, the change requires approval from the designated reviewers.

![Team review configuration settings](https://docs.statsig.com/images/guides/setting-up-reviews/166682283-c9e2de57-0b9a-473e-adf2-100a240ab6b0.png)

![Teams and reviewers selector for enforcing approvals](https://docs.statsig.com/images/guides/setting-up-reviews/166682177-d44411e6-c4ab-49fe-9250-c77b063621af.png)

## Configuring review settings for different environments

Many teams build, test, and launch new features and experiments across multiple development environments. Statsig supports multiple development environments through [Environments](https://docs.statsig.com/guides/using-environments#configuring-environments).

You can also configure which environments require reviews through **Project Settings**. Go to **Project Settings** → [**Keys & Environments**](https://console.statsig.com/BPJcDV1K1g87fTib5ZEMk/api_keys) → tap **Edit** on **Environments**.

By default, if you've enabled "Reviews Required" for your project, Statsig requires reviews for Production but not for non-Production environments.

![Environments settings showing environments and order](https://docs.statsig.com/images/environments.png)

![Manage environments dialog with environment list and review settings](https://docs.statsig.com/images/edit-environment-dialog.png)

#### Team-based required reviews per environment

You can assign specific teams as reviewers for each environment. Assigning teams ensures that only designated team members can approve changes for that environment.

![Assigning teams as reviewers for specific environments](https://docs.statsig.com/images/environment-reviews.png)

#### Code freeze use case

During code freeze periods, you can prevent anyone from deploying feature flags or configs to production. Assign a dedicated code freeze team as the production reviewer. This assignment ensures that only members of the code freeze team (such as your SRE team or designated code freeze owners) can approve production changes. After the code freeze period ends, you can remove the team assignment to restore normal review workflows.