Joni Miller

ADMINS:  Need more comments for the Permissions Granularity feature ideas

Discussion created by Joni Miller Expert on Jan 28, 2016

Hello Canvas Admins! 

 

Please post use cases and other documentation in each of these features if you can in order to help justify these requests. 

 

In Permissions, Separate "Add/remove other teachers, course designers, TAs, and Observers to the course" into 8 permissions

In Permissions, Change "ADD, EDIT, and DELETE" into Three Separate Settings

In Permissions, Separate "Manage (add/edit/delete) assignments and quizzes" into 3 permissions

In Permissions, Separate "Manage wiki (add/edit/delete pages)" into 3 permissions

In Permissions, Separate "Add, edit and delete events on the course calendar" into 3 permissions

In Permissions, Separate "Manage (add/edit/delete) course files" into 3 permissions

In Permissions, Separate "Manage (create/edit/delete) course sections" into 3 permissions 

In Permissions, Separate "Manage (create/edit /delete) groups" into 3 permissions

In Permissions, Separate "Moderate discussions (delete/edit other's posts, lock topics)" into 3 permissions 

In Permissions, Separate "Create and edit assessing rubrics" into 2 permissions (Looks like this one was archived)

In Permissions, Separate "Add/remove students for the course" into 2 permissions

In Permissions, Separate Manage (add/edit/delete) courses into 3 permissions

 

Here is some history on these feature ideas: 

This original feature idea was posted on May 4, 2015, got 306 votes: 

 

More granular permissions for admins

 

This one is one of the ideas that separated things out a bit more, but was archived, but has use cases and other information.

 

In Permissions, Change "ADD, EDIT, and DELETE" into Three Separate Settings

 

We were then asked to post separate feature ideas for each specific permission, so we did and now those have been out there since August 5 (see list above). 

 

Permissions is a big deal for institutions and when we have no ability to control permissions it creates a lot of extra work for admins and instructional technologists fixing what people break on accident. 

 

These permissions requests adds up to hours of work each week either cleaning up messes or not giving people access to things because the permissions are so broad that we can't give them access, which then means that the work falls back onto canvas admins or instructional technologists.  Either way, we need a better way of granting/controlling permissions for users.  JS and CS overrides do not work consistently

 

Thanks again to Susan Hicks for posting all of these, and to Kona Jones for starting this discussion back in May.   

 

Joni

Outcomes