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

[cms_hickss]

This idea has been developed and deployed to Canvas

---

Please change each the "Add/remove students for the course" from a single setting to two separate settings.

Current:

Add/remove students for the course

Should become:

• Add students to a course
• Remove students from a course

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.

[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...

[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 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.

[m_d_suijkerbuij]

This permission also includes adding and removing students in sections. 

This activity is essential for our teachers, but they are not allowed to add students to courses, since this needs to be in sync with our SIS. 

It would be useful if the permission for 'Adding students to sections' can be separate, so we can only enable that permission and disable the 'adding/removing students in courses' permission for our teachers and they are not able to add students to courses anymore. 

[dbrace]

I see that a permission for an "inactive" student enrollment status was requested.  I would be in favor of that.

Something else to consider is how any of these permissions (specifically "active", "delete", and maybe "inactive") will relate to SIS/CSV/API enrollments.

Will this functionality be "sticky" and override what happens from SIS/CSV/API enrollments?

[Stef_retired]

Comments from Instructure

The Add/Remove Teachers, Designers, TAs permission and the Add/Remove Students permission have been reorganized into individual user permissions. This change provides granularity among the options to manage users.

For more information, please read through the  Canvas Release Notes (2021-03-20).