Allow Inherited LTI 1.3 Developer Key Placements to be toggled

[tcs1]

Inherited LTI keys are nice because there's no need to manage LTI configuration settings. However, there is no way to manage whether individual placements are enabled or disabled.

One glaring example of this is the "show by default" Course Navigation placement setting. If the inherited key has a Course Placement, it will be shown by default in all courses under the sub-account where it is deployed. Instructors would have to manually disable the link (opt-out), potentially causing much confusion and gnashing of teeth. This is not ideal, especially for large institutions.

We'd like a way to have "placement enabled/disabled" switches available for tools that use inherited LTI keys. For LTI 1.1 placements, those switches are available per-deployment, but that option is not possible for LTI 1.3 tools.

[Stef_retired]

@tcs1 

Thanks for sharing this. This request, along with being able to view the configuration details, is already on our partnership team's radar for key management feature enhancements.

[derek_moore]

Are we talking about the "Placement" setting on the App?  Or are we talking about the XML?:

<lticm:property name="text">Attendance</lticm:property>

<lticm:property name="visibility">public</lticm:property>

<lticm:property name="default">enabled/disabled</lticm:property>