Competency FAQs
Who is this article for?Administrators who want to learn more about Lucidity Competency.
Administrator permissions are required.
These FAQs are designed as supplemental documentation to the main user guide. It aims to provide a better understanding and use of Lucidity Competency and its linked applications such as Lucidity HR, Lucidity Access and Lucidity Induction.
Please ensure that you have the correct administrative access to perform the required task. The system administrator can assist with this.
- How can I locate the answers for assessment questions within an eLearn training course?
- A user had been created in Lucidity HR and has been linked and given the correct permissions in Lucidity Access. Why can't their manager find and view their records?
- A user had been added to a role. Why aren't the role and needs displaying on the People page or on the Needs page?
- A user has failed an eLearn in Competency. How do I reset the module so they can attempt it again?
- What is the best way to manage annual refresher training that everyone completes at the same time, regardless of when they completed the initial course?
1. How can I locate the answers for assessment questions within an eLearn training course?
If you are having difficulties with answering the assessments and/ or passing the online courses, please contact your local Training representative or the owner of the eLearn module.
System administrators can view and edit assessment questions that are built within Lucidity Induction by clicking Edit on the relevant module. Refer to the Assessment Questions section of the Assessment page in the Lucidity Induction user guide for more details.
2. A user had been created in Lucidity HR and has been linked and given the correct permissions in Lucidity Access. Why can't their manager find and view their records?
This is likely to be due to the scoping on the manager's account. The manager is restricted to certain organisations which must correspond to the user's organisation. If they differ, the manager will not be able to view the user. Therefore, changes must be made to ensure these match by either:
-
Change the user's business unit/ division in Lucidity HR to match the scoping of the manager.
-
Or, change the scoping of the manager in Lucidity Access to include the business unit/ division of the user.
3. A user had been added to a role. Why aren't the role and needs displaying on the People page or on the Needs page?
The role is working correctly if other users assigned to this role have no issues and their needs have been created. Therefore the issue lies with the user account and there is likely a duplicate account for them.
4. A user has failed an eLearn in Competency. How do I reset the module so they can attempt it again?
- For Lucidity Competency: System administrator must delete existing need and reassign it if attempt limit is reached.
- For Lucidity Induction: Refer to the Reset a Failed Course section in the Records page of the Lucidity Induction user guide.
5. What is the best way to manage annual refresher training that everyone completes at the same time, regardless of when they completed the initial course?
In this situation, a new capability each year is the most efficient way to manage this. It also means reports can be used to view previous years existing records and outstanding needs.
-
Create initial course as a new capability labeled with the year (e.g., XYZ-2019).
-
Create role(s) requiring this capability, include additional capabilities, and enroll relevant users.
-
Enroll new users into required roles as they join.
-
Enter completion records with no expiry date (automatic for eLearning courses). For refresher:
-
Create new capability for new year (e.g., XYZ-2020). Copy previous year's version if needed.
-
Add new capability to all required roles.
-
Optionally remove previous year's course from roles (note: removes existing needs but not records).
-
Enter completions with no expiry date.
-
Run reports to view records vs. needs as required.
-
Note: Entering completions without expiry dates prevents previous years' records from showing as expired, as each year's record is separate and unlinked.