By default Launch Pad works with Motive’s hosted offering. You need to provision Launch Pad to work with your organization.

You can simplify this process by deploying an AppConfig.json file to your headset via MDM by following these steps. This process also allows you to direct Launch Pad to communicate with your self-hosted or private cloud offering.

1. Configure your AppConfig.json file

Download this template to get started.

Fill out the following fields. Note that optional fields can be removed.

Field	Description

Field	Description
CLUSTER NAME	This is the system name of the cluster, usually part of the cluster domain name. E.g. “us-west-a”.
CLUSTER TITLE	This is the user-facing title for the cluster. Note that this is part of a “localizedTitle” array, you can add localizations for other languages.
URL OF CLOUD INSTALL	The URL of the cluster, e.g. https://us-west-a.motivecloud.dev
OPTIONAL-URL OF IDENTITY SERVER	Only required for multi-cluster installs with a shared identity server. E.g. https://us-west-a.motivecloud.dev
OPTIONAL-CLIENT ID	Along with Client Secret, allows Launch Pad to connect directly to your organization to launch content using a Launch Code.
OPTIONAL-CLIENT SECRET	Works with Client Secret.
OPTIONAL-YOUR ORGANIZATION IDENTIFIER	If set, will bypass the organization select screen for the login flow.
OPTIONAL-DEFAULT CLUSTER	If multiple clusters are defined, this sets the default cluster that Launch Pad will use.

This is an example of AppConfig.json for the hosted Motive Cloud offering. This shows a multi-cluster configuration.

{
	"clusters": [
		{
			"localizedTitle": {
				"localizations": [
					{
						"cultureCode": "en",
						"text": "US West"
					}
				]
			},
			"motiveCloudConfig": {
				"url": "https://us-west-a.motivecloud.dev",
				"identityUrl": "https://us-west-a.motivecloud.dev"
			},
			"name": "us-west-a"
		},
		{
			"localizedTitle": {
				"localizations": [
					{
						"cultureCode": "en",
						"text": "Canada Central"
					}
				]
			},
			"motiveCloudConfig": {
				"url": "https://ca-central-a.az.motivecloud.dev",
				"identityUrl": "https://us-west-a.motivecloud.dev"
			},
			"name": "ca-central-a"
		}
	]
}

2 Deploy the AppConfig.json

2a) Via MDM

2b) Directly Upload to Headset

App configs may optionally be directly uploaded to a headset.
We recommend using SideQuest for doing this.

Add the AppConfig.json in one of two locations:

The app data folder (Android > data > packagename > files), or
The obb folder (Android > obb > packagename)

If using SideQuest you may use the FileManager built into the tool to do this. It will start at the /sdcard path so navigate to the given folder and add the file. See the image below for reference.

Configuring Launch Pad via MDM

1. Configure your AppConfig.json file

2 Deploy the AppConfig.json

2a) Via MDM

Quest for Business

ManageXR

ArborXR

2b) Directly Upload to Headset