Notifications FAQ

General

What kinds of events appear in the notifications panel?

Notifications are grouped by subject into these types: Mention (someone tagged you in a comment on an asset's Timeline), Ownership (a check, computed field, or container you own was updated), Anomaly (a new anomaly was identified in data relevant to you), Assignment (an anomaly you're assigned to was updated), Operation (a profile, scan, or other operation finished), Flow (a flow's in-app notification action reported its run), and System (general account or platform messages). Every notification is addressed to you: mentions, ownership updates, and assignments reach only the people involved, and flow-delivered notifications reach Admins and the members of the teams assigned to the affected datastore.

Are these the same as Slack or Email notifications from flows?

No. The bell icon shows in-app notifications for you, the signed-in user. To send messages to Slack, Email, Microsoft Teams, or PagerDuty as part of a flow, configure a notification action inside the flow itself. See the Flow Notifications documentation.

Why didn't I get a notification for something I did myself?

By design, your own actions are silent. Mentioning yourself in a comment, editing an asset you own, and updating an anomaly you are assigned to notify the other people involved, never you. Notifications exist to tell you about other people's activity.

Why did the same anomaly reach me as an Anomaly notification and a teammate as an Assignment?

The platform classifies by origin. When a flow delivers the anomaly through its in-app notification action, it arrives as an Anomaly notification, addressed to Admins and to members of the teams assigned to the datastore. When someone updates an anomaly directly, its assignees get an Assignment notification instead.

Can I disable specific notification types?

Not today. There is no per-type opt-out in the panel; who receives each notification is fixed by its type.

Can I read or manage notifications from a script?

Yes. The Notifications API lists your notifications with filters for read status, flow trigger type, and tags, and marks them read or unread, one at a time or in bulk, using a Personal API Token.

Delivery & Timing

How quickly do new notifications appear?

The platform checks for new notifications every 10 seconds while you're signed in, so there's no need to reload the page.

What happens when a notification arrives while I'm working?

It depends on whether the panel is open. With the panel closed, the bell badge updates and a toast appears in the bottom-right corner for about five seconds: a single notification shows its type, title, and a short preview with a View button that jumps straight to it, while several at once collapse into one toast whose View button opens the panel. With the panel already open, there is no toast. A <N> new notifications button appears at the top of the list instead, and clicking it pulls the new entries in.

Is the unread count on the bell capped, like 99+?

No. The badge shows the exact number of unread notifications on your account, however large it gets, and it counts everything, not just the notifications already loaded into the panel.

Do I get notifications when I'm signed out?

The bell only updates while you're signed in. When you return to the platform, the panel surfaces every unread notification that arrived during your absence, sorted from newest to oldest.

Are notifications synced across browsers and devices?

Yes. Notifications are stored on the server and personalized to your account, so the same list appears on every browser and device you sign in to.

Reading & Retention

Does clicking a notification mark it as read?

Yes. Clicking opens what the notification refers to and marks it as read in the same motion, and the bell's count updates immediately. Opening the page never waits for the read acknowledgement.

The exception is a link inside the message itself. That opens in a new tab and leaves the notification unread, so you can follow a link an author put in a flow's message and still come back to the notification later.

What's the difference between "Mark as read" and deleting?

There is no delete action. Mark as read (via the per-item action, bulk selection, or Mark all read ) removes the notification from the unread list, but the record is still stored on the server.

I marked something as read by mistake. Can I undo it?

Yes. Find it on the Read or All tab and use its Mark as unread action; the notification returns to the unread list and the bell counts it again. To reverse several at once, tick their checkboxes on the Read tab and use the Mark as unread button selection mode shows there. See Mark a Notification as Unread.

Can I see notifications I've already marked as read?

Yes. The panel has All, Unread, and Read tabs. Switch to Read to see only the notifications you've already marked as read, or All to see read and unread together. You can also retrieve them programmatically with the API by setting status=read (or status=all).

How long are notifications kept?

Notifications are retained server-side as part of your account history. There is no automatic expiration today.

A notification I remember seeing is gone. Why?

A notification does not outlive its subject. When the asset it points to is deleted (the anomaly, the flow, the container, or the comment), the notifications that reference it are removed with it. Apart from that, nothing expires: read notifications stay on the Read and All tabs indefinitely.

Permissions

Who can see notifications?

Every authenticated user (Member, Manager, or Admin) has a personal notifications panel. There is no team-permission gating; notifications are scoped to the recipient, not to a datastore or team.