***This feature was delayed in the production environment. The new go-live date is February 21.
Release notes
What is this update about?
This update enables more centralized control in Canvas Apps, streamlining app deployment and management- saving time and improving visibility into where apps are available.
- This update allows admin to have the ability to deploy an app with a shared deployment ID across the root account, enabling forced activation for all courses.
- Includes an updated review page to replace the current modal view that will enable admins to view and edit details about their apps.
- Enables users to make an app available in specific sub-accounts or courses.
When will this go to GA?
This feature will be generally available on February 21. The feature flag can be enabled in production on individual instances at any time, so if you want to use it in production please reach out and we’ll be happy to get it enabled for you!
If an app is set to ‘Not Available’ in a context, can it be launched there?
No, if an app is set as ‘Not Available’ in a specific context, it will not be able to be launched from it, even if a resource created with that app is already present. Canvas will act as if the tool is not installed when in that sub-account or course.
Will this allow me to set different configurations (especially placements) in different sub-accounts and courses?
At this time we are only supporting entirely enabling or disabling a tool in a sub-account or course. We are evaluating the feasibility of enabling customization of certain configuration settings at the sub-account or course level, but do not have a timeline for this feature.
