docs/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md

title, intro, redirect_from, versions, topics

title	intro	redirect_from	versions	topics
Configuring notifications	Choose the type of activity on {% data variables.product.prodname_dotcom %} that you want to receive notifications for and how you want these updates delivered.	/articles/about-web-notifications /format-of-notification-emails/ /articles/configuring-notification-emails/ /articles/about-notification-emails/ /articles/about-email-notifications /articles/accessing-your-notifications /articles/configuring-notification-delivery-methods/ /articles/managing-notification-delivery-methods/ /articles/managing-notification-emails-for-organizations/ /articles/choosing-the-delivery-method-for-your-notifications /articles/choosing-the-types-of-notifications-you-receive/ /github/managing-subscriptions-and-notifications-on-github/configuring-notifications /github/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications	fpt ghes ghae ghec * * * *	Notifications

{% ifversion ghes %} {% data reusables.mobile.ghes-release-phase %} {% endif %}

Notification delivery options

You can receive notifications for activity on {% data variables.product.product_location %} in the following locations.

• The notifications inbox in the {% data variables.product.product_location %} web interface{% ifversion fpt or ghes or ghec %}
• The notifications inbox on {% data variables.product.prodname_mobile %}, which syncs with the inbox on {% data variables.product.product_location %}{% endif %}
• An email client that uses a verified email address, which can also sync with the notifications inbox on {% data variables.product.product_location %}{% ifversion fpt or ghes or ghec %} and {% data variables.product.prodname_mobile %}{% endif %}

{% ifversion fpt or ghes or ghec %} {% data reusables.notifications-v2.notifications-inbox-required-setting %} For more information, see "Choosing your notification settings." {% endif %}

{% data reusables.notifications.shared_state %}

Benefits of the notifications inbox

The notifications inbox on {% data variables.product.product_location %}{% ifversion fpt or ghes or ghec %} and {% data variables.product.prodname_mobile %}{% endif %} includes triaging options designed specifically for your {% data variables.product.prodname_dotcom %} notifications flow, including options to:

• Triage multiple notifications at once.
• Mark completed notifications as Done and remove them from your inbox. To view all of your notifications marked as Done, use the is:done query.
• Save a notification to review later. Saved notifications are flagged in your inbox and kept indefinitely. To view all of your saved notifications, use the is:saved query.
• Unsubscribe and remove a notification from your inbox.
• Preview the issue, pull request, or team discussion where the notification originates on {% data variables.product.product_location %} from within the notifications inbox.
• See one of the latest reasons you're receiving a notification from your inbox with a reasons label.
• Create custom filters to focus on different notifications when you want.
• Group notifications in your inbox by repository or date to get a quick overview with less context switching

{% ifversion fpt or ghes or ghec %} In addition, you can receive and triage notifications on your mobile device with {% data variables.product.prodname_mobile %}. For more information, see "Managing your notification settings with GitHub Mobile" or "GitHub Mobile." {% endif %}

Benefits of using an email client for notifications

One benefit of using an email client is that all of your notifications can be kept indefinitely depending on your email client's storage capacity. Your inbox notifications are only kept for 5 months on {% data variables.product.prodname_dotcom %} unless you've marked them as Saved. Saved notifications are kept indefinitely. For more information about your inbox's retention policy, see "About notifications."

Sending notifications to your email client also allows you to customize your inbox according to your email client's settings, which can include custom or color-coded labels.

Email notifications also allow flexibility with the types of notifications you receive and allow you to choose different email addresses for updates. For example, you can send certain notifications for a repository to a verified personal email address. For more information, about your email customization options, see "Customizing your email notifications."

About participating and watching notifications

When you watch a repository, you're subscribing to updates for activity in that repository. Similarly, when you watch a specific team's discussions, you're subscribing to all conversation updates on that team's page. For more information, see "About team discussions."

To see repositories that you're watching, go to your watching page. For more information, see "Managing subscriptions and notifications on GitHub."

