Also answers:
- What can a viewer do?
- What can commenters do?
- What can editors do?
- What can managers do?
“The team was engaged in the building process in a way that I hadn’t seen before. I really feel like it was because they were so involved with Coursetune.” -Debora M. Dole, Ph.D., CNM, FACNM, Associate Professor and, the department’s Vice-Chair |
Coursetune works best when teams can collaborate and contribute together. There are many flexible options for roles and permission. In this article, you'll see several charts that detail who can do what and where. Because the four Coursetune levels are customizable, we will refer to the default language of Coursetune in this article:
- Institution (Level 1)
- Division (Level 2)
- Program (Level 3)
- Course (Level 4)
There are four team roles in Coursetune:
- Viewers (V) - can see the curriculum plan, mappings, and reports
- Commenters (C) - can do what viewers do and participate in discussions around the courses
- Editors (E) - can do what commenters do and edit the curriculum plan
- Managers (M) - can do what editors do and can change who is on a team (with what roles), change the status of suggestions, and move courses and programs
In a course (level-4 object), and depending on the size of the team, there are typically only one manager, one to two editors, and dozens of commenters and/or viewers. We recommend this ratio to maintain organization, data and facilitate healthy collaboration.
NOTES:
- At the institution level, the only role that can be designated is a viewer role.
- Only admins can create divisions (If you need a division created, please contact your team administrator).
Roles on Institution (Level 1)
This role on an Institution can do the following | V | Admin |
Create a division | ✓ | |
See who is on the institution team (access) | ✓ | |
Add viewers to the institution team (access) | ✓ | |
Make team member a manager of a division (access) | ✓ | |
Create and edit Institution level outcome sets (IOS) | ✓ | |
Generate API request string | ✓ |
Roles on Division (Level 2)
This role on a Division can do the following | V | C | E | M |
Create a division (admins only) | ||||
Delete a division | ✓ | |||
Edit a division | ✓ | ✓ | ||
Set or change the default bundle settings for the division | ✓ | ✓ | ||
Set or change the default c-layer settings for the division | ✓ | ✓ | ||
View all the programs in the division | ✓ | ✓ | ✓ | ✓ |
View outcome mappings on the division (right panel) | ✓ | ✓ | ✓ | ✓ |
See who is on the division team (access) | ✓ | ✓ | ✓ | |
Add team members to the division team (access) | ✓ | |||
Make a team member a manager of program (access) | ✓ | |||
Create and edit division outcome Sets (DOS) | ✓ | |||
Create a program in the division | ✓ | ✓ | ||
Create and edit division level mapping cascades | ✓ | |||
Map to division level mapping cascades | ✓ | ✓ | ||
Edit any program in the division | ✓ | ✓ | ||
Delete a program from the division | ✓ | |||
Generate API request string (only admins can do this) | ||||
Run reports | ✓ | ✓ | ✓ | ✓ |
Roles on Program (Level 3)
This role on a program can do the following | V | C | E | M |
Set or change the default bundle settings for the program | ✓ | ✓ | ||
Set or change the default c-layer settings for the program | ✓ | ✓ | ||
View all the courses in the program | ✓ | ✓ | ✓ | ✓ |
View outcome mappings on the program (right panel) | ✓ | ✓ | ✓ | ✓ |
View activities on any course in the program | ✓ | ✓ | ✓ | ✓ |
View suggestions (tuning) for all courses in the program | ✓ | ✓ | ✓ | |
Create suggestions on any course in the program | ✓ | ✓ | ✓ | |
Participate in discussions for any course in the program |
✓ | ✓ | ✓ | |
Change the status of a suggestion from status panel | ✓ | |||
Complete task in task list | ✓ | ✓ | ||
See who is on the program team (access) | ✓ | ✓ | ✓ | |
Add team members to the program team (access) | ✓ | |||
Make a team member a viewer, commenter or editor of program (access) | ✓ | |||
Make a team member a manager on course(s) in program (access) | ✓ | |||
Create a course in the program (access) | ✓ | ✓ | ||
Edit any course in the program | ✓ | ✓ | ||
Delete a course from the program | ✓ | ✓ | ||
Map any course in the program folder to available outcome sets* | ✓ | ✓ | ||
Create and edit program outcome Sets (POS) | ✓ | |||
Create and edit course outcome Sets (COS) | ✓ | ✓ | ||
Create program level mapping cascades | ✓ | |||
Map to program level mapping cascades | ✓ | ✓ | ||
Generate API request string (only admins can do this) | ||||
Run reports | ✓ | ✓ | ✓ | ✓ |
Run custom program reports | ✓ | ✓ |
*Some mapping access may be limited due to source course and proxy course mapping rules. See roles on a proxy course below. Here are articles for further reading.
Roles on the Course (Level 4)
When someone is a commenter, editor, or manager on one or more courses, they will automatically have limited view rights at the program level so that they can navigate to the course.
This role on Course (Level 4) can do the following | V | C | E | M |
Change the bundle settings for the course | ✓ | ✓ | ||
Change the c-layer settings for the course | ✓ | ✓ | ||
View the course from the program |
✓ | ✓ | ✓ | ✓ |
View the course from the course level | ✓ | ✓ | ✓ | ✓ |
View outcome mappings (right panel) for the course | ✓ | ✓ | ✓ | ✓ |
View learning and assessment activities for the course | ✓ | ✓ | ✓ | ✓ |
View suggestions (tuning) for the course | ✓ | ✓ | ✓ | |
Create suggestions on the course | ✓ | ✓ | ✓ | |
Participate in discussions for the course | ✓ | ✓ | ✓ | |
Change the status of a suggestion (e.g. closed, planned) | ✓ | |||
View the course task list | ✓ | ✓ | ✓ | |
Add items to the course task list | ✓ | ✓ | ||
Check items off the course task list | ✓ | ✓ | ||
See who is on the course team (access) | ✓ | ✓ | ✓ | |
Add team members to the course team (access) | ✓ | |||
Make a team member a viewer, commenter or editor of course | ✓ | |||
Edit the course | ✓ | ✓ | ||
Delete the course | ✓ | ✓ | ||
Map the course to all available outcome sets* | ✓ | ✓ | ||
Create and edit course outcome sets (COS) | ✓ | ✓ | ||
Create and edit course level mapping cascades | ✓ | |||
Can map to a course level mapping cascade | ✓ | ✓ | ||
Run reports | ✓ | ✓ | ✓ | ✓ |
Run custom reports | ✓ | ✓ | ||
Create a course archive | ✓ | |||
Generate API request string (only admins can do this) |
*Some mapping access may be limited due to source course and proxy course mapping rules. See roles on a proxy course below. Here are articles for further reading.
Roles on a Proxy Course (level-4 object)
On proxy courses, editors and managers have reduced roles (designated with E-pr and M-pr). A manager or editor in the source course maintains normal role definitions (see chart above for roles in a source course). The reduced roles are indicated with "no" in the chart.
Note: Admins in a proxy course view the course as the highest-role user (the M-pr role). An admin can go to the source course to gain full permissions.
This role at Course (level 4) can do the following on a proxy course | V | C | E-pr | M-pr |
Change the bundle settings for the course | no | no | ||
Change the c-layer settings for the course | no | no | ||
View the course from the program | ✓ | ✓ | ✓ | ✓ |
View the course from course level | ✓ | ✓ | ✓ | ✓ |
View outcome mappings (right panel) for the course | ✓ | ✓ | ✓ | ✓ |
View learning and assessment activities for the course | ✓ | ✓ | ✓ | ✓ |
View suggestions (tuning) for the course | ✓ | ✓ | ✓ | |
Create suggestions on the course | ✓ | ✓ | ✓ | |
Participate in discussions for the course | ✓ | ✓ | ✓ | |
Change the status of a suggestion (e.g. closed, planned) | no | |||
View the course task list | ✓ | ✓ | ✓ | |
Add items to the course task list | no | no | ||
Check items off the course task list | no | no | ||
See who is on the course team (access) | ✓ | ✓ | ✓ | |
Change who is on the proxy course team | ✓ | |||
Edit the course | no | no | ||
Delete the proxy (but not the source)** | ✓ | |||
Map the proxy to a course outcome set (COS) | ✓ | ✓ | ||
Map the proxy to a course level mapping cascade | ✓ | ✓ | ||
Map the proxy to program outcome sets (POS) | ✓ | ✓ | ||
Map the proxy to a program level mapping cascade | ✓ | ✓ | ||
Map the proxy to division outcome sets (DOS)* | ✓ | ✓ | ||
Map the proxy to a division level mapping cascade* | ✓ | ✓ | ||
Map the proxy to an institution outcome set (IOS) | no | no | ||
Map the proxy to an institution level mapping cascade*** | no | no | ||
Run reports | ✓ | ✓ | ✓ | ✓ |
Run custom reports | ✓ | ✓ | ||
Generate API request string (only admins can do this) |
*E-pr and M-pr can only map a proxy course to a division outcome set when the proxy is located in a different division than the source course. This way, your division mappings on the source courses cannot be changed by other groups. This rule applies to mapping cascades, as well.
** A manager of the program containing the proxy course can delete the proxy course
*** An institution level outcome/suboutcome cannot be an anchor, only part of a cascade from a lower level outcome set. Therefore there is no such thing as an institution level mapping cascade.
Comments
0 comments
Article is closed for comments.