ADMINS: Need more comments for the Permissions Granularity feature ideas

[millerjm]

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. 

" modifiedtitle="true" title="In Permissions, Separate "Manage (add/edit/delete) assignments and qui...

(Looks like this one was archived)

Here is some history on these feature ideas: 

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

" style="color: #2989c5;

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

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 cms_hickss​ for posting all of these, and to  @kona  for starting this discussion back in May.   

Joni

[cms_hickss]

This one:

In Permissions, Separate "Create and edit assessing rubrics" into 2 permissions​

hasn't been "archived" Archived as it wasn't Panda-Catted. They use Archive to also represent that it's an Idea they are looking at but not for this quarter/half what have you.