> 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.md).

# Use the Notification Center

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

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

The Notification Center is an in-app inbox that collects security events requiring your attention: identity confirmation requests, trusted device approvals, new device and location alerts, account sharing notifications, and one-time password (OTP) code deliveries. Unlike push notifications, which arrive on your lock screen and disappear, the Notification Center keeps a persistent record of all events so you can review and act on them at any time. When you have unread notifications, a badge appears on the Cerby app icon and on the bell icon inside the app.

## Open the Notification Center

To open the Notification Center, complete the following steps:

1. Open the Cerby app.
2. Tap the bell icon in the upper-right corner of the screen. The **Notification Center** is displayed, with the most recent events at the top.

Notifications are grouped by date. Unread notifications appear with a highlighted indicator. Scroll down to load older notifications.

{% hint style="info" %}
The unread badge on the bell icon reflects notifications from the past seven days only. Notifications older than seven days do not affect the badge count.
{% endhint %}

## Notification types

The Notification Center includes the following notification types:

| Notification type           | Description                                                               | Action required                                 |
| --------------------------- | ------------------------------------------------------------------------- | ----------------------------------------------- |
| **Identity confirmation**   | Cerby needs to verify your identity before completing a sensitive action. | Tap **Approve** or **Deny**.                    |
| **Trusted device request**  | A new device has requested approval to join your trusted device list.     | Tap **Approve** or **Deny**.                    |
| **New device login**        | Your account was accessed from an unrecognized device.                    | No action is required.                          |
| **New location login**      | Your account was accessed from an unrecognized location.                  | No action is required.                          |
| **Account shared with you** | Another user has shared an account with you.                              | No action is required. Tap to open the account. |
| **OTP received**            | A one-time password was delivered for an account action.                  | View the code in the notification.              |

### Expiration deadlines for actionable notifications

Identity confirmation and trusted device requests have a limited response window. After the window closes, the request expires and you can no longer approve or deny it.

The following response windows apply:

* **Identity confirmation requests:** Three minutes from the moment the request was created.
* **Trusted device requests:** Five minutes from the moment the request was created.

When a request expires, the **Approve** and **Deny** buttons are no longer active in the Notification Center. The notification remains visible so you can see that the request occurred. To restart an expired flow, return to the action that originally triggered it.

## Respond to an identity confirmation request

When Cerby cannot automatically complete an action (for example, a login requiring multi-factor authentication (MFA)), it sends an identity confirmation request to your Notification Center and, if enabled, a push notification.

To respond to an identity confirmation request, complete the following steps:

1. Open the Notification Center.
2. Locate the identity confirmation request.
3. Tap the notification to expand it. The details of the action requiring confirmation are displayed, along with the time remaining to respond.
4. Tap **Approve** to allow the action, or **Deny** to reject it. The action is completed or canceled, and the notification is marked as handled.

{% hint style="warning" %}
Tap **Deny** if you do not recognize the action or did not initiate it. Denying a request does not lock your account, but it signals a potential unauthorized attempt. Contact your workspace Admin if you receive unexpected confirmation requests.
{% endhint %}

## Respond to a trusted device request

When a new device attempts to join your workspace and your workspace requires existing-device approval, you receive a trusted device request in your Notification Center.

To respond to a trusted device request, complete the following steps:

1. Open the Notification Center.
2. Locate the trusted device request.
3. Tap the notification to expand it. The device name, platform, request time, and time remaining to respond are displayed.
4. Tap **Approve** if you recognize the device, or **Deny** if you do not. The device is added to or rejected from your trusted device list, and the notification is marked as handled.

## Mark notifications as read

Notifications are marked as read automatically when you tap them to view their details. To mark all notifications as read at once, complete the following steps:

1. Open the Notification Center.
2. Tap **Mark all as read** at the top of the screen. All notifications are marked as read and the unread badge is cleared.

Read status syncs across all your devices. If you mark a notification as read on your phone, it also appears as read on any other device where you are logged in to Cerby.

{% hint style="info" %}
On iOS, the Notification Center also marks notifications as read as you scroll past them while they are in view.
{% endhint %}

## Configure which notifications you receive

You can control which notification types appear in the Notification Center and which ones also send push notifications to your device.

To configure notification settings, complete the following steps:

1. Open the Cerby app.
2. Tap **Profile** at the bottom of the screen. The **Profile** screen is displayed.
3. Tap **Notification settings**. The **Notification settings** screen is displayed.
4. Activate the toggle for each notification type you want to receive, or deactivate it to stop receiving that type. The notification setting is saved.

The following notification types can be configured individually:

* **Identity verification requests**
* **New trusted device requests**
* **New device login alerts**
* **New location login alerts**
* **Account sharing notifications**
* **OTP code delivery**

{% hint style="info" %}
Some notification settings may be managed by your workspace Admin. If a toggle appears grayed out, your Admin has locked that setting for all workspace members.
{% endhint %}

{% hint style="info" %}
**Android only:** If a toggle shows a locked badge and tapping it opens your device's system settings instead of changing the preference, the permission is controlled by the Android OS rather than by Cerby. This can happen if you previously denied Cerby notification access at the OS level, or if your organization's mobile device management (MDM) policy controls app notification permissions. Update the permission in your device's system settings to unlock it.
{% endhint %}

## Related articles

* [Turn on notifications on the Cerby mobile app](/cerby-mobile-app/app-customization/turn-on-the-allow-notifications-feature.md)
* [Turn off mobile notifications](/cerby-mobile-app/app-customization/turn-off-mobile-notifications.md)
* [Remove a trusted device](/cerby-mobile-app/app-customization/remove-a-trusted-device.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.cerby.com/cerby-mobile-app/app-customization/use-the-notification-center.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.