Inbox

The Inbox is DayZero's unified notification feed, labelled Notifications in the sidebar: approvals, anomalies, bank and sync events, and firm asks in one triageable list. Pick your view, filter by topic and severity, then Resolve, Snooze, or follow each row's action link.

Key capabilities

• One feed across every business you belong to, with an All / This business / Firm switch (Firm needs an advisory firm; client portal users see only their own company)
• A status workflow with Open / Snoozed / Done tabs
• Topic filter chips (Anomaly, Billing, AP Approval, Bank Connection, Month-End, Ledger, Notes, Email Inbox, Reconciliation, Other) with live counts
• Severity chips (Info, Warning, Urgent); warning and urgent rows get a colored left border
• Pin important rows to the top of the Open tab
• Snooze with presets — 1 hour, 4 hours, Tomorrow 9am, 1 week — and the row reappears when the timer elapses
• Resolve or Dismiss (both move the item to Done), plus Mark all seen to clear the unread dots in bulk and Dismiss all anomalies for anomaly alerts
• In the Firm view, notifications are grouped by client, with collapsible groups and a per-client mark-seen button
• A deep-link action button that jumps straight to the related record (bill, invoice, transaction, report, etc.)
• Live alerts (low cash, stale bank connection, etc.) merged into the feed and tagged Live
• New items appear in the feed automatically, and the bell badge also refreshes every 30 seconds as a backstop
• Multi-channel delivery per topic: in-app always, Slack when a webhook is configured, email when the topic policy allows
• A bell badge with your unread count, and a sidebar badge with the unread count for the business you are viewing

How it works

When something happens — a bill enters an approval gate, an anomaly is detected, a bank sync finishes — DayZero decides who should be notified and which channels fire, then writes one row per recipient.

flowchart TD
  event["Event (bill gate, anomaly, sync, mention)"] --> policy{"Audience + channel policy by topic"}
  policy --> rows["Notification rows (user / business / firm)"]
  rows --> feed["Inbox feed"]
  rows -->|"Slack if enabled"| slack["Slack webhook"]
  rows -->|"email per policy"| email["Email"]
  feed --> act{"You act"}
  act -->|"open / mark seen"| seen["Seen"]
  act -->|"snooze"| snoozed["Snoozed (wakes later)"]
  act -->|"resolve / dismiss"| done["Done (terminal)"]

How to use it

1. Open Inbox from the sidebar — the bell badge shows how many Open items wait on you.
2. Use the All / This business / Firm switch in the header. All spans every business you belong to; This business narrows to the active business (the default when a business is selected); Firm shows your firm's client activity grouped by client.
3. Switch between the Open, Snoozed, and Done tabs to focus on what's actionable now versus deferred or finished.
4. Click severity chips (Info / Warning / Urgent) and topic chips to filter; topic chips show live counts and hide topics with zero items. Click Clear to reset. Use Load more at the bottom of the list for older items.
5. Click any row to open the detail panel on the right — a new row is auto-marked seen when you open it.
6. Use the row's action button (e.g. "Review bill") to jump to the underlying record.
7. From the detail header, Pin, Snooze (pick a preset), Resolve, or Dismiss the item. Dismissing an anomaly alert asks you to confirm, because it also clears the underlying anomalies.
8. In the Open tab, click Mark all seen to clear unread dots in one action.

Pro tips

• Stay in All for your personal triage; use This business to focus on one client, and Firm for a sweep across clients.
• Snooze instead of dismiss for things you can't action yet — a dismissed row is terminal, but a snoozed row resurfaces in the Open tab when its timer elapses.
• Filter to Urgent severity first thing each morning. Depending on the topic, urgent and high-severity rows also reach Slack and email.
• Pin the one or two items you're actively working so they stay at the top of Open even as new rows arrive.
• "Live" rows are computed from current data, not stored. Dismissing one hides it for you; it can reappear if the underlying condition (e.g. low cash) recurs.
• Tune per-topic noise in notification preferences rather than dismissing repeatedly — you can mute routine sync pings while keeping urgent reconnect alerts.

In-depth guide

Scopes and who gets notified

Every notification is addressed to a single user, a whole business, or an entire firm. The scope switch picks which slice you see:

• All — everything addressed to you across all your businesses.
• This business — filtered to one business.
• Firm — your firm's client activity, grouped by client with the firm-wide items last (needs an advisory firm).

Who receives a row depends on the topic: billing events go to the business owner (and firm owners); AP approval requests go to the approver for that tier and the assigned advisor; operational alerts (anomalies, bank connection health, month-end, reconciliation) go to the owner plus firm staff; note mentions go to the people mentioned.

Status lifecycle

Mark all seen only affects new rows currently in the list; it doesn't resolve or dismiss anything. Terminal rows won't transition again — prefer Snooze when you might need the item back.

Topics and severity

Topic chips answer "what domain is this about?" Severity drives visual urgency: Info is routine, Warning gets an amber border, Urgent gets a red border. Some topics (billing, anomalies, AP approvals, connection problems) email you only for higher severities; others never email by default. Items from other topics, such as sync-complete pings, still appear in the feed.

Channels and live rows

In-app delivery is always on; Slack and email depend on your firm's integration and the topic policy. If Slack or email fails, the in-app row is still written — the Inbox is the source of truth.

Some signals — low cash, a stale Plaid connection — are computed on every read rather than stored. They appear tagged Live and can return if the condition recurs. Live rows can't be pinned, snoozed or marked seen; dismissing one hides it for your account only.