Notifications — Tenant Admin
Overview
The Notifications area includes a tenant-scoped received inbox and, for an authorized Tenant Admin, tenant-originated mobile notification sending plus a separate Sent batch/history surface. Platform and system producers may also target tenant users.
Types of Notifications
| Type | Source | Examples |
|---|---|---|
| Platform Broadcast | Platform Admin | Maintenance windows, platform policy updates |
| Targeted Platform | Platform Admin | Billing reminders, subscription renewal alerts |
| System | Automated | Subscription expiry warning, storage approaching limit, payment confirmation |
Viewing Notifications
- Open Notifications from the dashboard navigation.
- The notification list shows all received notifications with their title, date, and read/unread status.
- Unread notifications are highlighted.
Marking as Read
- Click a notification to open it and mark it as read automatically.
- Click Mark All as Read to clear all unread notifications at once.
Notification Bell
The dashboard navigation includes a bell icon that shows the count of unread notifications. Clicking the bell opens the notification list directly.
Sending Tenant Notifications
When the current account is a Tenant Admin and has Tenant.ManageNotifications (or authorized platform-selected-tenant equivalent), open the tenant mobile notification create route. Enter the title and body, then choose all tenant users or specific user IDs. Submission is antiforgery-protected and checks tenant notification batch, recipient, and mobile-push entitlements before queuing eligible recipients.
Sent History
Open Sent to list notification batches created by the current tenant. Open a batch to inspect source intent, channels, recipient counts, batch status, and paged per-recipient delivery state. The history query is tenant-scoped; another tenant's batch returns not found.
Important Notes
- Authorized Tenant Admins can send tenant mobile notifications from the dedicated create route; ordinary tenant users and accounts without the required permission cannot.
- Notifications are read-only — they cannot be replied to from this section. For billing-related notifications, use the Billing Requests section to respond.
- No fixed retention duration is established by the tenant inbox controller; retention follows persisted notification/batch operational policy.
- The current tenant create route is specifically for mobile notification delivery. Do not infer email delivery or user-configurable email preferences from an in-app/mobile row.