Skip to main content
Zion watches Goal Check completion patterns and raises an alert when a student, a centre, or a subject crosses a threshold worth a look. Administrators and supervisors both work from the same alerts inbox, but what each role sees and what each role can trigger differs.

Who sees what

The administrator’s alerts inbox, at Alerts in the sidebar, shows every alert across the organization. There is no centre restriction. Administrators also get two manual controls not shown to supervisors: Generate Alerts Now and Send Digest Now.
If an administrator opens the supervisor alerts URL directly, or a supervisor opens the administrator alerts URL directly, the app redirects them to the dashboard. Each view is gated to its own role.

What an alert is

Every alert has three properties:
PropertyValuesNotes
Entity typeStudent, centre, subjectCentre and subject alerts have no linked student profile; they are rendered with their own icon and label.
SeverityCritical, warningShown as a badge on the alert card.
StatusOpen, acknowledged, resolvedThe lifecycle state, described below.

The seven alert types

Each alert type has a default threshold. An administrator can adjust these on the alert threshold settings page.
Alert typeEntityDefault trigger
Consecutive missesStudent3 consecutive missed days
Declining trendStudent20% decline over 2 weeks
Subject struggleStudent60% miss rate on a subject, minimum 5 goals
Sudden dropStudentCompletion rate falls from 80% to 50%
Termly goal at riskStudentProjected to reach only 80% of the term’s goal
Centre low performanceCentreCentre average below 60%
Subject decliningSubjectSubject completion dropping more than 10% over 2 weeks
A separate setting, alert expiry, auto-dismisses a stale alert after a configurable window (7 days by default) if nobody has acted on it. This applies to every alert type and is always on.

Reading the inbox

The inbox has a Severity filter, an Alert Type filter, and three tabs: Unacknowledged, Acknowledged, and All. When a tab has nothing to show, the inbox displays “No Alerts Found.”

Acknowledge and resolve lifecycle

1

Acknowledge

Open an alert and choose Acknowledge. A dialog lets you add an optional note. This moves the alert from open to acknowledged and records who acknowledged it.
2

Resolve

Once the issue behind an acknowledged alert has been handled, choose Resolve to move it from acknowledged to resolved.
3

Reopen

If the same issue recurs, an acknowledged or resolved alert can be reopened, which returns it to open.

Acknowledging in bulk

On the Unacknowledged tab, select multiple alerts with the checkboxes, or use the Acknowledge all warnings shortcut to select every warning-severity alert in one action. Add one note in the shared field and it is attached to every alert in the batch when you acknowledge.

Generating alerts (administrator only)

Alerts generate automatically on a daily schedule, but an administrator can also trigger generation on demand from the alerts inbox:
  • Generate Alerts Now runs the alert-generation check immediately instead of waiting for the next scheduled run. This requires an active subscription.
  • Send Digest Now sends the alert digest immediately.

Alert and report settings

Adjust thresholds per alert type and manage report scheduling.

Goal Check overview

See how daily goal completion is tracked, which is what feeds these alerts.

Attendance alerts

Attendance-specific alerting, tracked separately from the performance alerts inbox.

Roles and permissions

See exactly which role can see and act on which surfaces.