You can enable reviews for all Statsig resources such as feature gates, dynamic configs, segments, and experiments that you'll likely deploy to a production environment.
## 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 and toggle this on.
{% figure %}
{% /figure %}
- You can optionally allow different roles to bypass the review requirement and self-approve review requests by customizing the permissions available to user roles:
{% figure %}
{% /figure %}
- 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.
{% figure %}
{% /figure %}
- 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.
{% figure %}
{% /figure %}
{% figure %}
{% /figure %}
## Teams
To create a predefined group of reviewers, you can create Teams.
{% figure %}
{% /figure %}
You can now use these predefined **Teams** when you submit any changes for review.
{% figure %}
{% /figure %}
## 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** 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. This ensures that only these designated 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 currently designated reviewers.
{% figure %}
{% /figure %}
{% figure %}
{% /figure %}
## Configuring review settings for different environments
Many teams build, test, and launch new features and experiments across multiple development environments. Statsig supports this through [Environments](/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 have enabled "Reviews Required" for your project, reviews are required for Production but not for non-Production environments.
{% figure %}
{% /figure %}
{% figure %}
{% /figure %}
#### Team-based required reviews per environment
You can assign specific teams as reviewers for each environment. This ensures that only designated team members can approve changes for that environment.
{% figure %}
{% /figure %}
#### Code freeze use case
During code freeze periods, you can prevent anyone from deploying feature flags or configs to production by assigning a dedicated code freeze team as the production reviewer. This ensures that only members of that 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.