The Notifications tab: your alert inbox

What the Notifications tab is

Every alert Verinode has ever sent you lands in one place: a decision step coming due, a teammate replying to a survey, an HQ broadcast, a scheduled email queued for delivery. The small bell in the app header only shows you what is new. The Notifications tab is the full record: every alert, in every state, going back as far as your account has history. It is where you audit what Verinode has told you and clean up what you have already acted on.

Verinode does not decide what matters to your business. It flags things worth your attention, based on the data flowing in from your jobs, documents, and settings, and leaves the read, the dismiss, and the follow-through to you.

Where to find it

Open Vault from the My Data section of the sidebar, at iq.verinode.ai/data. Vault opens on a home screen of tile rows; one of them is a Notifications tile. Tap it to open the full-screen Vault view, which holds four tabs side by side: Uploads, Tracking, Lists, and Notifications. Notifications is the last of the four.

The Notifications tile on the Vault home screen is a shortcut into this same tab. Its number reads your unread count when you have unread alerts, or your total notification count when your inbox is fully read. Its subtitle reads "Unread" (with a scheduled count appended if any are queued), "All Caught Up" once everything is read, or "Alerts Land Here" if nothing has arrived yet. Tapping the tile with unread alerts jumps straight into the tab pre-filtered to Unread.

The table

Once open, notifications render as rows in a table, newest first. Each row has six columns:

• Notification. The alert's title, and if Verinode attached a link to the thing the alert is about (a decision, a job, a document), the title is a clickable link in copper. Below the title, if the alert has a longer body, up to two lines of that body text preview underneath.
• Category. A rounded pill naming what kind of alert this is, for example Decision Reminder, Survey, Ingestion, or Hq Broadcast. If no category was set at creation, the pill reads General.
• State. A colored pill showing where the notification sits in its lifecycle. See the four states below.
• Channel. How the alert was (or will be) delivered: In App, Email, or In-app + Email when both.
• When. For most rows, how long ago the alert was created ("just now," "12m ago," "3h ago," "2d ago," or a month/day date once it is more than a week old). For rows still in the Scheduled state, this column instead counts down to delivery ("in 45m," "in 6h," "in 3d," or "due now" once the scheduled time has passed).
• Actions. Up to three icon buttons on the right: a checkmark to mark the row read, an arrow to open its linked page, and an X to dismiss it. Which ones appear depends on the row's state, covered below.

Rows that are Read or Dismissed render at reduced opacity, so your eye is drawn to what still needs a decision.

The four states

Every row's state is derived live from four flags on the notification, not a status you set directly. In order of precedence:

1. Dismissed. You explicitly cleared this row from the dropdown or this tab. Once a row is dismissed it stays dismissed, shown as a muted gray pill labeled Dismissed.
2. Scheduled. The alert has a future delivery time and has not gone out yet. Shown as an amber-outlined pill labeled Scheduled. These are typically emails queued by the delivery cron, holding until their scheduled_for time arrives; they are not yet actionable because they have not reached you yet.
3. Unread. You have not opened or acknowledged this alert. Shown as a copper pill labeled Unread, with a small solid copper dot.
4. Read. Everything else: the alert has fired, is not dismissed, and you have already marked it (or opened it, or it arrived already read). Shown as a green pill labeled Read.

A row can only be in one state at a time, and Dismissed always wins: once you dismiss something, it will not flip back to Unread or Read even if it was never opened.

The filter bar

Above the table sits a search box and two dropdowns:

• Search. Placeholder text reads "Search notifications…". It matches against both the title and the body text of each row, case-insensitively.
• State filter. Defaults to "All states (N)" where N is your total row count. The other options are "Unread (N)", "Read" (no count shown), "Scheduled (N)", and "Dismissed (N)", each count reflecting the current full inbox, not the filtered view.
• Category filter. Defaults to "All categories." The remaining options are every category your notifications actually use, alphabetically sorted, each rendered in humanized Title Case (so "decision_step" reads as "Decision Step").

Filters and search combine: narrowing by state and category and typing a search term all apply together, and clearing any one of them widens the result set back out.

Taking action on a row

Three actions live in the rightmost column, and which ones show up depends on the row:

• Mark as read (checkmark icon) appears only on Unread rows. Clicking it flips the row to Read immediately in the table (an optimistic update), then confirms the change in the background. It does not touch the underlying alert, it just tells Verinode you have seen it.
• Open (arrow icon) appears on any row that has a link attached, regardless of state. Clicking it navigates you to whatever the alert is about, a decision, a job, a document.
• Dismiss (X icon) appears on any row that is not already dismissed. Clicking it sets the row to Dismissed right away in the table, then confirms the change in the background. Dismissing does not require you to have read the alert first, you can dismiss something Unread directly.

There is no bulk "select all and dismiss" control in this tab. Each row's actions apply one row at a time.

Empty states

No notifications at all. If your account has never received an alert, the tab shows: "Notifications appear as Verinode flags things worth your attention," with three examples underneath: "Decision reminders fire when a step is due," "Survey responses ping you when a teammate replies," and "Scheduled emails queue here before they go out." This is normal for a brand-new account, alerts start arriving as your data flows in and Verinode has enough to flag.

Filters return nothing. If you have notifications but your current search, state filter, or category filter excludes all of them, the tab shows "No notifications match these filters," with the suggestion "Try clearing the search or switching the state filter."

Best-practice example

Say you open Vault and the Notifications tile reads "4" with the subtitle "Unread · 2 Scheduled." Tap the tile: it opens straight into the Notifications tab, pre-filtered to Unread. You see a Decision Reminder about a step due on a job, a Survey alert that a teammate answered a rating request, and two more. Open the decision reminder (arrow icon) to act on it, then come back and mark it read. The two Scheduled rows are emails still queued, not yet worth your attention, switch the State filter to Scheduled to confirm what is coming and when. Once you have worked through the unread batch, the Notifications tile on the Vault home screen reads "All Caught Up."

Related reading

• The decision workspace: what happens when you open a decision reminder's linked page.
• The Feed: where new signals and recommendations surface before they generate a notification.
• Connecting your data: how ingestion and settings changes feed the alerts that show up here.