Notifications: the bell that tells you something already happened
The in-app inbox for staff: what changed, and what you still have to do.
Notifications is the screen behind the bell in the header. It collects everything the school’s own activity generated while you were busy somewhere else: a result published, an application approved, a fee fully settled, a store order validated, a payout confirmed, a logbook waiting for verification. It exists because most of the things that matter in a school happen while somebody else is looking at a different screen.
The bell shows the ten most recent items and a count of the unread ones. Clicking Notifications in the sidebar, or on the count, opens the full inbox: every message for your account, newest first, searchable, fifteen to a page. One message belongs to one account — opening yours does not mark somebody else’s as read.
The menu is opened by a super administrator, an institution admin, a secretary and a bursar. A teacher does not see it: the things that reach a teacher’s inbox arrive as a correction to grade, or as the correction of a submission they marked, and both of those are told to them on the screen where they happened. The distinction is a simple one — this inbox is for the people who run the school, not for the people who teach in it.
Working the notifications inbox
Three actions, and one habit that keeps it useful.
-
Step 1
Read the count, not the bell
The number on the bell is how many messages are unread. Open the menu if it is not zero at the start of the day.
-
Step 2
Open Notifications from the sidebar
The full inbox lists every message for your account, newest first, searchable, fifteen to a page, with Previous and Next at the foot.
-
Step 3
Open the thing, then mark it read
A message usually links to the screen it refers to. Deal with it there, then use Mark all as read to clear the counter at the end of the day.
-
Habit
Empty it daily
An inbox cleared every morning tells you what happened. An inbox cleared every fortnight tells you nothing.
-
When you need one
Use the search box
Search by a learner name, a reference or a word from the message to find the one you were told about.
What actually lands in the bell
Most of it is written by the platform, not by a person.
Results published
When an administrator publishes a class board, every learner who has a result is told that their results are now visible. This is the single most common notification in a school, and the one worth reading: it means a real person made a decision that families are now seeing.
Admission and enrolment
An applicant is told when their file is approved, and the family is told when the learner’s fees are fully settled — the moment their file stops being a pending file. These are generated by the decision itself, which is why a family is never left wondering whether their child’s place was confirmed.
Money moving
A store order that has been validated or cancelled, a payment that has failed at the operator, a payout whose status has changed: each of these reaches the person who caused it. For a bursar this is the fastest way to catch a transfer that has not gone through, because the notification arrives the moment the status moves rather than the next time you remember to look.
Work waiting for a decision
Corrections you have graded but not released, applications waiting for a review, logbook sessions that nobody has verified: these are not messages, they are the action centre on the Overview dashboard. The inbox tells you what already happened; the dashboard tells you what is still waiting. A school that reads both has nothing left to chase.
Reading and clearing, without losing anything
Two ways to mark, and one habit worth keeping.
Opening a message is not the same as marking it read
Reading and clearing are separate acts, which is deliberate. Open a notification and the message takes you to the screen it refers to — the application to review, the learner to open, the order to validate. When you have dealt with the thing itself, come back and use Mark all as read to bring the counter to zero. This ordering matters: a message marked read but not acted on is a job that has been hidden rather than done.
Mark all as read is safe, deleting is not
Mark all as read only changes how the bell displays the list; nothing is removed and no record is destroyed. The messages stay in the inbox and stay searchable. That is why clearing the counter every morning is a reasonable habit even in a busy week: nothing can be lost by marking, and everything is still there if somebody asks what the school was told and when.
Your inbox is yours
Each account has its own inbox. A secretary’s notifications are not a copy of the bursar’s, and neither of you sees the other’s. When you hand over a duty — a month at the counter, a term in the office — the colleague who takes it sees their own messages for the period they are covering, not yours.
If the bell is empty and the work is not
An empty bell is not proof that nothing is waiting. Work that has been created but not acted on — an unpublished correction, an application with no decision — generates no notification, because no event has happened yet. That is exactly why the Overview dashboard carries an action centre: read it every morning alongside the bell.
Notification questions
Asked by office staff who want to trust what the bell tells them.
-
Why can’t my teacher see Notifications?
Because the inbox is for the people who run the school. A super administrator, an institution admin, a secretary and a bursar open it; a teacher and a lecturer do not. The things a teacher needs to know are told to them where they happen instead — a submission they marked being corrected, a result being published for their class appears on the screen they were already on.
-
Does Mark all as read delete anything?
No. It changes how the bell displays the list and nothing else. Every message stays in the inbox, stays searchable and stays available to open again. Clearing the counter each morning is therefore safe: it hides nothing from the record, it only stops the number from growing.
-
The bell is empty but I know there is work waiting. Why?
Because a notification is generated by an event, and work that has not been acted on has not produced an event yet. An unpublished correction and an application with no decision are both silent. That is what the action centre on the Overview dashboard is for: it counts work waiting regardless of whether an event has happened. Read the bell for what already occurred, and the dashboard for what is still outstanding.
-
Can I see my colleague’s notifications when I cover for them?
No, and you should not be able to. Each account has its own inbox, so a colleague covering your duty sees the messages generated for their own account during the period they cover, not the ones you received. If a decision was made on your account while you were away, the colleague who needs to know will find it on the screen it concerns — the applications list, the payments list — rather than in your bell.