Manage notifications for a team, group, or organization

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

Your team or group can receive email notifications as changes occur to the following items in Azure DevOps:

  • work items
  • code reviews
  • pull requests
  • source control files
  • builds

For example, when a high priority work item is assigned to your team's area path, a notification email gets sent to the team.

Note

The notifications user interface changed with TFS 2017 Update 1. If you are working on TFS 2017 or earlier version, change the content version selector for this article to TFS 2015.

Prerequisites

You must be a Team-, Project-, or Project Collection Administrator to create group and team notifications. If you're not an administrator, get added as one. For more information, see Notification types.

Note

For on-premises Azure DevOps Server, configure an SMTP server for team members to see the Notifications option from their organization or user profile menu and to receive notifications.

Create an email subscription

A subscription lets you control what your team is notified of and how the team receives those notifications. For more information, see notification types.

  1. Sign in to your organization (https://dev.azure.com/{yourorganization}).

  2. Select Project settings > Notifications.

    Screenshot of Project settings and Notifications highlighted

  3. Select New subscription.

    Screenshot of New subscription highlighted.

  4. Select the type of activity you want your team to be notified of.

    Screenshot of select event category and template page.

  5. Provide a description to help you identify the subscription later.

    Screenshot of a description provided.

  6. Choose which team members should receive a notification:

    Screenshot of Deliver to and Roles dropdown menus.

    Choose from one of the following delivery options:

    Delivery option Description
    Team members by role Only certain team members associated with the event are notified. For example, for work item changes, you might only want the current assignee of the work item to receive a notification.
    Team preference Use the team's default delivery preference. For more information, see Manage delivery settings.
    Custom email address Send an email to a specified email address.
    All team members Send an individual email to each member of the team.

    For certain activities, when you select Team members by role, you can choose to have the user that initiated the activity receive a notification. This notification is controlled by the Skip initiator checkbox. By default, this box is checked, meaning the user that starts the change isn't notified about it.

    Tip

    For Team members by role, each role is fairly self-explanatory. However, the following two roles may need some further explanation.

    Changed reviewers applies to any reviewer that's added or deleted, as a result of policies defined for the set of files. For example, a push to a pull request (PR) could introduce a change to File1.cs. If there’s a policy which says that Person A needs to review changes to File1.cs, they’d be in the Changed reviewers role for that iteration of the PR.

    The Reset reviewers role is related to the “reset votes” policy. For example, the repo has configured the policy, “Reset votes on new pushes”. Person B, who was required on the PR, has already approved this PR. Because of the reset votes policy, their vote has been reset. Thus, she’s in the Reset reviewers role for that iteration.

  7. Choose whether you want to receive notifications about activity in all projects or only a specific project.

    Screenshot of selected scope.

  8. Optionally, configure additional filter criteria.

    Screenshot of configuring additional filter criteria.

  9. Select Finish to save the new subscription.

  1. Sign in to your organization (https://dev.azure.com/{yourorganization}).

  2. Select Project settings > Notifications.

    Screenshot of Project settings and Notifications highlighted

  3. Select New subscription.

    New subscription is highlighted.

  4. Select the type of activity you want your team to be notified of.

    Select event category and template.

  5. Provide a description to help you identify the subscription later.

    Provide a description.

  6. Choose which team members should receive a notification:

    Select role.

    Choose from one of the following delivery options:

    Delivery option Description
    Team members by role Only certain team members associated with the event are notified. For example, for work item changes, you might only want the current assignee of the work item to receive a notification.
    Team preference use the team's default delivery preference. For more information, see Manage delivery settings.
    Custom email address Send an email to a specified email address.
    All team members Send an individual email to each member of the team.

    For certain activities, when you select Team members by role, you can choose to have the user that initiated the activity receive a notification. This notification is controlled by the Skip initiator checkbox. By default, this box is checked, meaning the user that starts the change isn't notified about it.

    Tip

    For Team members by role, each role is fairly self-explanatory. However, the following two roles may need some further explanation. Changed reviewers applies to any reviewer that's added or deleted, as a result of policies defined for the set of files. For example, a push to a pull request (PR) could introduce a change to File1.cs. If there’s a policy which says that Person A needs to review changes to File1.cs, they’d be in the Changed reviewers role for that iteration of the PR. The Reset reviewers role is related to the “reset votes” policy. For example, the repo has configured the policy, “Reset votes on new pushes”. Person B, who was required on the PR, has already approved this PR. Because of the reset votes policy, their vote has been reset. Thus, she’s in the Reset reviewers role for that iteration.

  7. Choose whether you want to receive notifications about activity in all projects or only a specific project.

    Select scope

  8. Optionally, configure additional filter criteria.

    Configure additional filter criteria.

  9. Select Finish to save the new subscription.

  1. Open the Notifications page in Team settings: https://dev.azure.com/{organization}/{project}/_admin/_notifications?view=contents

    Go to team notifications page

  2. Select New subscription.

    New subscription

  3. Select the type of activity you want your team to be notified of.

    Select event category and template

  4. Provide a description to help you identify the subscription later.

    Provide a description.

  5. Choose which team members should receive a notification:

    Select role

    Choose from one of the following delivery options:

    Deliver to Description
    Members of Azure DevOps by role Only certain team members associated with the event are notified. For example, for work item changes, you might only want the current assignee of the work item to receive a notification.
    Team preference use the team's default delivery preference. For more information, see Manage delivery settings.
    Custom email address Send an email to a specified email address.
    Members of Azure DevOps Send an individual email to each member of the team.
    SOAP Send to an email address.

    See the following roles and their descriptions:

    Roles Description

    For certain activities, when you select Team members by role, you can choose to have the user that initiated the activity receive a notification. This notification is controlled by the Skip initiator checkbox. By default, this box is checked, meaning the user that starts the change isn't notified about it.

  6. Choose whether you want to receive notifications about activity in all projects or only a specific project.

    Select scope

  7. Optionally, configure additional filter criteria.

    Configure additional filter criteria.

  8. Select Finish to save the new subscription.

Tip

If you don't want to receive a notification for an event that you initiated, you can turn on the option, Skip initiator. For more information, see Exclude yourself from notification emails for events that you initiate.

Manage global delivery settings

Global notifications apply to all projects defined for an organization or collection. Choose to allow or block delivery of emails for all subscriptions owned by a team or a group. It's a default setting which applies only if the team or group hasn't explicitly set the option. For more information, see Global notifications.

Tip

We don't support organization-wide notifications. As an alternative, you can provide an email distribution list that goes to your entire organization. Also, you can generate a banner with the az devops banner command that all users see when they sign in.

Tip

You can send an email to all collections in an application tier. See Configure an SMTP server and customize email for alerts and feedback requests. Also, you can generate a banner with the az devops banner command that all users see when they sign in.

Tip

You can send an email to all collections in an application tier. See Configure an SMTP server and customize email for alerts and feedback requests.

  1. Sign in to your organization (https://dev.azure.com/{yourorganization}).

  2. Select gear icon Organization settings.

    Open Organization settings

  3. Select Global notifications > Subscribers, enter and find your group, and then select Delivery settings.

    Group notification settings

  4. Choose which option best fits your group's needs, and then select Save.

    Delivery settings options for group.

Your group delivery settings are updated for notifications.

Manage team and project delivery settings

  1. Sign in to your organization (https://dev.azure.com/{yourorganization}).

  2. Select Project settings > Notifications.

    Screenshot of Project settings and Notifications highlighted.

  3. Choose Delivery settings:

    Delivery settings

  4. Choose which option best fits your team's needs:

    Delivery settings options for team and project.

Your team delivery settings are updated for notifications.

Set alerts for your team

  1. Open team alerts from Manage TFS Alerts.

    Open team alerts

  2. Expand the team and open Select New Alert Template.

    Work Item Alerts link on the Alerts admin page

  3. Choose an alert type.

    Choose an alert type for the team

  4. Notice how the subscriber is set to the team context. Alerts are sent to each team member based on their preferred email address, which they set through their profile.

    Subscriber set to team context

    Tip

    For the team context, the alert query interprets the @Me variable as anyone who is a member of the team.

You can set filters for as many as 20 different alert types, specify the email addresses for yourself and other team members, and select the delivery format. Also, you can set team alerts to keep all team members notified of important changes.

Set alerts for a project

To set alerts for a project, you must be a member of the Project Collection Administrator or Team Foundation Administrator groups. To get added, see Add an administrator. If you're not a member of these groups, you won't see the options available for administering alerts.

As an administrator, you can view, create, edit, and delete alerts for team members and teams.

View alerts set for a project

  • From the web admin page for a project, open the Alerts tab and expand All alerts.

    Expand All Alerts

Find alerts set for a team member or team

  • Choose the name of the team member from the drop-down list, or type the name in the search box.

    Choose the team member whose alerts you want to edit

    Alerts listed for selected team member

Create, edit, or delete an alert

  1. To create an alert for a team member, first find the alerts defined for that subscriber as described in the previous step. Then, create an alert in the same way that a team member creates alerts.

    Create an alert for a team member

    To create an alert for a team, first find the alerts assigned to that team, and then create an alert in the same way. The team should appear in the Subscriber field.

  2. To edit or delete an alert, open it from the short cut menu.

    Open or delete an alert for a team member

Unsubscribe or opt out of a team or out-of-box (OOB) notification subscription

You can choose to not receive notifications for certain team notification subscriptions by opting out.

To access the Preview features options, open your profile menu. The profile menu appears, as shown, based on whether the New Account Manager feature is enabled.

  1. Sign in to your organization (https://dev.azure.com/{yourorganization}).

  2. Select User settings, and then select Notifications from the resulting list.

    Screenshot of personal notifications, preview page.

  3. To unsubscribe from any notification, slide the state On/Off indicator ot the Off position.

To unsubscribe from any notification, slide the state On/Off indicator ot the Off position. For example, here we turn off the "Build completes" notification subscription.

Screenshot of unsubscribe from Build completes notification subscription.

Note

Whether or not you're an administrator, when you move the toggle for a shared team notification subscription in your settings only impacts you and not other team members.