Notifications

Every alert Aegis has sent you — approvals waiting, deadlines approaching, records assigned to you — on one page where you can filter, catch up and clear the backlog.

Aegis notifies you when something needs your attention: a policy pending your approval, an incident assigned to you, a vendor review falling due, a training module about to fall due, a deadline about to pass. Each event lands in two places — a brief entry under the bell in the top bar, and this full page at /notifications. The bell is for a quick glance; this page is where you work through the list properly. Notifications are personal: you see only your own, and every signed-in user has this page regardless of role.

Who uses it

Everyone. Admin, Manager, Contributor and Viewer all receive notifications and manage them the same way — what differs is which events each role tends to receive. An approver sees Policy Pending Approval; a Viewer mostly sees status changes on records they follow, read requests for approved policies and procedures, and training reminders. The figure below was captured as a Viewer.

What's on this screen

The header shows a count such as 14 notifications (5 unread) — the figure on the captured screen; the bell badge in the top bar carries the same unread number. Unread rows are shaded, their round category initial is tinted blue and a small dot follows the title. Each row shows the notification's title, a one-line message and its type (for example Policy Read Required or Training Due Soon), with a relative date such as 2 hours ago on the right. The numbered landmarks:

  1. Preferences, top right, opens Notification Settings — where you configure how and when you receive notifications across the available channels. Mark all as read appears beside it whenever anything is unread.
  2. The Category: filter narrows the list to one notification type. It starts on All Categories and lists every type Aegis can send — from Incident Assigned and Risk Review Due to Policy Read Required, Regulatory Update and Training Due Soon. The unread count in the header follows the filter.
  3. The Unread only tick-box hides everything you have already seen — the quickest way to catch up after a few days away.
  4. The list itself, headed by a select-all tick-box and the Notification and Date columns. The header tick-box selects every row on the current page. Each row has its own tick-box for bulk actions and a bin icon to delete it (on a desktop screen the bin appears when you hover over the row).
The notifications page — /notifications.
The notifications page — /notifications.

Catch up after time away

  1. Tick Unread only. The list drops to what you have not yet seen.
  2. Select any row to act on it. Opening a notification marks it read and, where it points at a record — the incident, the policy, the vendor — takes you straight there.
  3. For rows that need no action, tick their boxes. A count such as 3 selected and a Mark as read button appear at the right of the filter bar; select it — or select Mark all as read in the header to clear everything at once. Marking read never deletes anything; the rows stay in the list for reference.
  4. Use Previous and Next under the list if there is more than one page; the list shows 20 rows per page and the footer shows which slice you are on, for example Showing 1 to 20 of 64 and Page 1 of 4.

Delete a notification

  1. Hover over the row and select the bin icon (Delete notification). A confirmation dialog asks whether you are sure, naming the notification.
  2. Select Delete to remove it, or Cancel to keep it. Deletion cannot be undone; the header count drops by one.

Choose what reaches you

  1. Select Preferences. The Notification Settings page (also reachable via Settings) lists the notification types, grouped by area, with a toggle per channel.
  2. Turn off what you do not need rather than ignoring it — a feed you trust is one you will actually read. Deadline and approval notifications are worth keeping on for anyone who owns records.
  3. Pick how email reaches you in the Digest column of each row: Immediate sends one email per notification, Hourly, Daily and Weekly gather them into one digest email. Daily digests go out at 09:00 and weekly ones on Monday at 09:00. Slack, Teams and in-app notifications still arrive one by one.
  4. To change every row at once, choose a mode in Set all digest modes above the list (it offers Immediate, Daily and Weekly), then select Save Changes. Daily and Weekly leave the time-critical alerts on Immediate; change those one by one if you really want them batched.

Organisation default (administrators)

A notification type you never set follows the organisation default, which is Daily unless an administrator changes it. Administrators set it in Organisation default delivery at the top of the same page. Rows a user has already saved keep their own setting.

Time-critical alerts ignore the default and always arrive immediately unless the user chooses otherwise: incident, NIS2 and DORA reporting deadlines, GDPR breach alerts, DSR deadlines, security alerts and new whistleblowing reports. They also ignore quiet hours. Anything else that falls inside your quiet hours is held back and delivered when the quiet period ends, never dropped. Sign-in, account and invitation emails are not notifications and are never batched.

Tips and limits

Where this connects