Skip to content

Latest commit

 

History

History
116 lines (71 loc) · 5.62 KB

set-tfvc-repository-permissions.md

File metadata and controls

116 lines (71 loc) · 5.62 KB
title titleSuffix description ms.assetid ms.service ms.topic ms.author author monikerRange ms.date ms.subservice
Set TFVC repository permissions
Azure Repos
Follow steps to manage access to a Team Foundation Version Control (TFVC) repository feature or function.
azure-devops-repos
quickstart
vijayma
vijayma
<= azure-devops
11/30/2022
azure-devops-repos-git

Set TFVC repository permissions

[!INCLUDE version-lt-eq-azure-devops] [!INCLUDE version-vs-gt-eq-2019]

You can manage access to a Team Foundation Version Control (TFVC) repository to lock down who can contribute to your source code. There's only one TFVC repository per project. For guidance on who to give greater permission levels, see Manage access using permissions.

Prerequisites

::: moniker range="azure-devops"

Category Requirements
Project access Member of the Azure DevOps project where the TFVC repository is located.
Permissions Member of the Project Administrators group or Manage permissions set to Allow for the TFVC repository.
Access levels To contribute to source code: At least Basic access. Stakeholder access for private projects provides no access to source code. Stakeholder access for public projects provides the same access as Contributors and Basic. For more information, see About access levels.

::: moniker-end

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

Category Requirements
Project access Member of the Azure DevOps project where the TFVC repository is located.
Permissions Member of the Project Administrators group or Manage permissions set to Allow for the TFVC repository.
Access levels To contribute to source code: At least Basic access. Stakeholder access for private projects provides no access to source code. For more information, see About access levels.

::: moniker-end

Default repository permissions

By default, members of the project Contributors group have permissions to contribute to a repository. For a description of each security group and permission level, see Security groups, service accounts, and permissions in Azure DevOps.

[!INCLUDE temp]

Set TFVC repository security permissions

To set permissions for a custom security group, ensure that the group is already defined. For more information, see Change project-level permissions for more information. ::: moniker range="azure-devops"

  1. In the Azure DevOps web portal for the project where you want to set permissions, select Project settings. To choose another project, see Switch project, repository, team.

  2. Select Repositories.

  3. Select the TFVC repository labeled with the name of the project.

    Image that shows choosing a TFVC repository.

  4. Choose the user or security group you want to change permissions for.

    To set permissions for a specific user or group, enter their name in the identity box and select their identity.

    Image that shows adding a user or group.

  5. Make the changes to the permission set.

    Image that shows setting the permissions for a user or group.

  6. When you're done, navigate away from the page. The permission changes are automatically saved for the selected user or group.

    If you add a user or group and don't change any of their permissions, the user or group you added no longer appears after you refresh the permissions page.

    [!INCLUDE temp]

::: moniker-end

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

To set the permissions for the TFVC repository for a project:

  1. In the Azure DevOps web portal for the project where you want to set permissions, select Project Settings.

  2. Select Repositories.

  3. Select the TFVC repository.

  4. Choose the security group whose permissions you want to manage, in this case the Contributors group.

  5. Select the permission for Manage branch.

    [!INCLUDE temp]

    Screenshot that shows Project security settings for a TFVC repository.

    [!INCLUDE temp]

    If you add a user or group and don't change any of their permissions, the user or group you added no longer appears after you refresh the permissions page.

  6. Save your changes.

::: moniker-end

Related articles