> For the complete documentation index, see [llms.txt](https://docs.mailtrap.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mailtrap.io/account-and-organization/notification-center.md).

# Notification center

In-app notifications help you stay informed about important changes and actions related to your account directly inside the application.

These notifications are closely connected with email notifications. In most cases, everything you receive by email is also available in the in-app notifications center. This gives you one central place to review updates, warnings, and actions that may require your attention.

### What can you do with notifications?

Every notification includes a call to action (CTA).

Depending on the notification type, the CTA allows you to:

* Review additional details,
* Fix an issue,
* Update settings,
* Or complete any other required action.

Notifications are designed to help you quickly understand what happened and what can be done next without searching through different parts of the application.

### Notification status

There are two different notification statuses:

{% tabs %}
{% tab title="Mark as read" %}
A notification becomes marked as read when you click its action link / CTA.

After that:

* the notification is no longer highlighted as unread,
* but it still remains visible in the notifications list.
  {% endtab %}

{% tab title="Archive notifications" %}

### Archive notifications

If you no longer need a notification, you can move it to the archive.

To archive a notification:

1. Open the notifications center.
2. Click the **Archive** button next to the notification.

Archived notifications are removed from the main notifications view.
{% endtab %}
{% endtabs %}

### Notification severity levels

Notifications use three severity levels to help you understand how important they are.

### Info

Used for standard informational updates when no immediate action is required. Examples:

* “Dedicated IP request received”
* “Suppression list export is available - check your email.”

<figure><img src="https://1476453098-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FS3xyr7ba7aGO19rc8dSK%2Fuploads%2F9CglMlh6iViw6AWpoem7%2FScreenshot%202026-05-20%20at%2012.30.07.png?alt=media&amp;token=adbe5458-ce04-4369-99a9-133721b1aeeb" alt="" width="375"><figcaption></figcaption></figure>

#### Critical

Used when there is a serious problem affecting the account. Critical notifications should be reviewed as soon as possible. Examples:

* “SMTP credentials leak detected for a domain.”
* “Email Live Sending subscription has been downgraded to Free due to failed payment”

<figure><img src="https://1476453098-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FS3xyr7ba7aGO19rc8dSK%2Fuploads%2FBcWtYghUDueUnbNd294F%2FScreenshot%202026-05-20%20at%2012.30.29.png?alt=media&amp;token=05dac692-4c2e-4964-a61b-3beb82ee64c9" alt="" width="375"><figcaption></figcaption></figure>

#### Warning

Used when an action is recommended. Examples:

* “Add sender information to approve a domain.”
* “Email Live Sending subscription expires in 7 days (payment failed again)”

<figure><img src="https://1476453098-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FS3xyr7ba7aGO19rc8dSK%2Fuploads%2Fd1VvbVzbJqFTCTFZpwJC%2FScreenshot%202026-05-20%20at%2012.30.42.png?alt=media&amp;token=d696f3ab-5e5a-4833-99f9-1e693da00479" alt="" width="375"><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.mailtrap.io/account-and-organization/notification-center.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
