Protected Git Scopes

Compliance Measures Shared Responsibility Firewall Access Control SAML SSO HTTPS/SSL Directory Sync Secure Backend Access Deployment Protection Deployment Retention Audit Logs Protected Git Scopes Security

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 Epycbyte 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 Epycbyte teams to deploy your Git repositories. As an owner of multiple teams you can claim the same scope for each Epycbyte 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 Epycbyte 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 Epycbyte 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 Epycbyte 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