Help Center/Admin Operations/How to use the Notification Command Center screen (Notifications)
Admin Operations•Last updated: 2026-10-20•3 min read

How to use the Notification Command Center screen (Notifications)

Send a broadcast to a segment of members and review past broadcasts. Each one really inserts an in-app notification per recipient.

Have questions or need step-by-step guidance on this topic?

Ask AI Copilot

Step-by-Step Procedure

1

Open the page

Sign in as an administrator and use Admin sidebar → Notifications → Notification Command Center, or go to /admin/notifications. The heading reads "Notification Command Center".

2

Know where the data comes from

This page reads i8_notification_broadcasts, i8_notifications and i8_notification_deliveries. KPI tiles for stored notifications, unread, broadcasts and delivery attempts or failures in 7 days. Columns: Broadcast, Title, Segment, Status, Recipients, In-app delivered, Emails queued, Email failures, Sent by, Sent.

3

Compose

Click New Record (Super Administrator only). Fill "Broadcast key", "Title", "Message", optional "Link (optional)", "Send to" (All active members, Members with a role, or Holders of a plan), "Role name or plan id" when needed, and tick "Also email" only if you want email too.

4

Understand the key

The broadcast key makes the send idempotent: submitting the same key again sends nothing twice and the banner says it already exists.

5

Read the banner

It states how many in-app notifications were delivered to how many recipients, how many members opted out of announcements, and how many emails were queued. A segment over 5000 members is refused, not truncated.

6

Use the shared controls

Use the shared controls: the search box ("Search records, hashes, DIDs...") filters rows by any text; "Status:" offers ALL, SENDING, COMPLETED, FAILED; "Page Size:" sets 10, 15, 25 or 50 rows; Refresh reloads; Export saves the rows currently loaded as a JSON file; New Record opens the form described above. The line "Data:" under the heading names the real source.

Expected Operational Outcome

The broadcast row appears with real counts and the members see the notification in their bell and Notifications page.

Troubleshooting & Failure Modes

Symptom: "Email was requested but the email engine is not configured"
Likely Cause: Email needs a configured provider in Communications.
Resolution: The in-app notifications were still delivered; configure the email engine and send a new broadcast with a new key if you want email.
Symptom: Error "Failed to load notifications/overview: HTTP 401" or "HTTP 403"
Likely Cause: The session is not signed in or does not hold an administrative role.
Resolution: Sign in again with an administrator account and click Refresh.

Was this guide helpful?

Help us refine our platform documentation