Skip to content

Latest commit

 

History

History
120 lines (80 loc) · 8.31 KB

branch-permissions.md

File metadata and controls

120 lines (80 loc) · 8.31 KB
title titleSuffix description ms.assetid ms.technology ms.topic ms.date monikerRange
Set Git branch security and permissions
Azure Repos
Set permissions for Git branches in Azure DevOps Services/TFS.
0dacda14-c251-4a89-8141-ae60a47dab52
devops-code-git
conceptual
12/04/2020
>= tfs-2017

Set branch permissions

[!INCLUDE version-tfs-2017-through-vsts]

Set up permissions to control who can read and update the code in a branch on your Git repo. You can set permissions for individual users and groups, and inherit and override permissions as needed from your repo permissions.

[!INCLUDE version-selector-minimize]

Use the branches view to configure security

::: moniker range=">= azure-devops-2019"

  1. Open the Branches page by navigating to your project in the web portal and selecting Repos, Branches.

    Open up the Branches page on the web

::: moniker-end

::: moniker range="< azure-devops-2019"

  1. Open the Branches page by navigating to your project in the web portal and selecting Code, Branches.

    Open up the Branches page on the web

::: moniker-end

  1. Locate your branch in the page. You can browse the list or you can search for your branch using the Search all branches box in the upper right.

    Branches page

  2. Open the context menu by selecting the ... icon next to the branch name. Select Branch security from the menu.

    Open the branch permissions page from the branches context menu

Add users or groups

Tip

You can only add permissions for users and groups already in your Project. Add new users and groups to your Project before setting branch permissions.

Add users or groups to your branch permissions by selecting Add.
Enter the sign-in address or group alias, then select Save Changes.

Remove users or groups

Remove permissions for a user or group by selecting the user or Azure DevOps group, then selecting Remove. The user or group will still exist in your Project and this change will not affect other permissions for the user or group.

Remove branch permissions for a user in Azure DevOps Services or TFS

Set permissions

Control branch permission settings from the branch permission view. Users and groups with permissions set at the repo level will inherit those permissions by default. To learn more about how permissions work, see Permission settings.

::: moniker range=">= tfs-2017 <= tfs-2018"

Permissions in TFS 2017 Update 1 through TFS 2018 Update 2

Permission Description
Contribute Users with this permission can push new commits to the branch and lock the branch.
Edit Policies Can edit branch policies.
Exempt from policy enforcement Users with this permission are exempt from the branch policy set for the branch when completing pull requests and can override the policies by checking Override branch policies and enable merge when completing a PR. Users with this permission can also push to a branch that has branch policies enabled.
Force Push (Rewrite History and Delete Branches) Can force push to a branch, which can rewrite history. This permission is also required to delete a branch.
Manage Permissions Can set permissions for the branch.
Remove Others' Locks Can remove locks set on branches by other users.

::: moniker-end

::: moniker range="<= tfs-2017"

Permissions in TFS 2017 and lower

Permission Description
Administer Users with this permission can set branch permissions for other users, delete the branch, and lock the branch.
Contribute Users with this permission can push new commits to the branch. Users with this permission cannot rewrite the existing commits on the branch. Users with this permission can lock the branch.
Exempt from policy enforcement Users with this permission are exempt from the branch policy set for the branch.
Rewrite and destroy history (force push) Can force push to a branch. This permission is also required to delete a branch. Users with this permission can modify the commit history of a branch.

::: moniker-end

::: moniker range=">= azure-devops-2019"

Permissions in Azure DevOps Server 2019 through Azure DevOps Services

Note

The Exempt from policy enforcement, (which is still available in TFS 2015 through TFS 2018 Update 2) was removed and its functionality divided into the following two new permissions:

  • Bypass policies when completing pull requests
  • Bypass policies when pushing

Users that previously had Exempt from policy enforcement enabled now have the two new permissions enabled instead. See the following table for more details on these two new permissions.

Permission Description
Contribute Users with this permission can push new commits to the branch and lock the branch.
Edit Policies Can edit branch policies.
Bypass policies when completing pull requests Users with this permission are exempt from the branch policy set for the branch when completing pull requests and can opt-in to override the policies by checking Override branch policies and enable merge when completing a PR.
Bypass policies when pushing Users with this permission can push to a branch that has branch policies enabled. Note that when a user with this permission makes a push that would override branch policy, the push automatically bypasses branch policy with no opt-in step or warning.
Force Push (Rewrite History and Delete Branches) Can force push to a branch, which can rewrite history. This permission is also required to delete a branch.
Manage Permissions Can set permissions for the branch.
Remove Others' Locks Can remove locks set on branches by other users.

The following permissions are automatically assigned to branch creators: Contribute, Edit Policies, Force Push, Manage Permissions, and Remove Others' Locks.

::: moniker-end