New article
Recently updated
Managing Access notifications
Who is this article for?Administrators who want to learn to manage Access notifications.
Administrator permissions are required.
This guide explains how to customise your notification preferences in Lucidity Access.
1. Notifications
Video: Notifications Overview
Each module in Lucidity may have a series of automated notifications that are delivered in response to certain actions within the system. Notifications will be sent from Lucidity to an end users email address based on select criteria, such as when an action is assigned to a user or when a user is assigned the responsible manager role in an Incident and so on. These are typically part of automated system work flows and are useful to ensure end users are notified when they have certain tasks to complete in the system.
Note: In order to receive email notifications all users must have a valid notification email address in their user account.
From the Notifications page, administrators can:
- View all previously sent notifications including content, recipient, date sent and read status.
- Generate reports on notifications sent from the system.
2. Standard Lucidity notifications
Lucidity will generally manage all system notifications, please contact Lucidity Support for assistance. Standard system notifications are typically established for all modules as part of the implementation process. The standard list of notifications is as follows:
|
Module |
Availability |
Trigger |
Recipient |
|---|---|---|---|
|
Incident |
Standard |
Issue has been created. |
Responsible Manager |
|
Incident |
Standard |
Issue has been created. |
Close Out Manager |
|
Incident |
Standard |
Issue is awaiting closeout (all actions closed, status = complete). |
Close Out Manager |
|
Incident |
Standard |
When the responsible manager is updated at any point of the Incident life cycle. |
Responsible Manger |
|
Incident |
Standard |
When the Close-out manager is updated at any point of the Incident life cycle. |
Close Out Manager |
|
Incident |
Standard |
Issue has been closed. |
Person creating the issue |
|
Incident |
Standard |
Issue has been rejected (reinstated to Draft) after the close out. |
Responsible Manager |
|
Incident |
Standard |
Issue has been rejected (reinstated to Draft) after the close out. |
Close Out Manager |
|
Incident |
Standard |
Issue has been rejected at close out. |
Responsible Manager |
|
InForm |
Standard |
Existing form record is assigned to a new Respondent or Approver (all forms). |
Respondent |
|
InForm |
Standard |
New public form is submitted and has an approval element. |
New Respondent |
|
Competency |
Standard |
On the day, when the training record expires (for each record). |
Learner |
|
Competency |
Standard |
30 days prior to training record expiry date (for each record). |
Learner |
|
Contractor |
Standard |
30 days prior to contractor document expiry date. |
Contractor Representative |
|
Contractor |
Standard |
30 days prior to contractor document expiry date. |
Contractor Manager |
|
Contractor |
Standard |
1 days prior to contractor document expiry date. |
Contractor Representative |
|
Contractor |
Standard |
0 days prior to contractor document expiry date. |
Contractor Representative |
|
Contractor |
Standard |
Contractor is required to submit a document. |
Contractor Representative |
|
Contractor |
Standard |
Contractor has submitted a required document for approval. |
Contractor Manager |
|
Contractor |
Standard |
The submitted contractor document has been approved. |
Contractor Representative |
|
Contractor |
Standard |
Submitted document has been rejected and requires re-submission. |
Contractor Representative |
|
Actions |
Standard |
New action is saved. |
Actionee |
|
Actions |
Standard |
Existing action is assigned to a new Actionee. |
Actionee |
|
Actions |
Standard |
Action is reopened. |
Actionee |
|
Actions |
Standard |
Action due in 7 days. |
Actionee |
|
Actions |
Standard |
Action due tomorrow. |
Actionee |
|
Actions |
Standard |
Action 1 day overdue. |
Actionee |
|
Actions |
Standard |
Action 3 days overdue. |
Actionee |
|
Actions |
Standard |
Action 5 days overdue (escalation to Line Manager). |
Actionee's Line Manager |
|
Induction |
Standard |
30 days prior to course expiry date. |
Self-Registered Learner |
|
Induction |
Standard |
On day of course expiry. |
Self-Registered Learner |
|
Induction |
Standard |
On completion of successful induction. |
Self-Registered Learner |
|
Permit to Work |
Standard |
A permit has been submitted. |
Permit Approver |
|
Permit to Work |
Standard |
A permit has been approved. |
Permit Approver |
|
Permit to Work |
Standard |
A permit has been started. |
Permit Approver |
|
Permit to Work |
Standard |
A permit has been finished. |
Permit Approver |
|
Permit to Work |
Standard |
A permit has been closed. |
Permit Approver |
|
Permit to Work |
Standard |
A permit has been Rejected. |
Permit Manager |
3. Editing notifications
Note: Support requests associated with notifications may incur additional charges. Each query will be evaluated independently and clients made aware of any potential charges prior to any work being completed.
The below shows an example of how a notification for an action may look:
4. Notification scoping
All notifications are "scoped" by default. This means they are only sent in association with records, forms, issues etc which the user has permissions to view. For example, if its desirable to only have a manager receive notifications for Incident issues that are allocated to their business unit, then scoping that manager to only see issues for their business unit will automatically scope the notifications at the same time. This can be managed via the individual user account in Lucidity Access.