What the notifications feed shows

The notifications page is a read-only record of events already persisted for your organization. It answers one question and no others: what has been recorded here, most recent first.

What the page does

It reads rows belonging to your organization and renders them in order. That is the whole operation. Opening the page writes nothing, marks nothing and requests nothing from a provider, so the feed you see is the same feed anyone else in your organization sees at that moment.

Rows shown

Newest 100

older events are not paged to, they are simply not listed

Scope

One organization

filtered on your organization before anything is rendered

Order

Newest first

by the time the event was recorded

Writes made by this page

None

viewing a feed does not change it

Stored on a row, shown on the page

A notification row carries more than the page displays. Knowing which columns go unread explains most of what the feature cannot do.

What a notification row holds, and what the page renders from it

Column	What it holds	Rendered
title	The summary line for the event	Yes
body	The detail beneath the title	Yes
createdAt	When the event was recorded	Yes, in the reader's local time
category	Which kind of event this is	No
href	A place in the product the event refers to	No
readAt	When the row was marked as read	No
userId	An optional person the event concerns	No

Three consequences follow directly. Nothing marks a row read, so there is no unread state and the workspace navigation carries no badge; the list looks identical before and after you read it. The stored link is not rendered, so a row tells you what happened but you navigate to it yourself. The category is not rendered either, so the feed cannot be filtered or grouped by kind.

What this feed will not tell you

Nor is it a record of your own activity. Creating an action, completing one, or running an export raises no entry here. The feed reflects only events that some part of the system chose to persist as a notification, and it will not reconstruct one after the fact.

Reading an empty feed

Emptiness is an ordinary state, and the page says so plainly rather than filling the space with welcome messages, tips or sample events. That restraint is the point of the surface. A feed that manufactures its own entries cannot be trusted to be complete on the day it matters, and a reader who has learned to skim past filler will skim past the one row that was real.

If you need to know whether the underlying data is current, the reliable checks are elsewhere: see how daily ingestion runs for the sweep and its cadence, and reading the dashboard for the two freshness dates and the source health panel. For how the organization filter on this page is enforced, see how organizations work.