Notifications
Operational view of in-app, push, and email notifications, user preferences, device tokens, and delivery attempts.
Queued
0notifications waiting
Failed
0delivery failures
Push Tokens
0active devices
Marketing Opt-In
0users opted in
Attention Queue
Notifications and delivery state needing operator review.
Consent Coverage
User preferences that gate email, push, and marketing delivery.
Push
0
of 0 saved preferences
0
of 0 saved preferences
Marketing
0
of 0 saved preferences
By Status
Notification lifecycle.
No notification data loaded yet.
By Channel
In-app, push, and email split.
No notification data loaded yet.
By Category
Product or operational reason.
No notification data loaded yet.
Attempts by Provider
Delivery provider split.
No notification data loaded yet.
Admin login required
Admin login required before reading operational data.
Admin login required
Admin login required before reading operational data.
Admin login required
Admin login required before reading operational data.
Admin login required
Admin login required before reading operational data.
Queue Notification
Create a notification record for a specific user.
Operator Boundary
Manual notifications are queued only; external delivery is still provider-dependent.
Use in-app notifications for safe operational messages that should appear in the product.
Push and email channels can be queued, but they will need provider fan-out before users receive them outside the app.
Do not use the marketing category until campaign consent and unsubscribe handling are fully wired.
Notifications
0 of 0 notifications shown. Provider fan-out will be handled by Edge Functions later.
Notifications
0 of 0 notifications shown. Provider fan-out will be handled by Edge Functions later.
Admin login required
Admin login required before reading operational data.
Push Tokens
Registered devices for future push notification fan-out.
Push Tokens
Registered devices for future push notification fan-out.
Admin login required
Admin login required before reading operational data.
Preferences
Consent and delivery preferences by user.
Preferences
Consent and delivery preferences by user.
Admin login required
Admin login required before reading operational data.
Delivery Attempts
Provider-level delivery attempts for push/email sends.
Delivery Attempts
Provider-level delivery attempts for push/email sends.
Admin login required
Admin login required before reading operational data.
Implementation Boundary
The notification store exists; provider fan-out is next.
In-app notification records can now be stored and marked read.
Push device tokens can be registered per user and platform.
Email consent is tracked, but email delivery needs an Edge Function/provider integration.
Marketing notifications must respect explicit opt-in before any campaign tooling is added.