LTI 1.1 to LTI 1.3 Advantage Transition Guides

For schools using the LTI 1.1 versions of Qwickly product looking to transition to LTI 1.3.  The articles linked below detail transitioning Qwickly products from LTI 1.1 to LTI 1.3 Advantage.

To check if the current installation is LTI 1.3, login to the qwickly.tools dashboard and follow these steps:

• Click on the "Instance Keys" button under your Instance's name (screenshot below)
• This will open a pop-up menu that will store any LTI 1.3 keys needed for Qwickly's apps to work on the LMS. This menu will allow you to select a Qwickly product, and will have required fields for the 1.3 installation (such as Deployment IDs). Please confirm that you've entered the required keys for any Product to make sure you're set up to use the LTI 1.3 tool.

	D2L Brightspace - Transitioning Qwickly Attendance to LTI 1.3 Advantage Qwickly Course Tools is already LTI 1.3 Advantage (this product has always been a LTI 1.3 launch and no update is required) Qwickly Jot (coming soon) will be LTI 1.3 Advantage (this product will be a LTI 1.3 launch upon initial release and no update will be required) Note: For Brightspace, both LTI 1.1 and 1.3 installations can be on the system concurrently.  We always recommend testing your deployments on your LMS staging server.
	Blackboard Learn - Transitioning Qwickly Attendance, Course Tools, and Jot to LTI 1.3 Advantage Note: For Blackboard Learn, this process will move all licensed Qwickly products (Qwickly Attendance, Qwickly Course Tools, & Qwickly Jot) from LTI 1.1 to LTI 1.3 at the same time.  Both LTI installations can NOT be on the system concurrently. This means those using multiple products need to transition all products to LTI 1.3 simultaneously. We always recommend testing your deployments on your LMS staging server.
	Canvas - Transitioning Qwickly Attendance Canvas - Transitioning Qwickly Course Tools Canvas - Transitioning Qwickly Jot Note: For Canvas, both LTI 1.1 and 1.3 installations can be on the system concurrently.  We always recommend testing your deployments on your LMS staging server.