Groups and Roles

All about the containers of maps (aka Scenarios or webinars). These are means to create sets of users and maps for management by course designers. Often managed externally by a LMS.

What are Courses?

Courses are a functional grouping of sets of maps, along with sets of users who can play those maps. Kinda like a superset of maps, if you like.

In OLab3, they were called Scenarios (see Glossary) and had an odd dual function. As well as providing another layer to access control (who could play a map), they also provided a way of grouping sessions for reporting purposes.

They are a little bit similar to a Course in a Learning Management System (LMS).

In OLab4.6 onwards, learning designs that involve supersets of cases and other materials can be handled by the parent LMS that you are using to authenticate users into OLab.

So far, this approach has been tested with Moodle but uptake has been limited. For more information about these issues, see https://olab4.net/courses-groups-sets-and-scenarios/

We have introduced Groups and Roles to internally manage our access control lists (ACLs) which determine who can do what with which resources.

Groups

Primarily, these are sets of Users. They are related together with Roles. See Users, roles

Using the OLab4 System Management Tool (SMT), course and curriculum designers can now allocate users to groups, maps to groups, and users to roles.

This approach is much more powerful and flexible. It avoids some of the constraints of previous approaches and gives us more flexibility to align with the Identity & Access Management System (IAMS) functions of the LMS.

The approach can also be used without an LMS, which opens things up for authors without enterprise-level systems for user management.

Note that Groups in OLab4 are not the same as OLab3 Groups, which were just convenient collections of Users. In OLab4, Groups have a strong functional relation to Roles; they also relate to Users and Maps.