Skip to content

Notifications

Notifications is always on and never a screen of its own: delivered in-app and by mail, tied to the record they are about, and filtered by what the reader is allowed to see.

Try it in the demonotifications · 3 tasks

Before you start

  • Working mail, if notifications are to arrive by mail as well as in-app.

What Notifications does

Always on, never a screen of their own.

01

Receive in-app and by mail

Both routes carry the same notification, so somebody who is not signed in still finds out.

02

Go from a notification to the record

A notification is tied to the thing it is about. That is what makes it actionable rather than an announcement that something happened somewhere.

03

Rely on permission filtering

Notifications respect the reader’s permissions. Nobody is told about a record they could not open.

What it claims to do

The capability list this guide is written against, unabridged. Nothing above adds to it.

Notifications on the Administration page
  • Delivered in-app and by mail
  • Tied to the record they are about
  • Respect the reader’s permissions

Where it connects

The modules Notifications hands work to, or takes it from. Most problems that look like one module are a handover between two.