The examples in this article were created for a fictional company, Lakeview Inc.

Quick Links

About Launch

Once your content is created in Storyflow, you can use Launch to determine who gets the content, how they get it, and the format it is delivered in. Launch provides VR content management functionality for you to seamlessly roll out your immersive training.

Generally, Launch is used to:

• Create content bundles and configurations from Storyflow and control how that content is deployed.

• Manage learner profiles.

• View session data from training sessions.

• Manage devices. 

Launch Permissions

There are permissions specific to Launch and you can learn about them, and grant them, using this article.

Accessing Launch

In order for you to access Launch, there are 3 things required:

1. Your Organization must have at least one Launch Space:

As a company, you have one instance of Launch. Within that instance, you can have several Organizations (though this may not be typical) and within each Organization, you can have distinct Spaces – we call them “Launch Spaces”. Organizations could represent different business units, training teams, or departments in a company. Many companies will only have one Organization.

A Launch Space is created by an individual with the Launch Organization Admin permission. We have step by step instructions in the Admin Essentials Pathway in Motive Academy or you can refer to these steps.

2. You must have either the Launch Organization Admin or Member Permission:

An Admin at your company with the Identity Organization Admin Permission must assign you one of the Launch permissions. Your Admin can refer to the step by step instructions in the Admin Essentials Pathway in Motive Academy or these instructions.

3. You must be added as a Collaborator to the Launch Space you wish to access:

As mentioned above in the first item, you must have at least one Launch Space, though your Organization can have more than one. After receiving the Organizational level permission, an individual with the Launch Organization Admin permission must assign you as a Collaborator to the space. Your Admin can refer to the step by step instructions in the Admin Essentials Pathway in Motive Academy or these instructions..

Once you have all three of the above, you can log into Launch!

Log into Launch

1. Log into Motive at https://cloud.motive.io/

2. Click on “Launch”:

Once you are in the Launch on the left hand side of the screen, you will find any Launch Spaces that have been created. When you click the arrow to the right of the space:

Then the menu for that space will open up:

If you do NOT see a Launch Space, like this example:

then an individual with the Launch Organization Admin Permission at your Organization needs to first create a Launch Space.

We have instructions on creating a Launch Space here, and this is part of the Admin Essentials Pathway in Motive Academy.

Delivering Training

Using Launch you can deliver your VR training. Click here to learn more.

Anatomy of Launch Screen

1. Organization: This is the dropdown that allows you to view the Launch Space for this Organization.

2. Home: This area provides a dashboard of your Launch area. For more info, click here.

Space Details: You can set up one or several Organizations in Launch. If your company has different departments that you want to separate, you can create more than one organization to which you can assign people with certain permissions.

Training Overview: Quickly see the number of learners in the space and how many sessions have been completed. Use the View Sessions/Learners link to jump to that area of Launch.

Collaborators: Individuals who have created the training or have permission to do so. Learners are not listed here – you can find them in the Learners section.

3. Modules: In this area you can see and create modules from uploaded Storyflow content. You will then use these Modules to distribute training to learners. For more info, click here.

4. Content: Content from Storyflow can be uploaded here and must be done before you can create a Module. For more info, click here.

5. Launchers: Launchers allow learners to connect to the learning. With a [Module] created, you can create a launcher. A launcher connects the [Module] to a 5 digit launch code. When the launch code is used to launch the training module in the headset, the data collected is connected to the learner specified in the launcher. Note that you would only use this feature if you were NOT connecting to an LMS.
For more info, click here.

6. LRS Credentials: If you have an external LRS service that you would like to use, you can set up your LRS credentials by navigating to this area. Choose Create Credentials and complete the fields. The information will be available through your LRS service. For more info, click here.

7. Sessions Overview: This provides an overview of training sessions completed by learners in Dashboard form.

8. Scenarios: This area allows you to break down analytics by scenario. When you choose a scenario you are then able to view stats such as number of pass/fail, or time in scenario, and more. For more info, click here.

9. Sessions: A more detailed look at learner sessions. Any Storyflow test assessments added via Resources will be able to be viewed here. XAPI statements are captured and you can see what the learner looked at, pointed at, experienced and more. If LRS Credentials have been added and the LRS Credentials have been added to a Module, then all Session data will be available in the LRS. For more info, click here.

10. Collaborators: While a list of collaborators can be seen by both Admin and Members in the Home area, the Collaborators area can only been seen with the permission Launch Organization Admin. This is where an admin will view and manage collaborators in the space. For more info, click here.

11. Applications: This feature works in conjunction with Launch Pad allows you to set up a configuration that will give you a code to launch a whole app from launchpad. You can find more information on this topic in the following articles: Using Launch Pad to Launch Apps and Configuring a Launch Module for LSDK.

12. WebGL: If you have a WebGL version of your training app (training done in browser) it can be configured here. Then you can associate it with a Module. Speak to Motive staff if you have further questions on this topic. For more info, click here.

13. Learners: In this area you can view learners and drill down to see their training sessions and device logs. For more info, click here.

14. Learner Groups: A group of learners that can be quickly added to other areas of the Motive Platform, instead of adding learners all individually. For more info, click here.

15. Devices: VR Headsets (Devices) are provisioned within Launch. For a given device you can see the errors, warnings, and debug statements as training is in session. Click on the View Details button next to the device name. This is very helpful information to send Motive staff when a support ticket is created to assist with resolving issues on the developer side. For more information, click here.

Admin: In this area, Admins can see and edit Launch Spaces. For more information, click here.