Skip to main content
This page is for administrators. Zion sends notifications by email and in-app for every event across the platform, from homework and attendance to meetings and billing. When an email address hard-bounces or a recipient marks a message as spam, Zion suppresses that address automatically so it is not emailed again until you clear it. The notification audit log gives you an org-wide view of every dispatched notification and its delivery outcome.

​
Email suppression

Suppression is automatic. Zion listens for hard-bounce and spam-complaint events from its email provider (Resend) and stops sending to that address without any action from you.
Two events trigger a suppression:
ReasonWhat happened
BounceThe email hard-bounced, for example the address does not exist or the mailbox rejected it permanently.
ComplaintThe recipient marked the message as spam.
ManualAn administrator suppressed the address directly.
Suppression can be org-scoped or global depending on how the provider reported the failure. While an address is suppressed, Zion continues to deliver the same notifications in-app, but no further emails go to that address.

​
Reviewing suppressed addresses

1

Open the suppression list

Go to /admin/email-suppressions.
2

Filter by reason

Filter the list by bounce, complaint, or manual to narrow down what you are looking at.
3

Confirm the address is fixable

Check with the parent, student, or staff member that the address is correct and can now receive mail, for example a typo has been corrected or a mailbox issue has been resolved.
4

Unsuppress

Click Unsuppress on the address and confirm in the dialog. Emailing to that address resumes immediately.
Unsuppressing an address that is still invalid causes it to bounce again and get re-suppressed. Confirm the address is corrected before unsuppressing it.

​
Notification audit log

The audit log at /admin/notification-audit is an org-wide table of every notification Zion has dispatched, regardless of which feature triggered it (homework, attendance, meetings, grading, billing, and others all write to the same log). Each row shows:
FieldWhat it tells you
ChannelIn-app, email, or WhatsApp (where active for that category).
Delivery statusQueued, sent, read, failed, or dead.
Email outcomeFor email sends: delivered, bounced, complaint, or no signal.

​
Reading delivery status

StatusMeaning
QueuedThe notification is waiting to be sent.
SentThe notification was dispatched to the channel.
ReadThe recipient has opened or read the notification.
FailedThe send attempt did not succeed.
DeadThe notification was stuck in processing for too long and was reclaimed as stale.
Filter the log by channel and by status to isolate a problem, for example filtering to email and failed to see which sends did not go through.

​
Using the audit log with suppressions

1

Spot a delivery problem

In the audit log, filter to channel Email and status Failed or Dead to find notifications that did not reach a recipient.
2

Check the address

Open /admin/email-suppressions and see whether the recipient’s address is suppressed for a bounce or complaint.
3

Fix or unsuppress

Correct the address with the recipient if it was wrong, or unsuppress it if it is confirmed valid.

Notifications

How the notification bell and personal notification history work for every role.

Broadcasts

Compose and send announcements with a per-recipient delivery ledger.

Roles and permissions

See which capabilities each of Zion’s five roles can reach.

Corrections and notifications audit

The org’s general audit log for corrections and other administrative actions.