Using centralised notifications
  • 30 Jan 2023
  • 4 minutes to read

Using centralised notifications


Accessing the notification configuration page

There are various ways to access the centralised notifications configuration page in Totara:

  • To configure notifications that occur at the site level, or that will be inherited by lower contexts, go to Quick-access menu > Notifications.
  • Notifications can be configured in specific instances, such as courses, activities, programs, certifications, performance activities, etc. Typically you can access the notifications for these instances via a link in the administration blocks, or a Notifications tab. See Feature-specific notifications to find out more about accessing notifications at lower context levels.

Regardless of the context in which you access the notifications configuration page, the functionality provided on the page is the same, with a small number of additional configuration options available when configuring notifications at the site level.

It's important to understand that notification content and settings are inherited to lower levels. Updates to fields and settings in a higher context will be reflected in lower contexts unless those fields have been overridden at the lower level. Unchanged fields at the lower level will automatically inherit changes made at the higher level.

Notification triggers

Once on a notification configuration page, you can expand the relevant category to see a list of all notification triggers. If the context you are in only contains notification triggers relating to one category then the list of notification triggers in that category will already be displayed.

Notifiable events

Notification triggers

The notifiable event that triggers the notification being sent.

Delivery channels

Indicates how the notification will be sent. The available delivery channels are:

  • Site notifications
  • Mobile app notifications
  • Tasks
  • Alerts
  • Email
  • Microsoft Teams
EnabledWhether the notification trigger is enabled in this context. If disabled, the trigger will not appear in descendent contexts.

See the following pages for more information:

Configuring notifications

Click a notification trigger to expand it and see the notifications relating to that event. Each notification trigger can have multiple notifications assigned to it. For example, by default the Learner assigned in certification event has two notifications - one that goes to the user, and one that goes to the user's manager.

The notification's Type indicates where it comes from, and determines some actions that can be performed with that notification in the current context:

  • Factory: When viewing notifications at the site level, this indicates that the notification is a built-in notification. These notifications can be modified or disabled in this context, but they cannot be deleted.
  • Custom: Indicates that the notification has been created in the current context. They can be fully controlled in this context and can only be deleted in this context.
  • Inherited: Indicates that the notification is inherited from a higher context. These notifications can be modified or disabled in this context, but they cannot be deleted.

See Notification settings for more information on each of the configurable settings for notifications. 

See the following pages for more information on configuring notifications:

Notification inheritance and templates

The centralised notification system does not provide templates in the traditional sense, but you can set up notifications in a way similar to having templates. Notification inheritance and overrides can be used when you require notifications that will be reused in many (but not all) contexts where a given notification event is applicable.

For example, say that many (but not all) courses on a site require a notification to be sent one month after completion. At the site level, an administrator can create the notification. They can define the recipients, schedule, subject and body to be used in all applicable courses. They can then set the status to Disabled, meaning it will be disabled in lower contexts by default. Then in each applicable course, the Editing Trainer can simply edit the inherited notification, override the status, and enable the notification. The Editing Trainer can also customise the notification as required for each course.

In future Totara releases, it should be possible to configure notifications at the tenant or course category context. When available, in relation to the example given above, it would be possible to enable the inherited notification in a category where the notification is applicable to all courses within that category. The notification could even be disabled for specific courses within that category if it is not required.

Use of text editors

The Weka editor is the default text editor when creating or editing a notification, unless it is disabled on your site. If the Weka editor is disabled you can instead select either the Plain text format, HTML format or Markdown format from the dropdown menu above the text editor. 

If you wish to format your message then you will only be able to use HTML formatting, as JSON (which is used by the Weka editor) is not recognised by many email clients such as Gmail and Outlook. In a future version of Totara we are planning to resolve this issue, but currently it is only possible to format with HTML. 

C065 - Notifications in TotaraThe Totara Academy has a whole course dedicated to Notifications in Totara. Here you can learn more about how to set up and use centralised notifications, see best practice, and give it a go yourself.

© Copyright 2022 Totara Learning Solutions. All rights reserved.


Was this article helpful?

Changing your password will log you out immediately. Use the new password to log back in.
First name must have atleast 2 characters. Numbers and special characters are not allowed.
Last name must have atleast 1 characters. Numbers and special characters are not allowed.
Enter a valid email
Enter a valid password
Your profile has been successfully updated.