Add users or groups to a team or project

Azure DevOps Services | Azure DevOps Server 2020 | Azure DevOps Server 2019 | TFS 2018 - TFS 2013

You add users to a team or project so they can contribute to the team and project. For enterprise organizations with large user bases, we recommend you use Azure Active Directory to add and manage new users through security groups. However, to enable flexibility for all size organizations, the following operations are supported:

  • Team and project administrators can add new users to their team or project, unless the policy Allow team and project administrators to invite new users is disabled. New users are ones that haven't been added to the organization.
  • When adding new users through the team and project user interfaces, the system automatically assigns an access level to the user.
  • Adding users to a team or project automatically adds them to the Contributors group for the project. Members of the Contributors group have permissions to most features needed to contribute.
  • By adding users to a team, you make team-specific tools aware of them, such as the team security group, Team Members widget, and sprint capacity planning tools.
  • Once users have been added to a project or organization, you can browse for their display name or user name (email alias) from any people-picker tool.

You add users to a team or project so they can contribute to the team and project. For enterprise organizations with large user bases, we recommend you use Active Directory or Windows Group to manage users through security groups. However, to enable flexibility for all size organizations, the following operations are supported:

  • Team and project administrators can add existing users to their team or project. Existing users are ones known to the project collection through Active Directory or Windows group.
  • Adding users to a team or project automatically adds them to the Contributors group for the project. Members of the Contributors group have permissions to most features needed to contribute.
  • By adding users to a team, you make team-specific tools aware of them, such as the team security group, Team Members widget, and sprint capacity planning tools.
  • Once users have been added to a project or organization, you can browse for their display name or user name (email alias) from any people-picker tool.

You add projects to an organization or project collection and you add teams to projects. To learn more, see:

Important

Select a version from Azure DevOps Content Version selector.

To view the content available for your platform, make sure that you select the correct version of this article from the version selector which is located above the table of contents. Feature support differs depending on whether you are working from Azure DevOps Services or an on-premises version of Azure DevOps Server.
To learn which on-premises version you are using, see What platform/version am I using?

Supported options for adding users

Depending on the interface you use, you can exercise different options for adding new or existing users to teams or projects.

Team and project administrators can add existing users to their team or project. Existing users are ones that are known to a project collection through the Active Directory or Windows Group created for the server that hosts the on-premises Azure DevOps Server.

Administrator level

Interface

Supported tasks

Team administrators

Add new or existing users to a team. Send new users an invite.

Team administrators

Add existing users or groups to a team, or remove a member.

Project Administrators

Add new or existing users. Send new users an invite. Optionally add users to one or more teams.

Project Administrators

Add existing users or groups to a security group. By adding to a team group, you effectively add them to the team. Optionally remove a user from a group.

Project Collection Administrators

Add new users to an organization and send an invite. Must specify the access level. Optionally add them to select projects. Can use Group rules to further manage groups being added.

Project Collection Administrators

Add new users to an organization and send an invite. Must specify the access level.

Azure Active Directory Administrators

Azure Active Directory

Users you add to Azure Active Directory connected to Azure DevOps Services are added to the Project Collection Valid Users group. To learn more, see Connect your organization to Azure Active Directory.

Active Directory Administrators

Active Directory or Windows Group

Users you add to Active Directory or Windows Group connected to Azure DevOps are added as members of the Project Collection Valid Users group. They have access to all projects within a project collection. To learn more, see Set up groups for use in Azure DevOps on-premises.

Prerequisites

If you're new to Azure DevOps, you may want to familiarize yourself with the information provided in these articles:

Add a user from the Team Members widget

As a team administrator, you can add new or existing members from the Team Members dashboard widget. To add this widget to a dashboard, see Add widgets to a dashboard.

  1. To invite someone to your team, choose the plus button on the Team Members widget.

    Screenshot of Team Members widget added to a dashboard, plus icon.

  2. For new users, enter their email address. For existing users, type their name until it resolves as a known name to the system. You can add several email addresses or account names by separating them with a semicolon (;).

    Choose the entry listed under Add users to complete the entry.

    Note

    Any valid email address is acceptable. When the user accepts the invitation and signs into Azure DevOps, they register their email address as a Microsoft account and choose a password.

    Choose the name that appears to complete the entry.

    Invite members to a team dialog, enter an unknown user email address.

    Invite members to a team dialog, enter a known user account.

  3. Complete the addition.

    When the user is unknown, you'll get a notification that an access level must be assigned. To complete the invitation, choose Add.

    Choose Add to complete adding the user. Known users don't receive an invitation.

    Invite members to a team dialog, Add new user account.

    Invite members to a team dialog, Add button.

    When adding a new user, the system assigns Stakeholder as the access level when all free five Basic access levels have been assigned. Active contributors to a project need to have Basic access as a minimum. A Project Collection Administrator can change the access level and resend invitations from the Organization Settings>Users page.

    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.

  4. (Optional) A message will briefly display on the screen to indicate success or failure. Choose Details to open the notification and review details.

    Screenshot of notification success message.

    Screenshot of notification failure message.

    A success message indicates the status of adding the user to the system.

    A failure message indicates why the addition of the user failed.

    Notification dialog of Success. ":::

    Notification dialog of failure.

  5. New users receive an email inviting them to sign in to the project. Existing users don't receive any formal notification.

