What it does
Administrators can watch every notification delivery for their scope, retry failures, review engagement analytics, and manage the email providers that carry the messages. Delivery and Analytics are their own tabs in the notifications admin area; email providers live under Settings → Providers.
Who it's for
Organization, institution, and program administrators with permission to manage notifications.
How it works
Delivery tracking and analytics work at all three scopes. Email providers are managed at organization or institution scope only, and program notifications inherit those providers.
Delivery tracking. The Delivery tab lists individual deliveries for your scope, fifty per page. Counters show Pending, Processing, Sent, and Failed. Filter by channel or status. Select View Details on any row. Select Retry on a single failed delivery, or Retry Failed to retry them all at once. A channel readiness summary shows whether each channel is set up and active.
Analytics. The Analytics tab summarizes engagement over Last 7 Days, Last 30 Days, or Last 90 Days. It shows Total Sent, Delivered, a Read Rate, and a Click Rate. Below that sit Channel Distribution, Top Categories, and a Failed Deliveries count split into bounced and failed. Select Refresh to pull the latest numbers.
Email providers. Settings → Providers manages the email services that send your notification email. Select Add Provider to set up a new one. Each provider shows its from address and reply-to, hourly and daily send limits, and today's send count. Select Test to send a test email, or Set as Primary to make a provider active. Non-primary active providers stand by, and a routing summary shows the current primary at a glance.
Before you start
You need the manage-notifications permission for delivery tracking and analytics. Email providers need that same permission, at organization or institution scope.
There must be deliveries already sent for these tabs to show anything. Nothing appears before the first notification goes out.
Do this
Open
/notifications/admin?tab=delivery→ the Delivery Tracking page lists deliveries with Pending, Processing, Sent, and Failed counters.Filter by the Channel or Status dropdown → the list narrows to matching deliveries.
Select View Details on any row → the Delivery Details dialog opens with the delivery timeline and any error.
On a failed row, select the Retry button → a toast confirms the delivery was retried.
To retry everything at once, select Retry Failed in the toolbar → a toast reports how many deliveries were queued for retry.
You're done when
✓ A retry toast confirms how many deliveries were queued.
✓ Retried deliveries move out of the Failed counter into Pending or Sent.
✓ Filtering by status Failed shows only deliveries that still need attention.
Boundaries and limits
All three areas require the manage-notifications permission. A restricted message appears without it. Providers are a Settings section, not its own page tab.
Email providers can't be configured at program scope. The section explains that programs inherit organization or institution providers.
Provider credentials (API keys) are write-only. They're stored encrypted and never shown back in the interface.
Retry applies to failed deliveries. It doesn't resend messages that were already delivered successfully.
Analytics date ranges are fixed: 7, 30, or 90 days. Custom ranges aren't offered.
You can't remove the primary provider directly. Promote another provider to primary first.
Delivery rows reflect what the platform attempted and recorded. Whether a recipient's mailbox ultimately accepted a message depends on their mail service.
Common questions
Q: A batch of emails failed. What do I do? A: Open the Delivery tab and filter by failed status. Open a failure's detail to see the reason. Fix the cause — often a provider setting — then select Retry Failed.
Q: What is the difference between "Total Sent" and the read rate in analytics? A: Total Sent and Delivered are counts — messages dispatched, and those confirmed handed off. Read Rate and Click Rate are percentages — how many recipients opened the notification, and how many then followed a link inside it.
Q: Why would I add a second email provider? A: Capacity and resilience. Send limits are tracked per provider, and non-primary active providers stand by while the primary handles routing.
Q: Can I verify a provider works before relying on it? A: Yes — use the test action on the provider to send a test email.
Related articles