{% ifversion ghae or ghes < 3.1 %}

Configuring notifications

{% endif %} You can configure notifications for a repository on the repository page, or on your watching page.{% ifversion ghes < 3.1 %} You can choose to only receive notifications for releases in a repository, or ignore all notifications for a repository.{% endif %}

{% ifversion fpt or ghes > 3.0 or ghae or ghec %}

About custom notifications

You can customize notifications for a repository. For example, you can choose to only be notified when updates to one or more types of events ({% data reusables.notifications-v2.custom-notification-types %}) happen within a repository, or ignore all notifications for a repository. {% endif %} For more information, see "Configuring your watch settings for an individual repository" below.

Participating in conversations

Anytime you comment in a conversation or when someone @mentions your username, you are participating in a conversation. By default, you are automatically subscribed to a conversation when you participate in it. You can unsubscribe from a conversation you've participated in manually by clicking Unsubscribe on the issue or pull request or through the Unsubscribe option in the notifications inbox.

For conversations you're watching or participating in, you can choose whether you want to receive notifications by email or through the notifications inbox on {% data variables.product.product_location %}{% ifversion fpt or ghes or ghec %} and {% data variables.product.prodname_mobile %}{% endif %}.

For example:

• If you don't want notifications to be sent to your email, unselect email for participating and watching notifications.
• If you want to receive notifications by email when you've participated in a conversation, then you can select email under "Participating".

If you do not enable watching or participating notifications for web{% ifversion fpt or ghes or ghec %} and mobile{% endif %}, then your notifications inbox will not have any updates.

Customizing your email notifications

After enabling email notifications, {% data variables.product.product_location %} will send notifications to you as multipart emails that contain both HTML and plain text copies of the content. Email notification content includes any Markdown, @mentions, emojis, hash-links, and more, that appear in the original content on {% data variables.product.product_location %}. If you only want to see the text in the email, you can configure your email client to display the plain text copy only.

{% data reusables.notifications.outbound_email_tip %}

{% data reusables.notifications.shared_state %}

{% ifversion fpt or ghec %}

If you're using Gmail, you can click a button beside the notification email to visit the original issue or pull request that generated the notification.

{% endif %}

Choose a default email address where you want to send updates for conversations you're participating in or watching. You can also specify which activity on {% data variables.product.product_location %} you want to receive updates for using your default email address. For example, choose whether you want updates to your default email from:

• Comments on issues and pull requests.
• Pull request reviews.
• Pull request pushes.
• Your own updates, such as when you open, comment on, or close an issue or pull request.

Depending on the organization that owns the repository, you can also send notifications to different email addresses. Your organization may require the email address to be verified for a specific domain. For more information, see "Choosing where your organization’s email notifications are sent."

You can also send notifications for a specific repository to an email address. For more information, see "About email notifications for pushes to your repository."

{% data reusables.notifications-v2.email-notification-caveats %}

Filtering email notifications

Each email notification that {% data variables.product.product_location %} sends contains header information. The header information in every email is consistent, so you can use it in your email client to filter or forward all {% data variables.product.prodname_dotcom %} notifications, or certain types of {% data variables.product.prodname_dotcom %} notifications.

If you believe you're receiving notifications that don't belong to you, examine the X-GitHub-Recipient and X-GitHub-Recipient-Address headers. These headers show who the intended recipient is. Depending on your email setup, you may receive notifications intended for another user.

Email notifications from {% data variables.product.product_location %} contain the following header information:

