Deploy Previews from forks now require approval on all public repos

November 16, 2026

For projects connected to public repositories, we’ve reworked the previous sensitive variable policy into an expanded untrusted deploys policy to improve security and help protect your team’s usage. Deploy Previews from forks, opened by someone outside your Netlify team, now wait for a team member to approve them before they build. You can opt out anytime by choosing a different option in your untrusted deploys policy.

Previously, the sensitive variable policy only blocked building these deploys when Netlify detected sensitive environment variables in your project. On projects without detected sensitive variables, anyone who opened a pull/merge request could build without anyone reviewing from your team reviewing the updates first. Now these deploys wait for approval whether or not your project has sensitive variables, as long as your project has the default Require approval setting on.

Production deploys, branch deploys, and Deploy Previews from your team members aren’t affected. Note that Netlify assumes that team members have matched their Netlify team user ID with their Git provider accounts. If you previously chose Build without sensitive variables or Build without restrictions, your project keeps that setting and allows those builds as it did before.

What you’ll notice

If your project receives pull/merge requests from people or bots not on your team, you may see more pending deploy requests at the top of your project’s deploy list. To find out when a deploy is waiting for approval, set up deploy notifications.

Why we made this change

Anyone can open a pull/merge request from a fork of a public repository, and building its Deploy Preview runs their code. Even without sensitive variables, that build can use your project’s resources and your team’s usage. Requiring approval lets you review the changes before they build.

The policy has a new name and location

Because the policy is no longer only about environment variables, the sensitive variable policy is now the untrusted deploys policy. It has moved from your project’s environment variables settings to Project configuration > Developer settings > Continuous deployment > Untrusted deploys policy.

The policy options are:

  • Require approval (default): untrusted deploys wait for a team member to accept or reject them.
  • Build without sensitive variables: untrusted deploys build automatically, but variables identified as sensitive aren’t passed to the build.
  • Build without restrictions: untrusted deploys build like any other Deploy Preview.

Learn more about the untrusted deploys policy in our docs.