Skip to content

In-app notifications

Applies to: all signed-in school staff (web header bell); students (portal Messages page). Last reviewed: 2026-11-18.

DriveFlow has no stored in-app inbox for staff. What it has are two different things that both carry the word "notifications":

  1. The bell in the web header - a live list of work that needs attention, calculated from the data each time it is opened.
  2. The student portal Messages page - a read-only copy of the emails, SMS and WhatsApp messages already sent to that student.

Note

Neither is a delivery channel of the notification engine. Nothing is "sent" to the bell, there is no read/unread state, and an item disappears by itself when the underlying work is done.

1. The bell in the header (staff)

Where: the bell icon at the top right of every page. A red badge shows the number of items.

Who: every signed-in user of a school with a running subscription. What each person sees depends on their permissions and plan; an instructor who does not manage everyone's lessons sees only their own lessons.

Using it

  1. Click the bell. A panel titled Notifications opens, with a line such as "3 items need attention".
  2. The panel shows up to 10 items. Click an item to go to the record.
  3. Click the refresh icon to reload.
  4. Click View all notifications to open the full page (/notifications, title Notifications, subtitle "Lessons, pickups, driving tests, overdue invoices and vehicles that need attention").

The list reloads when the bell is opened and automatically every 2 minutes while the page is open.

Screenshot to be added

Screen: Header. Should show: the bell panel open with several alert types listed.

What appears

Built by HeaderService.GetAlertsAsync (DriveFlow.Infrastructure/Services/HeaderService.cs):

Item Meaning
Lesson request · <student> A student asked for a lesson online and it still waits for approval. Requests whose time has passed are not shown.
Follow-up today / Overdue follow-up · <lead> An open lead follow-up due by the end of today, assigned to you or to nobody.
Lesson <day> <time> · <student> / Pickup <day> <time> · <student> Upcoming lessons today and tomorrow. A lesson with a pickup location is shown as a pickup; one within the next two hours is highlighted.
Sign-off needed · <student> A lesson with status Awaiting Instructor Sign-off. Nothing in the application sets that status, so this item does not appear in practice.
Driving test <day> <time> · <student> Upcoming driving tests.
Overdue invoice <number> Invoices marked overdue, or past due and not yet marked by the daily job.
Extra lesson to schedule · <student> A student has paid or free extra lessons that are not booked yet.
Vehicle items Licence disc, roadworthy or insurance expiring within 30 days (or expired); a service due within 14 days or 500 km. Sold vehicles are ignored.
Fleet items Fleet Management alerts (unusual fuel use, kilometres not logged, odometer readings that do not fit, services due by kilometres). Enterprise plan feature.

The bell does not send messages

This is where lesson requests, lead follow-ups and vehicle expiry dates are surfaced. None of them produce an email, SMS, WhatsApp or push message.

Limitations

  • No history, no "mark as read", no dismiss.
  • Not shown once the subscription has ended (only the subscription page is open then).
  • Not pushed: a user who is not looking at the web app is not told.

2. Messages page in the student portal

Where: student portal > Messages. The portal header also shows a count.

Who: the signed-in student.

It lists the 50 most recent messages recorded in the notification log for that student (StudentPortalRepository.GetNotificationsAsync):

  • emails whose recipient equals the student's current email address,
  • SMS and WhatsApp messages whose recipient equals the student's current phone number,
  • excluding any message with status Failed.

For an email the student can click Show email to see it exactly as sent.

Limitations

  • Matching is by the address on the student's record now. If the email address or phone number is changed, older messages sent to the previous address no longer appear.
  • Push notifications are not listed.
  • Emails that are not written to the log (portal invite, password reset) are not listed.
  • Two students sharing one email address in the same school would see each other's emails here.

The mobile app has an equivalent Messages screen for students; see Mobile app overview.

3. Lesson requests dialog

Staff can also open pending lesson requests from the bookings area (the Pending Requests dialog). Approving or declining there is what triggers the "Lesson Booking Confirmation" or "Lesson Request Declined" message to the student; see Notification triggers.