Manage notifications

Notifications draw your attention to changes, mentions and work requiring review. Your delivery preferences belong to you. Organization events and account events have separate settings.

Read and acknowledge notifications

1. Click the Notifications bell.
2. Read the unread list. The badge shows 99+ when the count exceeds 99.
3. Click a notification to mark it as read and open its target when available.
4. Use Mark all as read to clear the unread list when you have reviewed it.

The bell gathers unread notifications across your account's organizations. Opening a target in another organization can switch organizations and reload the page. Check the organization after navigation.

Marking notifications as read does not accept suggestions, attest assets or complete the underlying work. Some grouped messages are acknowledged together for the same resource.

The bell is an unread list, not a searchable archive of every notification you previously read. If you need to find the underlying information later, use the asset's history, suggestions or global search.

Adjust your delivery preferences

1. Open Organization > My preferences > Notifications for the organization concerned.
2. Find the event you want to configure.
3. Enable or disable the available In-app and Email buttons.
4. Check the saved button state before leaving. Changes are sent immediately; there is no global Save button.

Viewers can access their own preferences. This page does not disable notifications for colleagues. Without a custom preference, the default is enabled.

Mention and ownership-assignment emails also offer an unsubscribe link. Open it and confirm to stop that email type for that organization. In-app delivery stays separate. Re-enable the email in these preferences when needed.

Channels differ by event. Ownership assignment and mentions offer in-app and email options. Other rows concern asset changes, suggestions, resolutions, scenario events or Re-attestation requests. Use the buttons actually offered for the event you need.

The rows about the assets you own (assignment, owner departures, changes, suggestions and re-attestation requests), the owners' weekly digest and reminders appear only when repository quality is active. Without it, the asset activity group is named My suggestions and mentions.

In the organization preferences, Weekly administrator report has its own Email button for Administrators and the Owner. Turn that button off to stop this report. It is separate from the quality weekly digest and its scheduling; disabling one does not disable the other.

Set the organization's email time

Administrators and the Owner choose, at the top of Organization > My preferences > Notifications, under Email schedule, the hour (7:00 by default) and time zone at which the organization's emails go out. Unlike the preferences below it, this setting applies to the whole organization. The daily suggestions digest uses it in every plan, the weekly administrator report every Monday, and the owners' weekly digest with repository quality. Each change saves immediately. Editors and Viewers do not see this section.

Set account notification preferences

1. Open your avatar or initials, then Account settings > Notifications.
2. Set the available channels for Support replies and Organization membership.
3. Check the resulting state; these choices are saved immediately.

These preferences belong to your account, independently of the organization currently open. The in-app channel for support replies stays enabled and cannot be turned off here. Its email channel can be adjusted separately.

Understand summaries and missing messages

The Daily suggestions digest announces new suggestions from the 24 hours before its scheduled send time that are still pending. In every plan, it includes the suggestions on the assets you own and can accept, and the creations naming you as an owner that you can create. With repository quality, it also includes creations naming you as an owner even when you cannot create them. It excludes suggestions you authored and does not repeat the entire backlog each day.

A summary is not an immediate email for every event. Quality summaries and reminders depend on the quality program being enabled. The administrator report is available to Administrators and the Owner.

For a comment mention, the recipient must still be an active member with access to the resource. A person already reading the discussion may not receive a redundant alert. Mentioning yourself does not send a notification to you.

Without repository quality, a suggestion sends no individual notification: it reaches the asset's owners through Suggestions on Home, and those who can accept it through the daily suggestions digest. With repository quality, value-change and archiving suggestions also notify owners who can read the asset, excluding the author. If an owner cannot resolve the request, the message can name authorized reviewers. For archiving, these are people with deletion permission. A suggestion on an asset without an owner reaches no one, in any plan: it waits on the asset. A rejection reason remains in the resolved suggestion when it is retained. For an individual refusal, it can also appear in the author’s in-app notification. This preserves the reason when a refused creation suggestion is discarded. Notifications for suggestions resolved together do not include individual reasons.

The Creation suggestions setting, offered with repository quality, concerns assets awaiting creation. Suggested owners who can read the asset are notified, excluding the author. No one else is notified, even when none of these owners can create it, and a creation suggestion without an owner notifies no one. An owner who cannot create it can see the names of authorized reviewers. There is no recipient-count cutoff.

Creation alerts are grouped by asset type and open its suggestions list. Correcting a suggestion notifies newly added owners. Suggestions made in a scenario do not send these creation alerts.

With repository quality, for bulk assignments, each new owner receives one grouped notification and email for the operation, according to their preferences and readable assets. Existing owners receive a grouped change notification where applicable. A new owner does not also receive a change notification for the same asset. Self-assignments do not notify the author. Suggestions resolved together similarly notify each eligible author once per outcome.

Changing preferences affects notification delivery; it does not recall emails already sent. Email reception also depends on the sending service and the recipient's mailbox.

Diagnose an unavailable target

A notification can outlive your access to its target. If it no longer opens, check organization membership, current permissions, the active data context and whether the resource still exists.

If the list itself fails to load, use Retry. Do not treat a loading error as proof that you have no outstanding work. The Home page provides another entry point to your current priorities.