manage-team-group-global-organization-notifications.md

title	titleSuffix	description	ms.subservice	ms.assetid	ms.custom	ms.author	author	ms.topic	ms.date	monikerRange
Manage notifications for a team, project, organization, or collection	Azure DevOps	Learn how to configure team, project, and organization/collection notifications for when changes occur to source code, git, work items, and builds in Azure DevOps.	azure-devops-notifications	6edc44d0-2729-46f5-8108-c8a5160a6a7a	cross-project	chcomley	chcomley	how-to	09/05/2024	<= azure-devops

Manage notifications for a team, project, or organization

[!INCLUDE version-lt-eq-azure-devops]

You can manage email notifications at team, project, and organization levels when changes occur to work items, code reviews, pull requests, source control files, and 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. For more information, see Notification types.

Prerequisites

[!INCLUDE prerequisites-notifications]

[!INCLUDE note-smtp-server]

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.

::: moniker range="azure-devops"

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

2. Select Project settings > Notifications.

   :::image type="content" source="media/nav-team-notifications-hub-newnav.png" alt-text="Screenshot of Project settings and Notifications highlighted":::

3. Select New subscription.

   

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

   

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

   

6. Choose which team members should receive a notification:

   

   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.
   SOAP	Send email notifications to subscribers of SOAP service.

   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.

   

8. Optionally, configure more filter criteria.

   

9. Select Finish to save the new subscription.

::: moniker-end

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

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

2. Select Project settings > Notifications.

   :::image type="content" source="media/nav-team-notifications-hub-newnav.png" alt-text="Screenshot of Project settings and Notifications highlighted":::

3. Select New subscription.

   

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

   

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

   

6. Choose which team members should receive a notification:

   

   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.

   

8. Optionally, configure more filter criteria.

   

9. Select Finish to save the new subscription.

::: moniker-end

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.

::: moniker range="azure-devops"

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.

::: moniker-end

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

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 to communication with users without sending out mass emails. For more information, see Add and manage information banners in Azure DevOps.

::: moniker-end

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

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.

::: moniker-end

[!INCLUDE opt-out-notification]

Related articles

• Manage your personal notification settings
• Set your notification preferences
• Review default and supported notifications
• Follow a specific work item
• Change your preferred email address