> ## Content Index
> Fetch the complete content index at: https://blog.esadax.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# Protected Git Scopes
- URL: https://blog.esadax.com/en/protected-git-scopes/
- Published: 2026-11-15T04:21:09.000Z
- Updated: 2026-11-15T04:21:09.000Z
- Author: Esadax 
- Tags: #tr-platform-17-security-07-protected-git-scopes, #en, #mdx-imported, Platform

Protected Git Scopes are available on Enterprise plans. Those with the owner role can access this feature.

### How-to Protected Git Scopes

Learn how to limit other Esadax teams from deploying from your Git repositories.

## Table of Contents

- Protected Git Scopes
- Managing Protected Git Scopes
- Adding a Protected Git Scope
- Removing a Protected Git Scope

## Protected Git Scopes

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

## Managing Protected Git Scopes

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

### Adding a Protected Git Scope

1. Go to your Team Security Settings
2. From your Esadax Team's dashboard: Select the project that you wish to enable Password Protection for
3. Go to Settings then Security and Privacy
4. Scroll down to Protected Git Scopes
5. Add a Protected Git Scope
6. In the modal, select the Git provider you wish to add:
7. In the modal, select the Git namespace you wish to add:
8. Click Save

### Removing a Protected Git Scope

1. Go to your Team Security Settings
2. From your Esadax Team's dashboard: Select the project that you wish to enable Password Protection for
3. Go to Settings then Security and Privacy
4. Scroll down to Protected Git Scopes
5. Remove a Protected Git Scope
6. Select Remove to remove the Protected Git Scope