Header	Information
From address	This address will always be {% ifversion fpt or ghec %}'notifications@github.com'{% else %}'the no-reply email address configured by your site administrator'{% endif %}.
To field	This field connects directly to the thread.{% ifversion not ghae %} If you reply to the email, you'll add a new comment to the conversation.{% endif %}
Cc address	{% data variables.product.product_name %} will Cc you if you're subscribed to a conversation. The second Cc email address matches the notification reason. The suffix for these notification reasons is {% data variables.notifications.cc_address %}. The possible notification reasons are: assign: You were assigned to an issue or pull request. author: You created an issue or pull request. ci_activity: A {% data variables.product.prodname_actions %} workflow run that you triggered was completed. comment: You commented on an issue or pull request. manual: There was an update to an issue or pull request you manually subscribed to. mention: You were mentioned on an issue or pull request. push: Someone committed to a pull request you're subscribed to. review_requested: You or a team you're a member of was requested to review a pull request. {% ifversion fpt or ghes or ghae-issue-4864 or ghec %} security_alert: {% data variables.product.prodname_dotcom %} detected a vulnerability in a repository you receive alerts for. {% endif %} state_change: An issue or pull request you're subscribed to was either closed or opened. subscribed: There was an update in a repository you're watching. team_mention: A team you belong to was mentioned on an issue or pull request. your_activity: You opened, commented on, or closed an issue or pull request.
mailing list field	This field identifies the name of the repository and its owner. The format of this address is always <repository name>.<repository owner>.{% data variables.command_line.backticks %}.
X-GitHub-Severity field	{% data reusables.repositories.security-alerts-x-github-severity %} The possible severity levels are: low moderate high critical For more information, see "About alerts for vulnerable dependencies."

Choosing your notification settings

{% data reusables.notifications.access_notifications %} {% data reusables.notifications-v2.manage-notifications %} 3. On the notifications settings page, choose how you receive notifications when: - There are updates in repositories or team discussions you're watching or in a conversation you're participating in. For more information, see "About participating and watching notifications." - You gain access to a new repository or you've joined a new team. For more information, see "Automatic watching."{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} - There are new {% data variables.product.prodname_dependabot_alerts %} in your repository. For more information, see "{% data variables.product.prodname_dependabot_alerts %} notification options." {% endif %} {% ifversion fpt or ghec %} - There are workflow runs updates on repositories set up with {% data variables.product.prodname_actions %}. For more information, see "{% data variables.product.prodname_actions %} notification options."{% endif %}{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5668 %} - There are new deploy keys added to repositories that belong to organizations that you're an owner of. For more information, see "Organization alerts notification options."{% endif %}

Automatic watching

By default, anytime you gain access to a new repository, you will automatically begin watching that repository. Anytime you join a new team, you will automatically be subscribed to updates and receive notifications when that team is @mentioned. If you don't want to automatically be subscribed, you can unselect the automatic watching options.

If "Automatically watch repositories" is disabled, then you will not automatically watch your own repositories. You must navigate to your repository page and choose the watch option.

Configuring your watch settings for an individual repository

You can choose whether to watch or unwatch an individual repository. You can also choose to only be notified of {% ifversion fpt or ghes > 3.0 or ghae or ghec %}certain event types such as {% data reusables.notifications-v2.custom-notification-types %} (if enabled for the repository) {% else %}new releases{% endif %}, or completely ignore an individual repository.

{% data reusables.repositories.navigate-to-repo %} 2. In the upper-right corner, select the "Watch" drop-down menu to click a watch option. {% ifversion fpt or ghes > 3.0 or ghae-issue-4910 or ghec %}

The Custom option allows you to further customize notifications so that you're only notified when specific events happen in the repository, in addition to participating and @mentions. {% else %} {% endif %} {% ifversion fpt or ghes > 3.0 or ghae-issue-4910 or ghec %} If you select "Issues", you will be notified about, and subscribed to, updates on every issue (including those that existed prior to you selecting this option) in the repository. If you're @mentioned in a pull request in this repository, you'll receive notifications for that too, and you'll be subscribed to updates on that specific pull request, in addition to being notified about issues. {% endif %}

Choosing where your organization’s email notifications are sent

If you belong to an organization, you can choose the email account you want notifications for organization activity sent to. For example, if you belong to an organization for work, you may want your notifications sent to your work email address, rather than your personal address.

