...
NOTIFICATIONS
| Tip |
|---|
Lucidity Access: 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.
| Warning | ||
|---|---|---|
| ||
In order to receive email notifications all users must have a valid notification email address in their user profile. Refer to the Users page within this user guide for more details. If your users have issues receiving their emails, visit the FAQ section in 'My Emails User Guide' |
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
| Info | ||
|---|---|---|
| ||
Lucidity will generally manage all system notifications, please contact Lucidity Support for assistance. |
Standard Lucidity Notifications
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 | Issue has been closed | Person creating the issue |
| Incident | Standard | Issue has been rejected at close out | Responsible Manager |
| InForm | Standard | Existing form record is assigned to a new Respondent | 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 | Optional | 30 days prior to contractor document expiry date | Contractor Manager |
| Contractor | Optional | 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 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 |
| 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 |
| Note | ||
|---|---|---|
| ||
Please 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:
...