| Idea is currently in Product Radar Learn more about this stage...|
| Idea open for vote Wed. July 6, 2016 - Wed. October 5, 2016 Learn more about voting...|
The June 12 release of Canvas Commons (Commons Release Notes (2016-06-12) replaced the previous subaccount-based sharing permissions structure with a new "Groups" model. These Groups require manual management, either by a campus administrator or an individual designated as a Group Manager.
The previous subaccount-based sharing model allowed instructors to more dynamically share resources with their departmental colleagues without any need to identify and individually designate each one as a group member. At an institution as large as ours, with over 40,000 active Canvas users, manually managing groups quickly becomes an unsustainable process.
Although the new groups model provides some useful ways to support cross-departmental collaboration and resource sharing, removing the ability to dynamically restrict access to Commons resources by subaccount is overall a significant downgrade to Commons' usability and functionality. The subaccount-level sharing should be reinstated, complementing the new option to manually create and manage Commons groups.
| Comments from Instructure|
July 2016 Update by Kate McGee
I want to thank you all for sharing your feedback on this functionality request. Anytime we build new features into our products our aim is to improve your experience. It's clear from your comments that while groups added increased flexibility for inter-institutional sharing, removing sub-account functionality has been detrimental to the sharing process. I also appreciate the comments on hierarchical structure of sub-accounts in Commons. We are gathering information on this request so please continue to share your use cases of how your institution is sharing resources. Thank you again for your passion for our products!