{% data reusables.notifications-v2.email-notification-caveats %}

{% data reusables.notifications.access_notifications %} {% data reusables.notifications-v2.manage-notifications %} 3. Under "Default notification email", select the email address you'd like notifications sent to. 4. Click Save.

Customizing email routes per organization

If you are a member of more than one organization, you can configure each one to send notifications to any of{% ifversion fpt or ghec %} your verified email addresses{% else %} the email addresses for your account{% endif %}. {% ifversion fpt or ghec %} For more information, see "Verifying your email address."{% endif %}

{% data reusables.notifications.access_notifications %} {% data reusables.notifications-v2.manage-notifications %} 3. Under "Custom routing," find your organization's name in the list. 4. Click Edit next to the email address you want to change. 5. Select one of your verified email addresses, then click Save.

{% ifversion fpt or ghes or ghae-issue-4864 or ghec %}

{% data variables.product.prodname_dependabot_alerts %} notification options

{% data reusables.notifications.vulnerable-dependency-notification-enable %} {% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization2 %} {% data reusables.notifications.vulnerable-dependency-notification-options %}

For more information about the notification delivery methods available to you, and advice on optimizing your notifications for {% data variables.product.prodname_dependabot_alerts %}, see "Configuring notifications for vulnerable dependencies." {% endif %}

{% ifversion fpt or ghes or ghec %}

{% data variables.product.prodname_actions %} notification options

Choose how you want to receive workflow run updates for repositories that you are watching that are set up with {% data variables.product.prodname_actions %}. You can also choose to only receive notifications for failed workflow runs.

{% endif %}

{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5668 %}

Organization alerts notification options

If you're an organization owner, you'll receive email notifications by default when organization members add new deploy keys to repositories within the organization. You can unsubscribe from these notifications. On the notification settings page, under "Organization alerts", unselect Email.

{% endif %}

{% ifversion fpt or ghes or ghec %}

Managing your notification settings with {% data variables.product.prodname_mobile %}

When you install {% data variables.product.prodname_mobile %}, you will automatically be opted into web notifications. Within the app, you can enable push notifications for the following events.

• Direct mentions
• Assignments to issues or pull requests
• Requests to review a pull request
• Requests to approve a deployment

You can also schedule when {% data variables.product.prodname_mobile %} will send push notifications to your mobile device.

{% data reusables.mobile.push-notifications-on-ghes %}

Managing your notification settings with {% data variables.product.prodname_ios %}

1. In the bottom menu, tap Profile.
2. To view your settings, tap {% octicon "gear" aria-label="The Gear icon" %}.
3. To update your notification settings, tap Notifications and then use the toggles to enable or disable your preferred types of push notifications.
4. Optionally, to schedule when {% data variables.product.prodname_mobile %} will send push notifications to your mobile device, tap Working Hours, use the Custom working hours toggle, and then choose when you would like to receive push notifications.

Managing your notification settings with {% data variables.product.prodname_android %}

1. In the bottom menu, tap Profile.
2. To view your settings, tap {% octicon "gear" aria-label="The Gear icon" %}.
3. To update your notification settings, tap Configure Notifications and then use the toggles to enable or disable your preferred types of push notifications.
4. Optionally, to schedule when {% data variables.product.prodname_mobile %} will send push notifications to your mobile device, tap Working Hours, use the Custom working hours toggle, and then choose when you would like to receive push notifications.

Configuring your watch settings for an individual repository with {% data variables.product.prodname_mobile %}

You can choose whether to watch or unwatch an individual repository. You can also choose to only be notified of {% ifversion fpt or ghec %}certain event types such as issues, pull requests, discussions (if enabled for the repository) and {% endif %}new releases, or completely ignore an individual repository.

1. On {% data variables.product.prodname_mobile %}, navigate to the main page of the repository.
2. Tap Watch.
3. To choose what activities you receive notifications for, tap your preferred watch settings.

{% endif %}