Set permissions at the project- or collection-level

Azure DevOps Services | Azure DevOps Server 2019 | TFS 2018 | TFS 2017 | TFS 2015 | TFS 2013

Several permissions are set at the project or at the organization/project collection level. You can grant these permissions by adding a user or group to one of the default security groups listed here. Or, you can create a custom security group within a level and add members to that group. You can then change the default permission settings.

An organization is the container for several projects that share resources. For more information about projects and project collections, see Plan your organizational structure.

A project collection is the container for several projects that share resources. For more information about projects and project collections, see About projects and scaling your organization.

Project level Organization/Collection level
- Build Administrators
- Contributors
- Project Administrators
- Project Valid Users
- Readers
- Release Administrators
- TeamName Team
- Project Collection Administrators
- Project Collection Build Administrators
- Project Collection Build Service Accounts
- Project Collection Proxy Service Accounts
- Project Collection Service Accounts
- Project Collection Test Service Accounts
- Project Collection Valid Users
- Security Service Group

Note

The above list indicates the latest groups defined for Azure DevOps and TFS 2017 and later versions. For earlier versions of TFS, the list may differ. Only add service accounts to TFS service account groups. To understand valid user groups, see About permissions and groups, Valid user groups.

For a description of each group and each permission, see Permissions and groups reference, Groups.

Tip

For users tasked with managing project-level features —such as, teams, area and iteration paths, repositories, service hooks, and service end points—add them to the Project Administrators group. For users tasked with managing organization or collection-level features —such as, projects, policies, processes, retention policies, agent and deployment pools, and extensions—add them to the Project Collection Administrators group. To learn more, see About user, team, project, and organization-level settings.

Prerequisites

  • You must be a member of a project. If you don't have a project yet, create one in Azure DevOps. If you haven't been added as a team member, get added now.
  • You must be a member of a project. If you don't have a project yet, create one in an on-premises TFS. If you haven't been added as a team member, get added now.
  • To manage permissions or groups at the project level, you must be a member of the Project Administrators Group or have your Edit project-level information set to Allow. If you created the project, you are automatically added as a member of this group.
  • To manage permissions or groups at the collection or instance level, you must be a member of the Project Collection Administrators Group or have your Edit instance-level information set to Allow. If you created the organization or collection, you are automatically added as a member of this group.

Add a user or group to a security group

As roles and responsibilities change, you might need to change the permission levels for individual members of a project. The easiest way to do that is to add the user or a group of users to a pre-defined security group.

Here we show how to add a user to the built-in Project Administrators group. The method is similar to adding an Azure Active Directory or Active Directory group.

  1. Open the web portal and choose the project where you want to add users or groups. To choose another project, see Switch project, repository, team.

  2. Choose Project Settings and then Security.

    To see the full image, click to expand.

    Project Settings>Security

  3. Choose Project Administrators group, Members, and then Add.

    Project Settings>Security, Add member

  4. Enter the name of the user account into the text box. You can enter several identities into the text box, separated by commas. The system automatically searches for matches. Choose the match(es) that meets your choice.

    Add users and group dialog

    Note

    Users that have limited access, such as Stakeholders, won't be able to access select features even if granted permissions to those features. To learn more, see Permissions and access.

  5. Choose Save changes. Choose the  refresh icon to see the additions.

  1. Open the web portal and choose the project where you want to add users or groups. To choose another project, see Switch project, repository, team.

  2. Choose the  gear icon to open the administrative context.

    Open Project Settings, horizontal nav

  3. Choose Security, Project Administrators group, Members, and then Add.

    Project Settings>Security, Add member

  4. Enter the name of the user account into the text box. You can enter several identities into the text box, separated by commas. The system automatically searches for matches. Choose the match(es) that meets your choice.

    Add users and group dialog

    Note

    Users that have limited access, such as Stakeholders, won't be able to access select features even if granted permissions to those features. To learn more, see Permissions and access.

  5. Choose Save changes. Choose the  refresh icon to see the additions.

Change the permission level for a project-level group

  1. From the Security page, choose the group whose permissions you want to change.

    For example, here we grant permission to the Contributors group to delete and restore work items.

    Contributors group, permissions

    Tip

    In general, if you add a user to the Contributors group, they can add and modify work items. You can restrict permissions of users or user groups to add and modify work items based on the area path. For details, see Set permissions and access for work tracking, Modify work items under an area path.

    For a description of each permission, see Permissions and groups reference, project-level permissions.

    Note

    You can't change the permission settings for the Project Administrators group. This is by design.

  2. Choose Save changes.

Add a group and change its permissions at the organization or collection-level group

  1. From your project web portal, choose the Azure DevOps icon, and then select gear icon Organization settings.

    Open Organization settings

  2. Choose Security, and then choose Create group to open the dialog for adding a group.

    Create security group at the organization or collection level

  3. Enter a name for the group, and optionally a description.

    For example, here we define a Work Tracking Administrators group.
    Security group dialog, Add a security group at the organization or collection level
    For a description of each permission, see Permissions and groups reference, collection-level permissions.

  4. Choose the group name you just created and change the permission levels.

    Here we grant this group permissions to manage customizations for the Inheritance process model.

    Custom group, permissions

  5. Choose Save changes.

    Note

    You can't change the permission settings for the Project Collection Administrators group. This is by design.

  1. Choose the  settings icon and select Organization settings (Azure DevOps) or Collection settings (on-premises).

    Open Organization Settings

  2. Choose Security, and then choose Create group to open the dialog for adding a group.

    Create security group at the organization or collection level

  3. Enter a name for the group, and optionally a description.

    For example, here we define a Work Tracking Administrators group.
    Security group dialog, Add a security group at the organization or collection level
    For a description of each permission, see Permissions and groups reference, collection-level permissions.

  4. Choose the group name you just created and change the permission levels.

    Here we grant this group permissions to manage customizations for the Inheritance process model.

    Custom group, permissions

  5. Choose Save changes.

    Note

    You can't change the permission settings for the Project Collection Administrators group. This is by design.

On-premises deployments

For on-premises deployments, see these additional topics:

If your on-premises deployment is integrated with SQL Server Reports, you'll need to manage membership for those products separately from their websites. See Grant permissions to view or create SQL Server reports in TFS.

If your on-premises deployment is integrated with a SharePoint product or SQL Server Reports, you'll need to manage membership for those products separately from their websites.

Next steps