Notifications#
The MEGA inbox keeps repository and community activity in one place. Open Notifications to review unread items and follow their links back to the relevant repository, discussion, paper, or account page.
What appears in the inbox#
You may receive notifications for repository activity, replies and reactions in discussions or paper conversations, moderation outcomes, and important account or service notices. An item is visible only to the account it was sent to; it does not reveal private repositories or private activity to other people.
Use the unread filter to focus on new activity. Select one or more items to mark them read, or mark the whole current inbox read after you have reviewed it.
Choose activity preferences#
Open Settings → Notifications to control whether repository activity and discussion activity appear in your inbox and whether each category can also be delivered by email. Pull Request review requests belong to discussion activity. Their dedicated email identifies the contributor, PR, and repository and links directly to the browser review. Email delivery is asynchronous and preference-controlled; the Inbox and the underlying Pull Request remain authoritative if an email is delayed. Security and essential account notices remain visible so that an account cannot accidentally hide information needed to protect access.
Preferences affect new inbox views; they do not change repository permissions, memberships, subscriptions, or the history of an underlying discussion.
Manage noisy activity#
If a repository or conversation is generating more activity than you need, review its watch or participation settings before disabling a whole category. You can still return to the repository or discussion directly at any time.
Notifications are an inbox feature, not a workflow log. For a durable project record, use repository history, pull requests, and discussions.
Privacy and safety#
- Do not paste tokens, private keys, or secret values into a reply just because you reached it from a notification.
- Treat links as context, then confirm the repository owner and URL before a write or download action.
- Revoke an unfamiliar session and review tokens if an account-security notice looks unexpected. See Account Security.
The inbox endpoints are designed for a signed-in web session. Use the documented repository, discussion, and webhook APIs when building automation.