This document explains how to integrate Bodyswaps into a third party Learner Management or Learner Experience Systems (referred to as LMS’s from here-on).
There are a myriad of LMS solutions on the market and so whilst its not possible to support every system, we have created an integration route via the LTI1.3 standard which is supported by a large number of the LMSs.
Note: Unlike many web based eLearning applications Bodyswaps cannot actually be hosted inside an LMS - i.e. there are not application files that can be uploaded to host LMS. The Bodyswaps is a separate app that must be either installed on the target device via one of our recommended methods or we can stream Bodyswaps in the browser from our website. Please ask our team for details on this latter option.
Learning Tools Interoperability (LTI): Developed by the IMS Global Learning Consortium, LTI is a standard that allows third-party learning applications to integrate seamlessly into LMSs. LTI provides a framework for the LMS to send user, role, and course information to the third-party tool, and for the tool to send grade data back to the LMS. It's widely supported by many LMSs, making it a versatile choice for integration.
Configuration steps
LTI must be configured on both the LMS and Bodyswaps in order to connect.
These steps will vary between LMS’s, where we have already performed integrations we have LMS specific notes that can be shared with you.
1. Add Bodyswaps as an external tool
Bodyswaps must be added as an ‘External Tool’ to your LMS and configured using the following options:
Once this is registered locate your tool configuration details that should contain:
Authentication request URL You’ll need to enter these into Bodyswaps Go in the next step.
2. Register your LMS to Bodyswaps Go
Login to Bodyswaps Go as an administrator and navigate to the Integrations Tab
Here you can see any integrations that you’ve previously registered or click CREATE to create a new one.
Here you should fill out the following details:
Click SAVE at the end.
3. Register our public key
Click on the Copy Public Key button at the bottom of the settings section of the integrations page.
You will then need to paste this back into the Public Key field on your LMS.
Bodyswaps is now configured! Next step is to add it to a course.
Note
If the tool doesn't support pasting the Public Key in directly, please ensure you have set the tool up to use the jwks endpoint in the previous step.
4. Add a Bodyswaps activity to your course
Create a course in your LMS, add an activity or resource and add Bodyswaps as an External Tool.
Give the activity a name and select your preconfigured tool - in this case Bodyswaps (or the name you picked in Stage 1)
Bodyswaps has a large selection of modules so we need to select which module we want the learners to access. This is managed in the Manage Course Content page in the Integrations.
You can set a default module(s), which is the fallback set for all integrations used by the tool, if there is not a specific configuration set for that course.
Do this by using the Select Modules field at the top to select one ore more modules. Assigned modules will be displayed in the Modules Assigned section underneath.
Please ensure you save any changes when you’ve finished selecting the modules.
If you want to override the default set for a specific course you can do this in one of two ways:
Add a course specific module set
Click on the Add Course button and copy and paste the exact course name into the Course Name field. Use the Select Modules drop down to select the courses that will be displayed in that specific course.
This is the recommended approach.
Use custom parameters
On some LMS’s when you add the tool to your course, you have the option to pass custom parameters which can tell Bodyswaps which module and language to launch content in. This will be called Custom Params or similar. The syntax looks as follows:
You will need a specific module ID when using this method. Please ask Bodyswaps for the module ID for specific module you’d like.
Compatibility
LMS integration is a new feature and we are unable to test with every LTI1.3 compatible LMS out there - where possible we will keep the below table updated with which systems LMS integration has been tested with and any issues.