Article version: GitHub.com
Choosing the delivery method for your notifications
You can receive your notifications on GitHub or have them delivered through your email client.
In this article
- Choosing the delivery method for notifications about repository activity
- Choosing the delivery method for security alerts for vulnerable dependencies
- Choosing the delivery method for notifications about GitHub Actions
- Choosing the notification delivery method for organizations you belong to
- Further reading
For personal accounts, notification emails are automatically sent to your default notification email. You can also manage which verified email address organizations should send notifications to.
Choosing the delivery method for notifications about repository activity
-
In the upper-right corner of any page, click your profile photo, then click Settings.

-
In the user settings sidebar, click Notifications.

-
Configure how you would like to receive notifications you either participate in or watch by selecting the checkboxes:
- Selecting Email sends an email to your default notification email.
- Selecting Web allows you to access the notifications on GitHub.

-
If you selected Email for conversations you're either participating in or watching, choose which updates you receive by selecting the checkboxes in the "Notification email" section:
- Select Comments on Issues and Pull Requests to receive an email when someone makes a comment in an issue or in the "Conversation" tab of a pull request.
- Select Pull request reviews to receive an email when someone makes a review comment in the "Files changed" tab of a pull request.
- Select Pull request pushes to receive an email when someone adds commits to a pull request that you're subscribed to.
- Select Include your own updates to receive an email when you open, comment on, or close an issue or pull request.

Choosing the delivery method for security alerts for vulnerable dependencies
If your repository has a supported dependency manifest (and if you've set up the dependency graph if it's a private repository), whenever GitHub detects a vulnerable dependency in your repository, you will receive a weekly digest email. You can also configure your security alerts as web notifications, individual email notifications, daily email digests, or alerts in the GitHub interface. For more information, see "About security alerts for vulnerable dependencies."
-
In the upper-right corner of any page, click your profile photo, then click Settings.

-
In the user settings sidebar, click Notifications.

-
Under "Security alerts", configure how you would like to receive notifications when GitHub detects a vulnerable dependency in your repository:

- Selecting UI alerts displays a banner in the GitHub interface.
- Selecting Command Line displays warnings as a callback when you push to a repository with vulnerabilities.
- Selecting Web allows you to access the notifications on GitHub.
- Selecting Email each time a vulnerability is found sends an email to your default notification email.
- Selecting Email a digest summary of vulnerabilities sends a digest email with a summary of up to 10 repositories' security alerts. Use the drop-down menu to choose to receive digest emails daily or weekly.
Choosing the delivery method for notifications about GitHub Actions
If you enable email or web notifications for GitHub Actions, you'll receive a notification when any workflow runs that you've triggered have completed. The notification will include the workflow run's status (including successful, failed, neutral, and canceled runs). You can also choose to receive a notification only when a workflow run has failed.
You can also see the status of workflow runs on a repository's Actions tab. For more information, see "Managing a workflow run."
-
In the upper-right corner of any page, click your profile photo, then click Settings.

-
In the user settings sidebar, click Notifications.

-
Under "GitHub Actions", configure how you would like to receive notifications for workflow runs.

Choosing the notification delivery method for organizations you belong to
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.
Tips:
- You'll only receive notification emails if you've chosen to receive email notifications in your notification settings.
- If an organization you're a member of restricts email notifications to an approved email domain, you'll need to verify an email address in that domain to receive email notifications about activity in the organization. For more information, see "Restricting email notifications to an approved domain."
-
In the upper-right corner of any page, click your profile photo, then click Settings.

-
In the user settings sidebar, click Notifications.

-
Under "Default notification email", select the email address you'd like notifications sent to.

-
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 your verified email addresses. For more information, see "Verifying your email address."
-
In the upper-right corner of any page, click your profile photo, then click Settings.

-
In the user settings sidebar, click Notifications.

-
Under "Custom routing," find your organization's name in the list.

-
Click Edit next to the email address you want to change.

-
Select one of your verified email addresses, then click Save.
