← Help & Docs

Notification Hub

One place every TATER notification lands - an in-app feed and a delivery log, not just an email - with per-item snooze and per-event routing. Last updated 2026-07-22

What it is

The Notification Hub is the shared layer underneath every notification TATER sends. Historically a notification was just an email; the Hub adds two durable surfaces on top of that email, without changing the emails themselves:

Essentially every notification populates the Hub. The central template-based notification path feeds it, and so do the purpose-built notifiers behind specific flows - approvals, the review/attestation engine, RFIs, task updates, license rentals, and travel exemptions. (The one deliberate exception is the auto-reply that goes to an external email-intake requester, which is not an in-app event.)

The My Notifications feed

Each person's feed lives on the dedicated Notifications page in My TATER (my.tatersecurity.com). It is cross-organization - if you work across several organizations or help desks, every event addressed to you appears in one list. Items show the event, a title, an optional deep link to the thing that happened, and whether you have read them; an unread count is surfaced on the nav badge. Each item can be marked read (or "Mark all read") and snoozed (below). Feed items carry a 180-day retention before they auto-expire.

Snoozing a notification

A notification you can't act on yet doesn't have to keep staring at you. On the Notifications page, each item has a Snooze control with quick options - 1 hour, 1 day, 1 week, 30 days. Snoozing removes the item from your active feed and it reappears automatically when the snooze elapses (there's no background job - snoozed items are simply hidden until their time passes). A "Show snoozed" toggle reveals what you've deferred, and any snoozed item can be brought back early with Un-snooze. Snooze is per-person: snoozing your copy never affects anyone else's feed.

Snoozing meeting (and other) reminders

Recurring reminders - most commonly the compliance / governance meeting "due soon / overdue" reminders - now land in your in-app feed in addition to email, so you can snooze the in-app copy like anything else. For the meeting reminders specifically there is also a stronger, source-level snooze: open the meeting in TATER Security → Governance Meetings and use Snooze reminders (1 week / 1 month / 3 months, or Resume now). That pauses the daily email reminders for that meeting for everyone on its list until the snooze elapses or the meeting is logged - useful when a meeting is already scheduled and the nagging is just noise. Snoozed meetings show a 💤 marker in the list.

The delivery log

The delivery log (Manage → Audit & Telemetry; Auditor role) records each send: the event type, the channel (email / in-app / Teams), the recipient, the status, and the subject. Entries are retained 90 days. Use it to confirm a notification actually went out and to whom - the answer to "did the approver get pinged?" without guessing.

Per-organization channels

Beyond email and the in-app feed, an organization can enable additional notification channels (Admin role), from the Delivery Channels card on TATER Security → Settings → Notifications. Email and the in-app feed are on by default; the optional channel is a Microsoft Teams incoming webhook: paste the webhook URL for a Teams channel and events are posted there as well, with a "post which events" selector (All events or High-severity only). The webhook URL is validated to prevent it pointing at internal infrastructure, and it is redacted when the channel config is read back. Channels are additive - turning on Teams does not turn off email or the in-app feed.

Routing & per-event overrides (Settings → Notifications)

An Org Admin can decide, per event type, whether an event notifies at all, who it goes to, on which channel, and at what minimum severity. This lives in TATER Security → Settings → Notifications:

The same page also hosts the Delivery Channels card (above) and a Delivery Log card showing the most recent sends across every channel - when, event, channel, recipient, and status (sent, failed, suppressed, skipped).

How an event flows

When TATER raises a notification it goes out by email as before, and the same event is, fire-and-forget, pushed to each recipient's in-app feed and recorded in the delivery log (and posted to any enabled channel). A failure on the in-app / log side never blocks or delays the email - the email path is unchanged and authoritative.

MCP tool reference

ToolPurpose
list_my_notificationsList your in-app notification feed - every TATER event addressed to you, newest first, across organizations. Each item shows its id; optionally only unread, or include snoozed items. Viewer+.
snooze_notificationSnooze (or un-snooze) one or more of your notifications by id - pass minutes (60=1h, 1440=1 day, 10080=1 week) or an explicit until; minutes:0 clears it. Viewer+.

Related