Skip to main content
Zion keeps two separate audit logs for administrators: one for retroactive corrections to locked records, and one for every notification the school has sent. Both are read-only history views, and both are restricted to the administrator role.
This page covers the corrections audit log and the notification audit log only. It does not cover the alerts inbox, the SEO dashboard, or the internal webhook-events tool used by Zion’s own operators.

Corrections audit log

Some records in Zion get locked after submission, such as a goal entry, a goal check, a back-dated check, or a test score. When an administrator or supervisor needs to fix one of these after the fact, that fix is logged as a correction rather than a silent edit. Supervisors can make corrections to records in their own centre. Only administrators can view the org-wide corrections audit log that shows every correction made across all centres.

Where to find it

Navigate to People & Centres > Corrections Audit in the sidebar, or go directly to /admin/corrections-audit. If you are not an administrator, this page redirects you to your dashboard.

What each row shows

ColumnWhat it contains
TimestampWhen the correction was made
ActorThe name of the administrator or supervisor who made the correction
ActionA badge identifying the correction type: goal entry, goal check, back-dated check, or test score
ResourceThe type of record that was amended
Change summaryA computed before-and-after comparison of the fields that changed
ReasonThe mandatory correction reason the actor entered when making the fix
Expand any row to see the full before-and-after JSON snapshot of the record, not just the summarized field changes.
The table loads more history with a Load more control as you scroll, rather than numbered pages.

Investigating a disputed record

1

Open the corrections audit

Go to People & Centres > Corrections Audit in the sidebar.
2

Locate the record

Scan the table for the relevant student or date, using Load more to pull in older entries.
3

Expand the row

Open the row to see the full before-and-after JSON and the actor’s stated reason for the change.

Notification audit log

The notification audit log records every notification the organization has sent, across every delivery channel, so an administrator can confirm whether a message actually went out and whether it was delivered. This log is administrator-only and org-wide. It is not scoped to a single centre.

Where to find it

The notification audit log is reachable at /admin/notification-audit. Unauthenticated visitors are sent to sign in, and any signed-in user who is not an administrator is redirected to their dashboard.

What each row shows

ColumnWhat it contains
NotificationThe title and category of the notification
ChannelIn-App, Email, or WhatsApp
Statusqueued, sent, read, failed, or dead
Delivery outcomeEmail only: Delivered, Bounced, Complaint, or No signal
SentThe timestamp the notification was created or sent
The table can be filtered by channel and by status, and loads additional history with Load more.

Checking whether a parent received a message

1

Open the notification audit log

Go to /admin/notification-audit.
2

Filter by channel or status

Narrow the list to the channel in question (for example Email) or to a status such as failed or dead.
3

Read the delivery outcome

For email, check the delivery outcome badge to see whether the message was delivered, bounced, or flagged as a complaint.

See also

Alerts overview

Read the performance alerts inbox that surfaces at-risk students, centres, and subjects.

Notifications overview

Understand how notifications are generated and sent in the first place.

Notification deliverability and audit

Learn more about how notification deliverability is tracked.

Grading audit trail

See the audit trail for grading-specific score history.