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 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.

What's on this screen

The header shows a count such as 12 notifications (3 unread). Unread rows are highlighted; each row shows the notification's title, message and category, with its date 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 event type — incidents, risks, policies, vendors and so on. 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, with Notification and Date columns. Each row has a tick-box for bulk actions and a bin icon to delete it; the header tick-box selects the whole page.

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 and select Mark as read — 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 footer shows which slice you are on, for example Showing 1 to 20 of 64.

Choose what reaches you

1. Select Preferences. The Notification Settings page (also reachable via Settings) lists the notification types 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, 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

• The bell and the page always agree. The badge on the bell is your global unread count; View all notifications at the foot of the bell's dropdown brings you here.
• Deleting is per row and permanent. There is no bulk delete and no undelete. If you only want a quieter list, mark rows read instead.
• An empty list is a good sign. With no notifications at all the page says No notifications yet; with filters excluding everything it offers to adjust them; when nothing is unread you are told You're all caught up!
• Notifications are pointers, not the record. The truth lives on the record's own page; a notification just tells you to go and look. Deleting one changes nothing about the underlying record.

Where this connects

• The screen layout — where the bell sits in the top bar.
• Settings — the home of Notification Settings.
• Incidents and Policies — two of the modules that notify most: assignments and deadlines from one, approval requests from the other.
• Workflows — automations that can generate notifications of their own.