How-to

Protected Git Scopes

Learn how to limit other Vercel teams from deploying from your Git repositories.
Table of Contents

Protected Git Scopes are available on Enterprise plans

Those with the owner role can access this feature

Only allow specific Vercel teams to deploy your Git repositories. As an owner of multiple teams you can claim the same scope for each Vercel team, allowing all of them to deploy repositories from your protected Git scope.

You can add up to five Protected Git Scopes to your Vercel Team. Multiple teams can specify the same scope, allowing both teams access.

In order to add a Protected Git Scope to your Vercel Team, you must be an Owner of the Vercel Team, and have the required permission in the Git namespace.

For Github you must be an admin, for Gitlab you must be an owner, and for Bitbucket you must be a owner.

  1. From your Vercel Team's dashboard:

    1. Select the project that you wish to enable Password Protection for
    2. Go to Settings then Security and Privacy
    3. Scroll down to Protected Git Scopes
  2. From Protected Git Scopes:

    1. Select Add to add a new Protected Git Scope
    2. In the modal, select the Git provider you wish to add:
    3. In the modal, select the Git namespace you wish to add:
    4. Click Save
  1. From your Vercel Team's dashboard:

    1. Select the project that you wish to enable Password Protection for
    2. Go to Settings then Security and Privacy
    3. Scroll down to Protected Git Scopes:
  2. From Protected Git Scopes

    1. Select Remove to remove the Protected Git Scope
Last updated on September 16, 2024