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

[cms_hickss]

Please change each the "Moderate discussions ( delete / edit other's posts, lock topics)" from a single setting to three separate settings.

Current:

Moderate discussions ( delete / edit other's posts, lock topics)

Should become:

• Lock Topics in Discussions
• Allow Edit Other's Posts in Discussions
• Delete Discussion Posts

One reason for this request:

This would allow you to set TAs (or other roles) to having only the permissions needed for that role instead of none of them or all of them. For example, the ability to only edit other's post but not delete a post in discussions.

Per Cosme Salazar in More granular permissions for admins and In Permissions, Change "ADD, EDIT, and DELETE" into Three Separate Settings I have divided out the multiple functionality settings into their own requests. There are now 10 separate requests.

Comments from Instructure

We have exciting news about the first phase of the Priority: Granular Permissions‌.  The New User Interface is included in the Canvas Production Release Notes (2018-07-14) .  Go check it out!

[allison]

 @nealc62 ​, I have a follow-up question to your use case of students moderating class discussions. Does that mean that for one discussion and one discussion only, you would like to set a student as a "Discussion Leader"? Or is this more like a TA where you have a permission set that persists throughout the course?

[nealc62]

Hi Allison, We use both instructor-led discussions along and student-led discussions. Each student in the course is required to lead at least one class discussion. It a course assignment for which they are evaluated, so it is not a TA role.

This brings up another issue of needing to be able to have more than one grading rubric on a discussion. As it is now, a discussion participation rubric is linked to the student-led discussion and an assignment with no submission is created with a leadership rubric linked to it for grading the student moderators.

Thanks for your question!

[allison]

Thanks,  @nealc62 ​. I will tuck this idea away for future work on Discussions, especially the idea of supporting more elaborate workflows where a Discussion Leader can be assessed separately from other students replying to the thread. As far as the permissions go, I'd like to point you to this page, where we are beginning the process of gathering permission granularity requests:  Canvas Permissions and Granularity Feature Ideas This request will be considered with all of the others this summer as we do a deep dive into Permissions.

[millerjm]

We need some support for our case that the permissions available in Canvas are not sufficient for our needs.  Above is the update that Allison Weiss posted to many of our feature ideas.  She is asking for use cases for granularity and we really need to justify each and every one.  I made a document to track discussions and feature ideas related to permissions: 

Canvas Permissions and Granularity Feature Ideas

This is the sort of information that would assist in getting these changes made during this permissions audit.  This information would need to be added as comments to the individual feature ideas, and if it needs to be pasted to more than one, then please do that.  I know it's tiresome to post the same thing again and again, even though someone else has already done it, but they need to see that it's not just 5 people with these issues!  We haven't gotten much traction because we haven't had enough use cases posted but my document above seems to have gotten some attention.

• What has the current user permissions "bundling" and lack of granularity cost you in terms of support and functionality?
• What permissions have you HAD to grant to someone simply to allow them to be able to do their job, that you would have rather NOT given?
• What permissions have you had to DENY giving someone because it gave them access to something that you could not due to security, concern about causing trouble, etc.?
• What other qualms do you have about things?
• What things have cost you more in staff hours because of denying access to someone, means that your department had to research, do work, etc, on behalf of a user that would have been able to do their work if the permissions were granular?

Thank you!

Joni

I'm also tagging  @kona ​ and cms_hickss​  since they have been so involved in getting attention to these feature ideas. 

[Renee_Carney]

Greetings, Partners on Permissions

Thank you for the time, energy, experience, and knowledge you have put into these threads.  The granulated permissions threads have been open and gathering information for almost a year now.  This extra time has allowed our team to collect important feedback and perspectives.  Each of the permissions threads contain valuable stories that will help inform development if/when a project is allocated for.  Having worked with Allison on these, and now working with Matt G., I know that the product team is sincerely interested in improving permissions, however the magnitude and impact of such a project does not make it one that is easy to squeeze in.  We will be archiving these permissions threads for now.  Archiving these threads does not mean they are forgotten; they are set aside, while they are inactive projects on our roadmap.  The ideas are monitored, so you can continue to add your examples and use cases to the dialogue.  Please follow this thread to receive updates when they are available.

Again, thank you for the rich conversation!

[Renee_Carney]

  Idea is currently in Product Radar Learn more about this stage...

[meichin]

I would like to add to this to separate the permission: Discussions - moderate from the permission to post announcements.  Announcements are almost never graded, but discussions can be.  There are user roles that I would like to add where all they can do is observe but also post announcements - for tutoring purposes - but I don't want them to be able do add/edit/delete/lock discussions!  Thanks for listening!

[Renee_Carney]

The Radar idea stage has been removed from the Feature Idea Process.  You can read more about why in the blog post Adaptation: Feature Idea Process Changes.

This change will only impact the stage sort of this idea and will not change how it is voted on or how it is considered during prioritization activities.  This change will streamline the list of ideas 'open for voting', making it easier for you to see the true top voted ideas in one sort, here.

[cms_hickss]

For this idea, please also remember to follow:

• Priority: Granular Permissions 
• Canvas Permissions and Granularity Feature Ideas 

The first step to getting Granular Permissions was completed with the Permissions: New Interface.

[JacquiChan]

You've got my vote on this.