|
1 | 1 | ---
|
2 | 2 | title: Get started with notifications in Azure DevOps
|
3 |
| -description: Understand how notifications or alerts are managed in Azure DevOps |
| 3 | +description: Understand how notifications or alerts are managed in Azure DevOps. |
4 | 4 | ms.technology: devops-collab
|
5 | 5 | toc: show
|
6 | 6 | ms.author: chcomley
|
7 | 7 | author: chcomley
|
8 | 8 | ms.topic: conceptual
|
9 |
| -ms.date: 12/30/2019 |
| 9 | +ms.date: 10/09/2020 |
10 | 10 | monikerRange: '>= tfs-2013'
|
11 | 11 | ---
|
12 | 12 |
|
13 | 13 | # About notifications
|
14 | 14 |
|
15 | 15 | [!INCLUDE [version-all](../includes/version-all.md)]
|
16 | 16 |
|
17 |
| -Notifications help you and your team stay informed about activity that occurs within your Azure DevOps projects. You're notified when changes occur to work items, code reviews, pull requests, source control files, and builds. You can be notified via email. For example, you can get notified whenever you resolve a bug or are assigned a work item. |
| 17 | +Notifications help you and your team stay informed about activity that occurs within your projects in Azure DevOps. You're notified when changes occur to the following items: |
| 18 | +- work items |
| 19 | +- code reviews |
| 20 | +- pull requests |
| 21 | +- source control files |
| 22 | +- builds |
18 | 23 |
|
19 |
| -You receive notifications based on rules or subscriptions. Subscriptions arise from the following instances: |
| 24 | +For example, you can get notified whenever you or your team resolves a bug or are assigned a work item. |
20 | 25 |
|
21 |
| -- Out of the box or default |
| 26 | +You receive notifications based on rules or subscriptions. |
| 27 | +Subscriptions arise from the following instances: |
| 28 | + |
| 29 | +- Out-of-the-box (OOB) or default |
22 | 30 | - Created by an administrator for a team or group that you belong to
|
23 | 31 | - Created by you
|
24 | 32 |
|
25 |
| -You can manage your notifications, which you access from your organization menu. Other notifications are managed by an administrator at the following levels: |
| 33 | +## Notification types |
| 34 | + |
| 35 | +There are four types of notifications that you can manage in Azure DevOps. See the following table of the notification types and required permission or role to manage. |
| 36 | + |
| 37 | +| Notification type | Role required to manage | |
| 38 | +|---------------------------------------------|-------------------------------------------------------| |
| 39 | +|[Personal notifications](#personal-notifications) | User | |
| 40 | +|[Team notifications](#team-and-project-level-notifications) | Team Administrator or member of the Project Administrators group or Project Collection Administrators group | |
| 41 | +|[Project notifications](#team-and-project-level-notifications) | Member of the Project Administrators group or Project Collection Administrators group | |
| 42 | +|[Global notifications](#global-notifications)| Member of the Project Collection Administrators group | |
| 43 | + |
| 44 | +### Personal notifications |
| 45 | + |
| 46 | +You can manage your personal notifications in the following manner. |
| 47 | + |
| 48 | +* View your notifications |
| 49 | +* Set alerts just for yourself |
| 50 | +* View and edit all subscriptions |
| 51 | +* Add a custom subscription |
| 52 | +* Unsubscribe or opt out of a team or project subscription |
| 53 | + |
| 54 | +For more information, see [Manage your personal notifications](manage-your-personal-notifications.md). |
| 55 | + |
| 56 | +### Team and project-level notifications |
| 57 | + |
| 58 | +You can create a subscription for the following categories and select from the following templates. |
| 59 | + |
| 60 | +|Category |Template options | |
| 61 | +|---------|---------| |
| 62 | +|Build | <ul><li>a build completes</li><li>a build fails</li><li>a legacy XAML build controller or agent's status changes</li><li>a legacy XAML build's quality changes</li></ul> | |
| 63 | +|Code (Git) | <ul><li>a commit is pushed</li><li>a pull request is created or updated</li><li>a pull request my team is a reviewer on is updated</li><li>a comment is made on a pull request</li></ul> | |
| 64 | +|Code (TFVC) | <ul><li>code is checked in</li><li>code is checked in with a policy override</li><li>a file with a specific extension is checked in</li><li>a file under a specific path is checked in</li><li>any code review changes</li></ul> | |
| 65 | +|Pipelines | <ul><li>run stage waiting for approval</li><li>run stage waiting for Manual validation</li></ul> |
| 66 | +|Work | <ul><li>a work item is created</li><li>a work item is changed</li><li>a work item is deleted</li><li>a work item is restored</li><li>a work item is moved from this team project</li></ul> | |
| 67 | +|Artifacts | <ul><li>a package is changed</li></ul> | |
| 68 | +|Extension management | <ul><li>an extension is modified</li></ul> | |
| 69 | +|Release | <ul><li>an approval for a deployment is pending</li><li>a deployment is completed</li><li>a request for release creation failed</li><li>a manual intervention for a deployment is pending</li></ul> | |
| 70 | + |
| 71 | +For more information, see [Manage team, group, and global notifications](manage-team-group-global-organization-notifications.md). |
| 72 | + |
| 73 | +### Global notifications |
| 74 | + |
| 75 | +Global notifications apply to all **projects** defined for an organization or collection. |
| 76 | + |
| 77 | +#### Default subscription |
| 78 | + |
| 79 | +The **Default subscriptions** tab lists all default global subscriptions available. The globe icon on a notification subscription indicates the subscription is a default subscription. View all [default notification subscriptions](./oob-built-in-notifications.md). |
| 80 | + |
| 81 | +Members of the **Project Collection Administrators** group have permission to enable/disable any default subscription in this view. Any member of the **Project Collection Valid Users** group has permission to view the details of the default subscription. The view and enable options are available in the context menu (`...`) associated with each individual subscription. |
| 82 | + |
| 83 | + :::image type="content" source="media/view-organization-notification-default-subscriptions.png" alt-text="Screenshot of the organization-level notifications page: Default subscriptions tab."::: |
| 84 | + |
| 85 | +#### Subscribers |
| 86 | + |
| 87 | +The **Subscribers** section begins with an empty identity search box. Enter any group, team, or individual to view the list of subscriptions associated with the specified identity. |
| 88 | + |
| 89 | +All notification subscriptions for the chosen identity are listed in this view. Management options are available from the context menu (`...`) associated with each subscription. The  icon on subscription row indicates a default subscription. |
| 90 | + |
| 91 | + :::image type="content" source="media/view-organization-notification-subscribers.png" alt-text="Screenshot of organization-level notifications page: Subscribers list."::: |
| 92 | + |
| 93 | +#### Statistics |
| 94 | + |
| 95 | +The **Statistics** section shows the most active notification subscriptions and the top event initiators (group, team, or individual). The statistics are only for the current day and reset at 00:00 UTC. A benefit of these statistics is identifying unintended high volume subscriptions or event initiators. |
| 96 | + |
| 97 | + :::image type="content" source="media/view-organization-notification-stats.png" alt-text="Screenshot of organization-level notifications page, Statistics section."::: |
| 98 | +#### Settings |
| 99 | + |
| 100 | +Manage global-level **Settings**, such as delivery preferences. |
| 101 | + |
| 102 | +The **Settings** section allows organization-level notification settings to be managed by any member of the **Project Collection Administrators** group. All teams and groups inherit the _Default delivery option_ setting, which is why it isn't explicitly set at the team or group level. |
| 103 | + |
| 104 | + :::image type="content" source="media/view-organization-notification-settings.png" alt-text="Screenshot of organization-level notifications page: Settings."::: |
| 105 | + |
| 106 | +For more information, see [Manage team, group, and global notifications](manage-team-group-global-organization-notifications.md). |
| 107 | + |
| 108 | +## Permissions for notifications |
| 109 | + |
| 110 | +There are no UI permissions associated with managing email notifications or alerts. Instead, they can be managed using the [TFSSecurity command line tool](https://docs.microsoft.com/azure/devops/server/command-line/tfssecurity-cmd#collection-level-permissions). |
26 | 111 |
|
27 |
| -- Team notifications, managed by a team administrator |
28 |
| -- Project notifications, managed by a member of the Project Administrators group |
29 |
| -- Organization/collection-level notifications, managed by a member of the Project Collection Administrators group |
| 112 | +- By default, members of the project level **Contributors** group can subscribe to alerts for themselves. |
| 113 | +- Members of the **Project Collection Administrators** group, or users who have **Edit collection-level information** permission can set alerts in that collection for others or for a team. |
| 114 | +- Members of the **Project Administrators** group, or users who have **Edit project-level information** permissions can set alerts in that project for others or for a team. |
30 | 115 |
|
31 | 116 | ## Preferred email address
|
32 | 117 |
|
@@ -55,7 +140,7 @@ You can also use a third-party service like Zapier to send notifications to hund
|
55 | 140 |
|
56 | 141 | ## On-premises SMTP server
|
57 | 142 |
|
58 |
| -For on-premises Azure DevOps, [you must configure an SMTP server](/azure/devops/server/admin/setup-customize-alerts) in order for team members to see the Notifications option from their organization menu and to receive notifications. |
| 143 | +[!INCLUDE [note-smtp-server](includes/note-smtp-server.md)] |
59 | 144 |
|
60 | 145 | ::: moniker-end
|
61 | 146 |
|
|
0 commit comments