Setting notification preferences

Notifications decides which events reach people, and by which route. It sets the position for the whole account rather than for you.

That is the thing to be clear about before changing anything. Turning something off here turns it off for everybody, not for the administrator who found it noisy.

Where it is

Choose Admin, then Workspace and Notifications. The screen has two tabs: Notification preferences, covered here, and Email templates, which changes the wording rather than the sending.

The table

One row per kind of event, with a column for Email and a column for Push. The two are independent — an event can do both, either, or neither.

The rows cover assignments and approvals, course comments, category subscriptions, workflow notifications, skills gap themes, 360 feedback, AI course generation, third-party integrations, report exports and subject data exports.

How often the emails go

Some rows carry a frequency as well as a switch, and the choice is between none, as it happens, daily and weekly.

This is the setting that decides whether a busy account is usable. An event that fires fifty times a day is fine as a daily summary and unbearable as it happens, and the answer is the frequency rather than switching the whole row off.

What is not on this tab

The lower part of the screen holds training reminders — due dates, certification expiry, skill expiry and CPD. They work differently: each has its own schedule of before-and-after intervals, its own frequency, and its own decision about whether managers are told, and they save with their own button.

Those are covered in Reminders. Do not treat them as more rows in the table above; changing one and pressing the wrong Save leaves the other half unsaved.

What happens when you save

Save changes applies to everybody in the account from that moment. Nothing already queued is recalled — somebody who triggered a notification a minute ago still receives it.

Turning a row off stops the sending; it does not stop the event. The thing still happens and is still recorded, and anybody looking at the relevant screen still sees it. This is a setting about interruption, not about activity.