Add users or groups to a team

Add existing users or security groups to a team from the Project settings> Teams page. From this interface you can view, add, or remove users and security groups to/from a team. To add a custom security group, see Set permissions at the project- or collection-level.

Note

To enable the preview feature, New Teams Page, see Enable preview features.

You can toggle between direct or expanded membership views. The Direct Members view displays users and groups that have been added to the team. The Expanded Members view replaces any Azure DevOps groups with the members that belong to those groups. Azure Active Directory or Active Directory groups aren't expanded.

  1. Open a backlog or board for a team and choose the team profile icon. Then choose Team Settings.

    Here we open the Board for the Web team and from there the team profile.

    Work Backlog or Board, choose team profile icon

  2. If you need to switch the team context, use the team selector within the breadcrumbs.

    Screenshot of Project Settings>Teams>Team and Teams breadcrumb.

  3. Choose Add.

    Team Profile, choose Add, preview page

  4. Enter the sign-in addresses or display name for each account you want to add. You can also add a project security group—such as another team group, custom group, or Azure Active Directory group when used by the organization. Add them one at a time or all at the same time. You can enter several identities into the text box, separated by commas.

    Invite members to team dialog, choose user account.

    Tip

    You must enter user and group names one at a time. However, after entering a name, the account is added to the list, and you can enter another name in the Identities text box before choosing to save your changes.

    You may need to choose the refresh icon to see your updates.

  5. To add an account as a team administrator, choose the Settings page and then choose Add under the Administrators section. For details, see Add a team administrator

Choose the Current page tab for information on adding a user to a team. The New Teams Page preview feature is only available for Azure DevOps Services at this time.

Remove users or groups from a team

From the team's Members page, you can remove members.

  1. To remove members, open the team's Members page, choose Direct Members, check the checkbox of the user you want to remove, choose More options, and then choose Remove.

    Team profile page, remove a team member, new nav

    Tip

    To remove a team administrator as a team member, you must first remove them as an administrator.

  2. Confirm the removal by choosing Delete in the confirmation message.

    Delete member dialog confirmation.

Choose the Current page tab for information on adding a user to a team. The New Teams Page preview feature is only available for Azure DevOps Services at this time.

Invite users from the Summary page

As a member of the Project Administrators group, you can add members to a project from the Summary page and optionally add them to one or more teams. To learn more about the Summary page, see Share your project vision, view project activity.

Note

For on-premises Azure DevOps, all email actions require an SMTP server to be configured.

  1. Open the Project>Summary page, and choose Invite.

    Screenshot of Summary page, Invite button.

  1. Open the Project>Summary page, and choose the Add button.
    Screenshot of Summary page, Add members button.
  1. For new users, enter their email address. For existing users, type their name until it resolves as a known name to the system. You can add several email addresses or account names by separating them with a semicolon (;).

    Choose the entry listed under Add users to complete the entry.

    If you're adding a user known by the organization or collection, type the name or email address and then choose the name that appears to complete the entry.

    Invite members to a project dialog, unknown user.

    Invite members to a project dialog, enter a known user account.

    Note

    Any valid email address is acceptable. When the user accepts the invitation and signs into Azure DevOps, they register their email address as a Microsoft account and choose a password.

  2. Optionally, select the teams you want to add the user to and then choose Add to complete the invitation.

    When the user is unknown, you'll get a notification that an access level must be assigned. To complete the invitation, choose Add.

    Choose Add to complete the invitation.

    Invite members to a project dialog, unknown user, select teams to add.

    Invite members to a project dialog, known user, select teams to add.

    When adding a new user, the system assigns Stakeholder as the access level when all free five Basic access levels have been assigned. Active contributors to a project need to have Basic access as a minimum. A Project Collection Administrator can change the access level from the Organization Settings>Users page.

    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.

  3. (Optional) A message will briefly display on the screen to indicate success or failure. Choose Details to open the notification and review details.

    Screenshot of notification success message.

    Screenshot of notification failure message.

    A success message indicates the status of adding the user to the system.

    A failure message indicates why the addition of the user failed.

    Notification dialog of Success. ":::

    Notification dialog of failure.

  4. New users receive an email inviting them to sign in to the project. Existing users don't receive any formal notification.

Add users or groups to a project

As a member of the Project Administrators group, you can add users or groups to a project from the Project settings> Permissions page by adding them to a security group. To add a custom security group, see Set permissions at the project- or collection-level.

