Admin: Roles for a large part determine what a user can do Cirrus
- Item and Collection authoring roles and workflow
- Example collection role setting: Allow Subject Matter Experts (SME's) to develop items directly Cirrus
- Assessment authoring roles
- Site roles setup users for those specific parts of Cirrus relevant to their tasks
Item and Collection authoring roles and workflow
The item authoring in Cirrus is fully web-based. Workflows for quality assurance can be set up to facilitate the desired way of working. For example, a Collection (bank containing items) can be shared with co-workers and they can be given different permissions within that collection.
A typical workflow looks like this (but can indeed be adjusted to need):
- The owner of the collection creates a new collection
- The owner shares the collection with a co-worker and gives that person the Reviewer role
- The owner creates an item and changes the status from Draft to Ready for review
- The Reviewer is notified on their Dashboard that an item needs reviewing and checks the items and comments on it
- The owner checks the comments from the reviewer and changes the status to either Approved or Not approved
Revisions can be compared with each other and authors/reviewers can comment on revisions. This helps tracking how the item develops in time or in doing a roll back.
The permissions of a role can be set up by the admin. Below is an overview of what the default collection roles look like:
Example scenario on collection role setting: allow Subject Matter Experts (SME's) develop items directly Cirrus
- Determine the access levels to items (what an item author can do or see) - taking the screenshot above an example. So you determine the different collection-roles
- Create a site-role ('SME') via Admin > Roles > Site which only has access to the Library
- Create an user account for the SME and give it the SME role
- Create the collection with the correct settings and the Learning Objective repository
- Share the the collection with the account and set the collection level access by selecting the correct collection-role.
Assessment authoring roles
As with collections, roles can also be set up for assessment authoring. This works in the exact same way as collection roles and are used to organise the workflow of assessment creation and quality assurance of these.
Site roles setup users for those specific parts of Cirrus relevant to their tasks
Site roles are used to define permissions on your environment level. Cirrus provides a set of default roles, like Admin, Author and Candidate, but these can be expanded depending on the complexity of the organisation. For example you could create specific Marker role or Invigilator role. Users with these roles will only have access to specific parts of the Cirrus platform needed to perform their tasks.
Roles are set up by the admin of the site and have a very high level of customisation:
Site Role: Admins can 'Login As' another user
User like Admins and Coordinators can be granted the permission to login as another user.
This will be a setting under Admin > Roles > Site > 'Login As'
If this has been enabled you can login as a user by going to Admin > Users and clicking on the 'eye' icon next to the user details.
The Roles Type levels are taken into account for being able to Login as other users:
- System Admin can overtake: System Admin / Admin / Author / Candidate
- Admin can overtake: Admin / Author / Candidate
- Author can overtake: Author / Candidate
- A new window will open (for most browsers you will need to agree to allow pop-ups like this from Cirrus) and you will be automatically logged in as that user.
- A blue bar at the top warns you that you are viewing and doing things in name of this user.
- The user itself will get a notification on their Dashboard (if enabled for them) that you have done this.
Image showing logged in as use via blue bar:
Image showing warning on user's dashboard: we will add this closer to our release of this feature.