Your notification inbox

The bell in the top bar is Lurno’s in-app channel: a running record of things that happened to you or need you. Behind it sits a full-page inbox with your complete history, and — for people who hold the right permission — a separate Platform alerts page for announcements the platform team sent to your organization.

This page is about the inbox surface itself. For choosing which events reach you and on which channel, see Notifications & preferences. For configuring what your organization sends, see Notifications (for admins).

What this does

Every in-app notification Lurno sends you lands in one list, newest first. Each entry carries a title, a short body, a severity, and a timestamp. Some also carry a link to the thing they’re about — a case that needs a look, a module that just unlocked. The bell shows the recent slice; the inbox page shows all of it.

The same inbox appears in both shells. In the admin shell it’s reached from the bell’s View all; in the learner shell the bell’s View all opens the identical page. There is one list per person, not one per surface — reading an item in one place reads it everywhere. There is no sidebar entry for it: the bell is the way in.

Before you start

You need to be signed in. No permission is required to see your own notifications.
The bell sits in the top bar of both the admin shell and the learner shell. Full-screen surfaces that deliberately drop the chrome — the lesson player, assessment delivery — have no bell.
To see Platform alerts, you need permission to view platform alerts, granted at organization scope. See Roles & permissions.

Read your notifications

Select the bell in the top bar. The panel shows your most recent notifications.
Select any row. It’s marked read, and if it carries an in-app destination you’re taken there.
Use Mark all read in the panel header to clear everything at once.
Select View all at the bottom to open the full inbox page.

The inbox page loads 50 notifications at a time. Select Load more to walk further back through your history. It has its own Mark all read button, shown whenever anything on the page is unread.

Seen, read, and dismissed

Three separate states do three different jobs, which explains most surprises about the badge:

Seen drives the number on the bell. It clears the moment you open the bell panel — you don’t have to read anything, and opening the inbox page doesn’t clear it. Above nine, the badge shows 9+.
Read is set when you actually select a row, or when you choose Mark all read. Unread rows are tinted and carry a dot in the bell; on the inbox page their titles are bolder.
Dismissed removes a notification from both the bell and the inbox. Hover a row and select the ✕. There’s no undo, so dismiss things you’ve finished with rather than things you want to come back to.

All three states are stored on the server, so they follow you across devices and browser tabs.

Act on a notification

Some notifications carry a destination, and selecting the row marks it read and takes you there — a wellbeing case opens the triage queue, an unlocked module opens the program, an assessment reminder opens your assessments list.

Plenty carry none. A released grade, a mastered competency, a finished AI generation, a program shared with your organization: these tell you the thing happened and leave you to open it from its own screen. Selecting such a row still marks it read; it just doesn’t navigate.

Some now carry an action rather than only a link. Where the AI assistant has something to propose, the notification says what it would do and offers Accept in the inbox — you don’t have to go to a page and find the thing. Accepting runs it through exactly the same gated path as confirming the proposal in the assistant itself: the same permission checks, the same second-approver rule where one applies, and the same receipt afterwards. See What the assistant changed.

Dismissing is not declining. Dismissing the card means not now; declining the proposal means no. They’re recorded separately, so ignoring a notification is never counted as rejecting what it suggested.

Lurno only ever follows in-app destinations. A notification whose link points anywhere outside the app is shown as plain text with no link, deliberately, so a notification can never be used to bounce you to an external site.

How new notifications arrive

New notifications appear without a page refresh. Lurno holds a live connection scoped to you personally, and a brand-new arrival also raises a short toast in the corner. Toasts are styled by severity — informational, success, warning, or critical — and carry a View button when, and only when, the notification has an in-app destination.

The bell also re-checks about once a minute on its own, and whenever you return to the tab. So if the live connection can’t be established — a proxy, an extension, a flaky network — nothing is lost: the counts stay correct, they just update a little later.

Platform alerts

Platform alerts is a narrower, read-only page: system announcements, service notices, and incident updates that the platform team sent to your organization, most recent first, with a severity marker and an Open link when the announcement points somewhere in the app. It has no menu entry — reach it at /dashboard/notifications/alerts, or from a link someone sends you.

Two things are worth knowing:

It shows your own platform announcements, not everyone’s. Two administrators in the same organization may see different lists depending on who each announcement was addressed to.
It’s a filtered view, not a second inbox. Those same announcements also appear in your bell and in your ordinary inbox, and reading or dismissing one there doesn’t remove it from the alerts page.

This is not the same thing as wellbeing alerts, which are a separate module surface — see Signals, alerts & cases.

What lands in the inbox

The exact set depends on which features your organization uses. Events that currently reach the in-app channel include:

Event	Who gets it
Grade released	The learner whose attempt was released
Competency mastered	The learner who reached mastery
Assessment due soon	The enrolled learner (also by email)
Module unlocked	The learner whose drip-scheduled module opened (also by email)
AI generation ready / failed	The person who requested the generation
Program shared / access revoked	Administrators of the organization it was shared with
Course copy ready / failed	Administrators of the organization the copy was made for
Wellbeing case opened / deadline approaching	The people who handle wellbeing cases
Wellbeing alert escalated	Whoever it escalated to, after it went unacknowledged

Wellbeing notifications are in-app only by design and carry a short reference — plus, for rule-triggered ones, the name of the rule that fired. Never any case content.

Reference

Term	What it is
Bell	The top-bar panel showing your most recent notifications
Inbox	The full paged history, reached from View all
Seen	Whether you’ve opened the bell since it arrived; drives the badge
Read	Whether you’ve opened the notification itself
Dismissed	Hidden from bell and inbox; not recoverable
Severity	Info, success, warning, or critical — sets the icon and toast style
Platform alert	An announcement sent to your organization by the platform team
Essential notification	One that always delivers, regardless of your preferences

Dismissed notifications are permanently deleted after 30 days, and everything is removed after 365 days. The inbox is a working record, not an archive — anything you need to keep long-term should be kept where it actually lives: the attempt, the certificate, the case.

Troubleshooting

The badge cleared but I haven’t read anything. That’s expected. The badge counts unseen items and clears when you open the bell panel. Unread items stay marked unread until you open them or choose Mark all read.

I turned in-app notifications off but still get some. Essential notifications — grade releases, mastery milestones, AI job results, wellbeing alerts — always deliver. Preference toggles govern the optional categories only. See Notifications & preferences.

A notification won’t open anything. Either it carries no destination — many don’t — or its link points outside the app and was deliberately not made clickable. Navigate to the item yourself.

Nothing new appears until I reload. The live connection is probably blocked — often by a corporate proxy or a browser extension. The bell still refreshes about once a minute and whenever you refocus the tab, so nothing is lost.

A notification I dismissed is gone for good. Dismissal is permanent. The underlying thing still exists, so open it from its own screen — the course, the attempt, the queue.

The alerts page bounces me to my organizations list. That’s the permission check. Without permission to view platform alerts at organization scope you’re redirected rather than shown an error. Your ordinary inbox is unaffected and still shows the same announcements.