In this article, we looked at integrating your Storyflow training with your LMS. Now we will discuss the benefits of integrating Single Sign On ("SSO") and LMS.

Quick Links

Workflow Compared to “Author Workflow with an LMS (no SSO)”

If you compare the workflows for with or without SSO, the steps for Adding Learners is removed when you add the SSO integration:

Open

See the Workflow Steps at the bottom of this article.

One of the primary advantages of using SSO is the LMS integration. When both the Motive
Training Platform and the LMS use the same login provider, credentials can be passed from
one system to the other without additional logins, passwords, and user configuration for
new learners. That flow is described in more detail below.

Integration Benefits

● Same process to assign VR modules to learners as other e-learning
● Seamless learner experience - no cumbersome username and password
● Secure single sign-on
● Manage modules in your LMS
● Completion data flows back to LMS automatically

Integration Requirements

● SSO - OIDC or OAuth
● LMS - SCORM 1.2, SCORM 2004 or xAPI

Flow for Launching from an LMS with SSO configured

Assumptions

● Learner does not have a Motive account.
● Learning Manager has generated an XAPI or SCORM compliant package and has
uploaded it into an LMS
● SSO has been configured to use the same provider as the LMS
● SSO is configured as a trusted authority to create Learners
● Headset has been provisioned to communicate with the proper Launch Server and
Workspace

Flow

1. Learner logs into LMS using SSO and launches a course

2. LMS opens Launch Code screen

3. Launch detects that this is a new learner for the organization who is currently logged in
   using SSO

4. Launch creates a new user record

5. Launch displays Launch Code

Motive LMS Integration

The Motive Training Platform integrates with Learning Management Systems (LMS) that
support any of the following standards:
● SCORM 1.2
● SCORM 2004
● xAPI

Workflow Steps

Configuring your SSO

Before you use the SSO integration there are two steps that must be completed the first time to set this up:

A. Configure the SSO with Motive Hub by following these steps

B. Set up the SSO configuration in your LMS (contact your LMS provider for steps)

Step 1: Publish the Scenario with a Completion Resource into a Bundle

Permission Required: Storyflow Organization Member or Admin

1. Add a Completion Resource to the Scenario

2. Publish the Scenario. By default it is “Draft”. Click on it to open it and change the Status and save

Step 2: Deploy the Bundle

Permission Required: Storyflow Organization Member or Admin

3. Go to the Bundles Tab

4. Give your Bundle a name that clearly identifies it

5. Click Publish. You will then see it listed

6. Choose Deploy. This automatically sends the Bundle to Launch for us as Content

Step 3: Export Module to LMS

Permission Required: Launch Organization Member or Admin

7. Open Launch

8. Go to Modules. Here we will create a module from the Content we just created.

9. Select Create Module

10. Give the Module a title

11. Optional: add a Description

12. Optional: add an image – the learner will see this in their learner view

13. Under Content, Choose the bundle you just uploaded by clicking on the dropdown arrow and choosing it from the list

14. Choose the specific scenarios to be included in this Module

15. Under LRS communication method – leave the default Communicate with an LRS via Launch

16. Click Create

After you create the Module, you’ll see it in a list on the Module screen.

17. Click the Download Content button

18. Choose the export file type (refer to your LMS’ instructions)

19. Navigate to your LMS and import the file per their instructions

Step 4: Provision Devices

Permission Required: Launch Organization Member or Admin

Note: This step can be done anytime after Step 1 but must be done before the learner can launch training

In order to provision the devices, you or another individual must have physical access to all the headsets. There are a few types of scenarios that could happen here:

Open

First, let’s look at a Learning Manager that has physical access to all the headsets.

20. Open Launch

21. On the left hand side go to Devices

22. Then click on Provision New Device

23. Note there is a User Code field – you’ll fill it out in a moment

24. Put on your headset and open the APK

25. You’ll see the screen for Device Authentication

26. Click Connect:

     

27. You’ll see the Authentication Number – you’ll need this in a moment.

28. Open Launch on your computer

29. Enter the Authentication Number in the User Code field:

30. Click Submit

31. Refresh to see the new device added

Back in the headset after you’ve completed the Device Authentication, the next screen will be the Launch Experience:

The next time this headset it logged into and the APK launched, it will go straight to the Launch Code screen. You only need to provision this particular device the one time.

If we look at our example again where the Learning Manager does not have physical access to the devices, then you would follow these steps:

You need to complete all of these steps together in one session. If the individual logs out of the headset, before you provision the device, then the next time they go to log in you would have to do this again.

Step 5: Learner Logs into LMS

These steps are completed by the learner.

32. Log into the LMS and start the course

33. See a popup with the Launch Code

34. Don the headset and open the APK

35. Enter the 6 digit code into the screen in the headset that was generated in the LMS

36. Complete the training and then quit

All other Learners would also complete these steps individually and complete their training in the VR headset.

Step 6: View Session Data

Permission Required: Launch Organization Member or Admin

37. Open Launch

38. Go to Sessions and see data

You can also view your own data in your LMS.

Related Articles

Launch: An Overview

Deliver Training: Author Workflow with an LMS (no SSO)

Deliver Training: Author Workflow without an LMS