Celebrate Excellence in Education: Nominate Outstanding Educators by April 15!
Found this content helpful? Log in or sign up to leave a like!
Looking to discuss this feature from the 2022-04-27 Release Notes? Post a reply and start a conversation!
ADD FEEDBACK FOR THIS FEATURE IN Q&A TOPIC
- This topic is for feature discussion only—Please share use cases, best practices, questions, clarifications, etc. regarding this feature.
- Please thread replies as possible to keep posts organized. This will help everyone to track discussions and to participate.
ADDITIONAL FEEDBACK—WHERE TO POST IDEA SUGGESTIONS AND SUBMIT BUG REPORTS
- Idea requests for the Product Team to consider should be submitted in ideas.canvaslms.com. This is the best way to ask for additional or alternative functionality than what is included in the release. Linking to the related idea here so others can find it is encouraged!
- Bug reports should be submitted to Canvas Support. This way, cases can be connected and uniform updates can be provided to those involved. Bugs will not be triaged in this thread.
Is this setting being on/off only relevant to courses built with MasteryPaths? For instance, is it safe to enable this setting for all courses in an account without effecting non-MasteryPaths courses? For ones already built with MasteryPath, what does this setting affect?
Thanks!
This update does not change any functionality for Mastery Paths. It only moves it from a "Feature Option" to a "Setting" for consistency with the intended use of "Feature Options".
@dlyonsCould you please clarify what the behaviour of checking each one of these boxes actually is as the language is not clear?
If 'Mastery Paths' is unchecked, does that mean that no course within the sub-account can use it?
What if it is checked?
Depending on what it actually does, I'd suggest changing the wording of the setting so that it is clearer in its impact and consistent with the other settings, for example:
Disable comments on announcements
Copyright and license information must be provided for files before they are published.
Thank you
The behavior currently in production is slightly erroneous but the description is the correct behavior (engineers are already working on correcting the observed behavior in prod.) The expected behavior is:
To participate in the Instructure Community, you need to sign up or log in:
Sign In