Note

To enable the new user interface for the Project Permissions Settings Page, see Enable preview features.

  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 Permissions.

    ...

  3. Under Groups, choose one of the following options:

    • Readers: To add users who require read-only access to the project, choose.
    • Contributors: To add users who contribute fully to this project or who have been granted Stakeholder access.
    • Project Administrators: To add users who need to administrate the project. To learn more, see Set permissions at the project-level or project collection-level.

    Or, you can choose any team group to add users to a specific team.

    Here we choose the Contributors group.

    Security page, Contributors group

  4. Next, choose the Members tab.

    The default team group, and any other teams you add to the project, get included as members of the Contributors group. Add a new user as a member of a team instead, and the user automatically inherits Contributor permissions.

    Tip

    Managing users is much easier using groups, not individual users.

  5. Choose Add to add a user or a user group.

    Security page, Contributors group, Members page, Add button

  6. 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 requirements.

    Add users and group dialog.

    Note

    The first time you add a user or group to Azure DevOps, you can't browse to it or check the friendly name. After the identity has been added, you can just enter the friendly name.

    Choose Save when done.

  7. You may customize user permissions for other functionality in the project. For example, in areas and iterations or shared queries.

Choose the Current page tab for information on adding a user to a project. The Project Permissions Settings Page preview feature is only available for Azure DevOps Services at this time.

Manage users or resend invitations

Project Collection Administrators can update user assignments and resend invitations. The various options they have are:

  • Change the access level
  • Manage user - add them to select projects
  • Resend invite
  • Remove direct assignments
  • Remove from organization

To learn more, see Add account users for Azure DevOps.

Screenshot of Organization Settings>Users page, Manage user options.

List team members or team details

From the Azure DevOps CLI command, you can see details about a team or list the individual members of that team. To first see a list of all teams in your organization, use the az devops team list command.

List team members | Show team details

Note

You can use the az devops user command to add users to an organization. There is no comparable command for adding users to a team or project.

List team members

You can list the individual members of a team in your organization with the az devops team list-member command. To get started, see Get started with Azure DevOps CLI.

az devops team list-member --team
                           [--org]
                           [--project]
                           [--skip]
                           [--top]

Parameters

  • team: Required. Name or ID of the team to show.
  • org: Azure DevOps organization URL. You can configure the default organization using az devops configure -d organization=ORG_URL. Required if not configured as default or picked up using git config. Example: --org https://dev.azure.com/MyOrganizationName/.
  • project: Name or ID of the project. You can configure the default project using az devops configure -d project=NAME_OR_ID. Required if not configured as default or picked up using git config.
  • skip: Optional. Number of members to skip.
  • top: Optional. Maximum number of members to return.

Example

The following command lists the first five members of the team named Fabrikam Team and returns the details in table format.

az devops team list-member --team "Fabrikam Team" --top 5 --output table

ID                                    Name               Email
------------------------------------  -----------------  --------------------------
3b5f0c34-4aec-4bf4-8708-1d36f0dbc468  Christie Church    fabrikamfiber1@hotmail.com
19d9411e-9a34-45bb-b985-d24d9d87c0c9  Johnnie McLeod     fabrikamfiber2@hotmail.com
8c8c7d32-6b1b-47f4-b2e9-30b477b5ab3d  Chuck Reinhart     fabrikamfiber3@hotmail.com
d291b0c4-a05c-4ea6-8df1-4b41d5f39eff  Jamal Hartnett     fabrikamfiber4@hotmail.com
bd30c189-db0f-4dd6-9418-5d8b41dc1754  Raisa Pokrovskaya  fabrikamfiber5@hotmail.com

Show team details

You can view details about a team in your organization with the az devops team show command. To get started, see Get started with Azure DevOps CLI.

az devops team show --team
                    [--org]
                    [--project]

Parameters

  • team: Required. Name or ID of the team to show.
  • org: Azure DevOps organization URL. You can configure the default organization using az devops configure -d organization=ORG_URL. Required if not configured as default or picked up using git config. Example: --org https://dev.azure.com/MyOrganizationName/.
  • project: Name or ID of the project. You can configure the default project using az devops configure -d project=NAME_OR_ID. Required if not configured as default or picked up using git config.

Example

The following command shows information about the team in your organization named Fabrikam Team and returns the details in table format.

az devops team show --team "Fabrikam Team" --output table

ID                                    Name          Description
------------------------------------  ------------  -------------------------------------------------
a48cb46f-7366-4f4b-baf5-b3632398ed1e  Fabrikam Team  The default project team. Was Fabrikam Fiber Team

Add users or groups to an access level

For on-premises deployments, you may need to set the access level for a user or group, particularly if those groups don't belong to the default access level. To learn more, see Change access levels.

Add users or groups to SQL Server Reports

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

Add users or groups to SharePoint or SQL Server Reports

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

Next steps