Page Comparison

While the term "role" defines the security permissions a user has (e.g. what what a user can do), the term "cohort" defines the security group for a user (e.g. who who a user can do it to). In other words, the role of "Supervisor" allows a user to view the compliance report. The cohort the Supervisor is in charge of determines who they can see in the compliance report.

To a large extent, cohorts are created automatically by the learning environment if it's integrated to your OSS/BSS systems, such as an HRIS or Active Directory server. That being said, you you can manually create cohorts to represent a group by role, function or department, and then allow an administrator of that cohort to view its members in reports. For example, if you'd like the Volunteer Administrator to be able to run the compliance report but only for volunteers, you could create a "volunteer cohort", set the Volunteer Administrator as the administrator of that cohort, and set volunteers as members of that cohort.

Step-by-step Guide

To manually add a cohort:

1. Go to Site Administration > Users > Cohorts

2. Click on the "Add new cohort" tab

3. Give it a name (mandatory) and Cohort Id / Description (optional)

4. Click on "Save changes" at the bottom of the page

Image Removed

Image Added

Important Notes

• If you are managing a system deployed in a

  /wiki/spaces/Healthcare/pages/34844303

  multi-site deployment, an additional field called "Parent site"

  will

  may appear at the bottom of the form. You must select which site (the "parent") the cohort will belong to.