Skip to main content
All manual pages

Notifications

The Notifications inbox is the unified feed of alert triggers, scanner hits, simulator fills, economic releases, and options-flow detections — filterable by kind, unread-tracked, server-side retained until you clear them.

The Notifications page is the inbox side of every push surface in Tapeboard. Set the alerts in /settings/alerts, configure the scanner and the sim fills in their respective pages, and every triggered event lands here — newest first, one row per event, with a kind chip, a title, a body, a relative timestamp, and a click-through URL when the source has one.

The notifications inbox — alert hits, system messages, and account activity
The notifications inbox — alert hits, system messages, and account activity

What it is

A reverse-chronological feed of every event the product pushes to you. Five kinds land here: alert (price/percent/volume/VIX triggers from /settings/alerts), scanner (scanner-hit pushes), sim_fill (simulator order fills), economic (economic-calendar releases), and options_flow (unusual-options-activity detections). The inbox is where you read them; the rules that create them live in each feature's own settings.

Read-state is saved to your account — a row is unread until you click it or hit Mark all read. The unread count powers the badge in the sidebar.

When to use it

After every alert that fires when you weren't looking at the chart. End of session — sweep the inbox, click into the ones that matter, clear the noise. Pre-market — scan economic-release notifications from overnight to see what's on the tape before the open.

Open it

  • Path: /notifications
  • Shortcut: none
  • Tier-gate: free — the inbox itself is universal; the gating happens at the source (e.g. sound alerts are Pro+, but the resulting notification still lands in every tier's inbox)

How to use it

  1. Open /notifications. The page loads the 200 newest entries. The header shows a Bell icon, the page title, an N UNREAD chip if you have unread rows, and two action buttons: Mark all read (only when there are unread) and Clear (only when there are rows at all).
  2. Filter by kind with the chip row — All, Alert, Scanner, Fill, Economic, Options. The filter narrows the list you're looking at.
  3. Click any row to open. If the row has a click-through destination (most do — alerts deep-link to /charts?symbol=XYZ, sim fills to /simulator, options flow to /options-flow), the click navigates there. Unread rows are marked read at the same time.
  4. Mark all read marks every unread row read. The button vanishes when the unread count hits zero.
  5. The trash icon on each row deletes that single notification. The row vanishes from the inbox; the source rule (e.g. the underlying alert) is untouched.
  6. Clear (top-right) removes every row in your inbox after a confirm prompt. This is destructive and not reversible; the underlying alert rules are untouched, so they'll re-fire and re-populate the inbox.

Fields

FieldNotes
idServer-generated row id
kindOne of alert, scanner, sim_fill, economic, options_flow
titleShort headline — e.g. AAPL crossed $200
bodyOne- or two-line context — e.g. Last 200.15, threshold 200.00, repeating: yes
urlClick-through destination. Optional — some rows are read-only
symbolTicker if applicable; null for market-wide rows
read_atISO timestamp or null. Drives the unread chip + the row background color
created_atISO timestamp; the sort key

Kind chip colors follow the brutalist palette: alert amber, scanner green, sim_fill indigo, economic pink, options_flow cyan.

Limits

  • Page loads up to 200 of the newest rows; older history loads as you scroll back
  • Retention: indefinite. No automatic expiration; rows persist until you delete them per-row or use Clear
  • Read-state is saved to your account — read on one device = read on all devices
  • economic and options_flow are newer kinds; older notifications are all alert / scanner / sim_fill
  • The unread badge in the sidebar refreshes on a short interval, so it can lag the inbox by up to ~30s
  • Setup surfaces: alerts live in /settings/alerts, scanner triggers in /scanner, simulator fills in /simulator. This page is consumption-only; you can't create a rule from here
  • Browser push notifications (the OS-level tray pop) are a separate channel managed in Settings under Push Notifications. The inbox row is always written regardless of whether the browser push succeeded
  • Quiet-hours: configured in Settings, notifications inside the quiet-hours window still land in the inbox but skip the device push

Troubleshooting

I deleted a notification but it came back. The notification is consumption-only — deleting it doesn't disarm the underlying rule. If it was an alert with repeating: true and the condition re-crossed, a fresh notification is written. To stop the rule from re-firing, delete the alert in /settings/alerts, not the notification.

Clear wiped my inbox and now I can't find an alert I needed. There's no undo. The notification is permanently deleted. The underlying alert rule still exists and will fire again the next time the condition triggers — but the historical row is gone.

Notification body says "Last 200.15, threshold 200.00" but the chart shows the price is back below. The alert fires on the cross, not on the holding condition. Last price moved through the threshold at some point in the streaming window; by the time you opened the inbox, price had reverted. Set the alert to repeating: false if you only want the first cross.

Sidebar shows "3 UNREAD" but the inbox is empty. Cache lag. The unread count poll can lag the inbox state by up to the poll interval. Reload the page; both should reconcile.

I never get push notifications even though the inbox fills. Browser permission for push is separate from in-app notifications. Open Settings → Push Notifications and enable; the browser will prompt for OS-level permission. Also check /settings Quiet Hours — pushes inside the window are intentionally skipped (inbox row still lands).

Scanner / options_flow rows say "kind not recognized" or the icon is missing. You're on an older build — hard-refresh the page to pick up the latest notification kinds.