Notifications

The Notifications page is where you read user notifications and manage delivery preferences.

What this page is for

Use Notifications for two things:

• clearing pending notifications;
• deciding whether a category should arrive via in-app, email, or both.

Inbox and menu preview

Notifications appear in two places:

• the inbox page with the full list, filters, and bulk actions;
• a short preview in the menu that shows the most recent items with a quick “go to inbox” button.

On mobile, the inbox opens as a bottom sheet so it is comfortable to use one-handed.

Sound on new notifications

Behind a feature flag, you can enable a sound cue that plays when a new notification arrives while you are in the app. The toggle sits with your notification preferences; you can turn it off again at any time.

Central delivery from all products

The notifications page is cross-product. Notifications from the account dashboard, the RAG dashboard, and the marketing dashboard are all delivered centrally to the platform shell. You see them alongside notifications from LEO, VERA, and ZIA, and you manage them with the same preferences.

Support escalations (from Zammad) arrive in the same place, so you do not need to track them in a separate mailbox.

List view

The notification list supports:

• Unread or All filtering;
• category filtering;
• per-item mark-as-read actions;
• a bulk Mark all read action for the current visible selection.

Important:

• if you open an unread notification, the app marks it as read first;
• then it routes you to the linked destination, such as a project or the partner inbox.

Categories

The current categories are:

Category	Typical examples
second_opinion	partner inbox, conflict status, acceptance/decline
collaboration	project or collaboration actions
job_status	research or other background jobs
document_processing	files that finished or failed processing
account_access	account or access-related updates

Not every category is relevant to every user. For example:

• second_opinion is only relevant if you use that workflow;
• job_status is mainly relevant if you use background jobs.

Preferences by channel

At the bottom of the page you manage two channels per category:

• in_app
• email

What to keep in mind:

• changes remain a draft until you save them;
• the matrix applies per category;
• collaboration starts broader than most other categories;
• most categories default to in-app, with email enabled only where it is explicitly useful.

Practical examples

• If you never want to miss partner requests, keep second_opinion enabled in-app at minimum.
• If you want less noise, disable document_processing email but keep it in-app.
• Use collaboration email if you want updates outside the app as well.

Related pages

• Projects: many notifications open a project or partner flow.
• Chat: some background actions return through notifications.
• Settings: product switching changes which workflows are relevant to you, but channel preferences are managed here.