Skip to end of metadata
Go to start of metadata

LAMS Roles




Global Roles

From LAMS 3.1+ the Author/Course Admin roles have been deprecated. See LDEV-4705

  • System Administrator

System Administrator

Sysadmin is the "walk with the Gods" user in LAMS and it has the following privileges:

  • Has access to System Admin module to set up, modify, archive, hide course/classes/users
  • Adds/Modify tools properties and settings
  • Has all access (write/read/delete/modify) to all Content Folders
  • Can login as any user in the system
  • Has access to all content folders including users's private folders.

This means that they can do anything that a course administrator or a authoring administrator can do plus more. The Sysadmin is God!

Course based roles

From LAMS 3.1+ the Course Admin roles have been deprecated and merged to Course Manager. See LDEV-4705

  • Course Manager
  • Author
  • Monitor
  • Learner

Roles and privileges matrix according to course structure and content

Role

Course Structure

Content

Course Manager

  • Can add/remove/modify classes within the course
  • Can create running instances of sequences that are in
    the course content folder ans assign those to a class
  • Can stop/start running sequences
  • Can monitor the progress of learners
  •   Can add/remove/modify classes within the course
  • Has write/create/delete permissions in course content
    folder and any subfolder within it

Author

No rights

  • Create content for a course in LAMS authoring and save them
    in the course content folder
  • Has write/create/read access for the content folder
  • can delete sequences that he/she has created, but not others

Monitor

  • Can create running instances of sequences that are in
    the course content folder ans assign those to a class
  • Can stop/start running sequences
  • Can monitor the progress of learners
  • Only read access to course content folder (thru Monitor)

Learner

  • Participates in sequences
  • Export their progress on each running sequence (export portfolio)

No rights

Course Manager

The Course Manager role for a course has the following privileges:

  • Can add/remove/modify classes within the course
  • Can create running instances of sequences that are in the course content folder and assign those to a class
  • Can stop/start running sequences
  • Can monitor the progress of learners
  • Can add/remove/modify classes within the course 

Author

The Author role for a course can do the following:

  • Create content for a course in LAMS Authoring
  • Save sequences in the Course content folder
  • Has writing/create/read access on the content folder
  • Can delete sequences that he/she has created, but not of others
  • Has no access to Monitor to run sequences for this course 

Monitor

The Monitor role for a course can do:

  • Can creating running instances of sequences that are in the course content folder and assign those to a class
  • Can stop/start running sequences 
  • Can monitor the progress of learners 

Learner

The learner role for a course allows:

  • Participate sequences
  • Export their progress on each running sequence (export portfolio)

Future Roles

Additionally to the roles described above, we are considering to implement a Parent/Manager Role. This Parent role is linked a learner(s) in courses and allows the Parent to login and see the progress the learner has done in their sequences (sorted by courses/classes). There's also another type of Export Portfolio that exports all the answers/comments for only the son learner, no other learner's comment are to be displayed.

Another future role is Guest, which is a person that comes for only a temporary period of time to a course and gives a lecture or in the case of LAMS facilitates a sequence, discussion, etc. The priviledge this role would have are similar to the current Monitor role but without the ability to run sequences for a class.  

Technical Notes

The roles are defined in the lams_role table. The entries in the privilege matrix above become one or more entries in the privilege table, and the roles are linked to the privilege entries.

Then the user's course roles are recorded by linking the user's role to a particular course, and the permission derived from the role.

The global roles are recorded by linking the user's roles to the ROOT organisation. As a general rule, if a user has permission to do something in the ROOT organisation then they can do it to any organisation.

When the user's details are cached on logon, a list of active organisations (root organisation, active courses and active classes) and their permissions are cached. Many of buttons and links on the index page are generated from cached permissions. The only ones that aren't are related to the lesson entries and the link/buttons for the lesson entries are dependent on the staff/learner lists in the lesson. However the staff/learner lists were created using the user's permissions and hence all the buttons and links on the index page are either directly or indirectly defined by the user's permissions.

 Database Table Model:


 

  • No labels