Skip to content

§21 NOTIFICATIONS

OVERVIEW

The Notifications page is the inbox for every push surface in Tapeboard. Every triggered event lands here — newest first, one row per event. Set alert rules in /settings/alerts, configure the scanner in /scanner, and manage simulator fills in /simulator; this page is consumption-only.

NOTIFICATIONS_tapeboard

Path: /notifications Tier: Free — the inbox is universal; gating occurs at the source feature, not the inbox itself.

Note

Read-state syncs to your account. Mark a row read on one device and it is read on all devices. The unread badge in the sidebar refreshes on a short polling interval and may lag the inbox by up to ~30 seconds.


FEATURES

Notification Kinds

Five event kinds land in the inbox. Each is identified by a colored chip.

Kind Color Source
alert Amber Price, percent, volume, or VIX triggers from /settings/alerts
scanner Green Scanner-hit pushes from /scanner
sim_fill Indigo Simulator order fills from /simulator
economic Pink Economic-calendar releases
options_flow Cyan Unusual-options-activity detections

Row Fields

Field Notes
id Server-generated row identifier
kind One of the five kinds listed above
title Short headline — e.g. AAPL crossed $200
body One- or two-line context — e.g. Last 200.15, threshold 200.00, repeating: yes
url Click-through destination — optional; some rows are read-only
symbol Ticker if applicable; null for market-wide rows
read_at ISO timestamp or null — drives the unread chip and row background color
created_at ISO timestamp; the primary sort key

Click-Through Destinations

Kind Destination
alert /charts?symbol=XYZ
sim_fill /simulator
options_flow /options-flow
scanner /scanner
economic Read-only; no navigation

Limits and Retention

Property Detail
Page load Up to 200 newest rows; older history loads on scroll
Retention Indefinite — no automatic expiration
Deletion Per-row trash icon, or bulk Clear
History recovery None — Clear is destructive and irreversible

Note

economic and options_flow are newer kinds. Older account history will contain only alert, scanner, and sim_fill rows.


HOW TO USE

Reading the Inbox

  1. Open /notifications. The page loads the 200 newest entries.
  2. The header displays a Bell icon, the page title, an N UNREAD chip when unread rows exist, and two action buttons: Mark all read and Clear.
  3. Use the filter chip row to narrow by kind: All, Alert, Scanner, Fill, Economic, Options.
  4. Click any row to open it. If a click-through URL exists, the click navigates to the destination and marks the row read simultaneously.

Marking and Deleting

  • Mark all read — marks every unread row read at once. The button disappears when the unread count reaches zero.
  • Trash icon (per row) — deletes that single notification. The row is removed from the inbox; the underlying rule is untouched and will re-fire if its condition triggers again.
  • Clear — removes every row in the inbox after a confirmation prompt. Destructive and not reversible. Underlying alert rules are untouched and will re-populate the inbox on the next trigger.

Tip

Use the inbox as an end-of-session sweep. Filter by kind, click into the rows that matter, and use Clear to reset before the next session. Pre-market, check economic rows for overnight calendar releases before the open.

Setting Location
Alert rules /settings/alerts
Scanner triggers /scanner
Simulator fills /simulator
Browser / OS push notifications Settings › Push Notifications
Quiet hours Settings › Quiet Hours

Note

Browser push notifications are a separate channel from the inbox. An inbox row is always written regardless of whether the OS-level push succeeded. Notifications generated inside a configured quiet-hours window still land in the inbox but skip the device push.


KEYBOARD SHORTCUTS

Shortcut Action
None defined

Tip

There is no keyboard shortcut to open /notifications directly. Navigate to it via the sidebar bell icon or by typing the path into the address bar.


TROUBLESHOOTING

A deleted notification reappeared. Deleting a notification does not disarm the underlying rule. If the alert has repeating: true and the condition crosses again, a new row is written. To stop re-firing, delete the rule in /settings/alerts, not the notification.

Clear removed a notification I needed. There is no undo. The inbox row is permanently deleted. The underlying alert rule is intact and will fire again the next time the condition triggers, but the historical row cannot be recovered.

The body shows Last 200.15, threshold 200.00 but the chart price is now below the threshold. Alerts fire on the cross, not on a holding condition. The price moved through the threshold at the moment the notification was written; subsequent price movement does not alter or retract the notification.