In LAAMP, user access and functionality are determined by Permissions. These are structured into roles that define what each user can see and do within the system. Understanding these roles is essential for configuring access appropriately across your organisation.
What Are Permissions?
Permissions are assigned to users during setup or by an Administrator. They determine the tools, features, and data a user can access. This ensures each user only interacts with the system in a way that suits their responsibilities.
Key Permission Roles in LAAMP
Role | Functionality Overview |
---|---|
User | Access to complete training, view assigned competencies, and track their progress. |
Assessor | Able to conduct Practical Assessments and review evidence. |
Coordinator | Manages users, verifies assessments, generates reports, and helps with training oversight. |
Authoriser | Provides final approval for completed assessments. |
Administrator | Full access to all settings, reporting, user management, content creation, and automation tools. |
Publisher | Can create, edit, and publish training content such as Courses and Competencies. |
Reviewer | Scores Review Assessments and participates in capability reviews. |
Multiple Permissions per User
Users can hold multiple permissions. For example, someone could be both an Assessor and a Coordinator. When this happens, the Permissions Switcher allows the user to toggle between roles and see the relevant interface for each.
Managing Permissions
To update a user’s permissions:
Navigate to the User List (Admins/Coordinators only).
Select a user and open their profile.
Allocate the required permission types.
Save changes. The user will see updated options upon their next login or permission switch.
Best Practice Tip
Keep permission roles aligned with real-world responsibilities. Avoid over-permissioning users unless necessary—it helps reduce confusion and simplifies training experiences.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article