> For the complete documentation index, see [llms.txt](https://help.cerby.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.cerby.com/cerby-mobile-app/app-customization/use-the-notification-center/mark-notifications-as-read.md).

# Mark notifications as read

This article describes how to mark notifications as read in the Cerby mobile app.

{% hint style="info" %}
**Who can use this feature?**

* Workspace **Owners**, **Super Admins**, **Admins**, **Users**, **Login-Only**, and **Guest Users**
* Only supported using the Cerby mobile app
  {% endhint %}

Notifications are marked as read automatically when you tap them to view their details. Read status syncs across all your devices, so marking a notification as read on one device marks it as read everywhere you are logged in to Cerby.

To mark all notifications as read at once, complete the following steps:

1. Open the Cerby mobile app on your mobile phone.
2. Log in to your [Cerby](https://app.cerby.com/) workspace.
3. Tap the bell icon in the upper-right corner of the screen. The **Notification Center** is displayed.
4. Tap **Mark all as read** at the top of the screen. All notifications are marked as read and the unread badge is cleared.

{% hint style="info" %}
**NOTE:** On iOS, notifications are also marked as read automatically as you scroll past them while they are visible on screen.
{% endhint %}

## Related articles

* [Open the Notification Center](/cerby-mobile-app/app-customization/use-the-notification-center/open-the-notification-center.md)
* [Configure notification settings](/cerby-mobile-app/app-customization/use-the-notification-center/configure-notification-settings.md)


---

# 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://help.cerby.com/cerby-mobile-app/app-customization/use-the-notification-center/mark-notifications-as-read.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.