# About

<figure><img src="/files/tHOLdPHOrdw1gxgaWvKI" alt=""><figcaption></figcaption></figure>

***

## Welcome to the MOTAR Docs!

If you are looking for more details about the **MOTAR** platform, you’ve come to the right place. **MOTAR** Docs will teach you how to spin up your own local instance of **MOTAR**, explain capabilities and features of **MOTAR**, and even help you get a license!

{% hint style="success" %}
Still wondering what **MOTAR** is? **Visit** <https://www.motar.com/> to learn more about how you can level up your organization today!
{% endhint %}

### Are you ready to get started with your own MOTAR instance?

<table data-card-size="large" data-view="cards" data-full-width="false"><thead><tr><th></th><th data-type="content-ref"></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td>Find out which <strong>license type</strong> would be best for you. </td><td><a href="/pages/tqV8Vr9F2wZxrXpxIIqe">/pages/tqV8Vr9F2wZxrXpxIIqe</a></td><td><a href="/files/5FKq3fT9SxzMEKExNju0">/files/5FKq3fT9SxzMEKExNju0</a></td></tr><tr><td>Find out which <strong>installation type</strong> would be best for you. From local installs to production ready instances.</td><td><a href="/pages/4ZrWu216oQkhsbq4nR9n">/pages/4ZrWu216oQkhsbq4nR9n</a></td><td><a href="/files/pE7W4j01HBpcYQkfgsuw">/files/pE7W4j01HBpcYQkfgsuw</a></td></tr></tbody></table>

### Do you want to learn more about the MOTAR platform?

<table data-view="cards"><thead><tr><th></th><th data-type="content-ref"></th><th data-type="content-ref"></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td>Learn more about MOTAR’s Services and the capabilities they provide.</td><td><a href="/pages/JTue8ZjFGhgRGT5YdaF9">/pages/JTue8ZjFGhgRGT5YdaF9</a></td><td></td><td><a href="/files/THwhdWYgbA676vN3wnzt">/files/THwhdWYgbA676vN3wnzt</a></td></tr><tr><td>Learn more about the hardware requirements for MOTAR.</td><td><a href="/pages/FVfN986UpddzdQbTmFF7">/pages/FVfN986UpddzdQbTmFF7</a></td><td><a href="/pages/EPZsTUdeUR1FFc6Cg0Hn">/pages/EPZsTUdeUR1FFc6Cg0Hn</a></td><td><a href="/files/Vzg3RFCRbFnszqgrjHRj">/files/Vzg3RFCRbFnszqgrjHRj</a></td></tr><tr><td>Learn more about features currently in development.</td><td><a href="/pages/TbsANnSXJYpSQKZkV9Fn">/pages/TbsANnSXJYpSQKZkV9Fn</a></td><td></td><td><a href="/files/ReQSndg0xaik1fCEGags">/files/ReQSndg0xaik1fCEGags</a></td></tr></tbody></table>

***

## Questions?

[Contact Us!](/support/contact-us) or visit our website at <https://www.motar.com/>

<figure><img src="/files/UepTTCAYOBLkKQtwOVU3" alt=""><figcaption></figcaption></figure>


# Getting Started

Select your installation type and get your license.

### Which installation type is right for you?

Choose the environment that fits your current goal. Once you select a path, we will walk you through requesting your license, downloading the necessary assets, and completing the setup.

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-type="content-ref"></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td><h4>Local Demo Install</h4></td><td><strong>Best for</strong>: Rapid evaluation and feature exploration.<br>Set up <strong>MOTAR</strong> in a local sandbox environment. We will guide you through obtaining a <strong>Discovery</strong> License and configuring a functional local instance in minutes.</td><td><a href="/pages/YOnTp6MaXucteXuRpuq9">/pages/YOnTp6MaXucteXuRpuq9</a></td><td><a href="/files/JmmQGK2WeMCWQ7Ez4B5C">/files/JmmQGK2WeMCWQ7Ez4B5C</a></td></tr><tr><td><h4>Production Ready Install</h4></td><td><strong>Best for</strong>: <strong>Enterprise</strong>-grade, scalable deployments.<br>Build a <strong>secure</strong>, scalable foundation. We’ll guide you through using your <strong>Enterprise License</strong> and preparing your production infrastructure.</td><td><a href="/pages/S60IzFFpq3l8DC4XvBLN">/pages/S60IzFFpq3l8DC4XvBLN</a></td><td><a href="/files/hfNljJ7a3a3fRU9BgDX0">/files/hfNljJ7a3a3fRU9BgDX0</a></td></tr></tbody></table>

<figure><img src="/files/ETQaU81LcQxoh9pb3LCR" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
**Note:** For details about supported features, platforms, and changes, please refer to the [Release Notes](broken://pages/f0PJFxUMqJe6DusMbhkR).
{% endhint %}

***


# Local Installation

This guide will show you how to install MOTAR on a local desktop computer for testing and demo purposes.

{% hint style="warning" %}
This installation method will install MOTAR on your local desktop computer. If you need to install MOTAR in a cloud environment or on a server, see [Production Installation](/welcome/getting-started/production-installation)
{% endhint %}

#### Start Your Local Sandbox

To begin your local **MOTAR** evaluation, you will need a **Discovery** License.

**→** I need a license: [Request Discovery License](https://www.motar.com/product-page/motar-discovery-license). *A license key will be sent to your email.*

**→** I already have a license: \[Proceed to **Download ↓**]

**→** I'm not sure which license I need: [MOTAR Licenses](/additioinal-features/motar-licenses)

## Download MOTAR QuickStart

Get the latest **MOTAR** Local **Installer** for your system:&#x20;

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th data-type="content-ref"></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td>Windows EXE</td><td><a href="https://dyn-downloads.s3.us-east-1.amazonaws.com/installers/windows-amd64/MOTAR_QuickStart.exe">https://dyn-downloads.s3.us-east-1.amazonaws.com/installers/windows-amd64/MOTAR_QuickStart.exe</a></td><td><a href="/files/5tYGQHsw3ceYn6vkmz8N">/files/5tYGQHsw3ceYn6vkmz8N</a></td></tr><tr><td>Windows Zip</td><td><a href="https://dyn-downloads.s3.us-east-1.amazonaws.com/installers/windows-amd64/MOTAR_QuickStart.zip">https://dyn-downloads.s3.us-east-1.amazonaws.com/installers/windows-amd64/MOTAR_QuickStart.zip</a></td><td><a href="/files/9t5y9Q6fnO1wDnqIV1hk">/files/9t5y9Q6fnO1wDnqIV1hk</a></td></tr><tr><td>Linux AMD</td><td><a href="https://dyn-downloads.s3.us-east-1.amazonaws.com/installers/linux-amd64/MOTAR_QuickStart.tar.xz">https://dyn-downloads.s3.us-east-1.amazonaws.com/installers/linux-amd64/MOTAR_QuickStart.tar.xz</a></td><td><a href="/files/JUDIIfhd9xJlyVi1laeV">/files/JUDIIfhd9xJlyVi1laeV</a></td></tr><tr><td>Linux ARM</td><td><a href="https://dyn-downloads.s3.us-east-1.amazonaws.com/installers/linux-arm64/MOTAR_QuickStart.tar.xz">https://dyn-downloads.s3.us-east-1.amazonaws.com/installers/linux-arm64/MOTAR_QuickStart.tar.xz</a></td><td><a href="/files/kuBnbgdDhgdU4KAmlQ7u">/files/kuBnbgdDhgdU4KAmlQ7u</a></td></tr><tr><td>Mac</td><td><a href="https://dyn-downloads.s3.us-east-1.amazonaws.com/installers/mac-arm64/MOTAR_QuickStart">https://dyn-downloads.s3.us-east-1.amazonaws.com/installers/mac-arm64/MOTAR_QuickStart</a></td><td><a href="/files/9z7okBnzZUW6Vnq7JM8f">/files/9z7okBnzZUW6Vnq7JM8f</a></td></tr></tbody></table>

#### Optional

**Download** sample files to speed up testing.\*

Sample files include everything you need to test MOTAR, such as models, video, a sample XR app, and images.

{% embed url="<https://dyn-downloads.s3.us-east-1.amazonaws.com/MOTAR-Tutorial-Files.zip>" %}

Once the appropriate files are **downloaded** and you have your **license** ready, proceed to the QuickStart Guild. [MOTAR QuickStart](/welcome/getting-started/local-installation/motar-quickstart)


# MOTAR QuickStart

This page will guide you through the process to install MOTAR locally for testing and demonstration purposes.

<figure><img src="/files/f6vJ57ORJGJd3TKeXDz2" alt=""><figcaption></figcaption></figure>

## Launching MOTAR QuickStart

**MOTAR QuickStart** *runs the same regardless of your system, with some minor differences for Windows.*

{% hint style="warning" %}
Running MOTAR QuickStart requires **Admin** privleges on the computer used to run MOTAR and update networking files.

If you did not run the installer as administrator, you will be prompted to continue without Admin privleges, this may cause some networking issues with the install.&#x20;

Select **NO** and then restart MOTAR QuickStart as an administrator.
{% endhint %}

<details>

<summary>Windows</summary>

* **Unpack** the zip file, if applicable
* Right Click the **MOTAR\_QuickStart.exe** file and select **"Run as Administrator"**
* You may be prompted to allow the Installer to run. Select **YES**

<figure><img src="/files/5aDYRJS8bgIp6KzhuyVn" alt="" width="375"><figcaption></figcaption></figure>

</details>

<details>

<summary>Mac/Linux</summary>

* Open Terminal and run the following command:

\*replace "/Downloads/" with the directory where you downloaded the installer.

```
sudo ./~/Downloads/MOTAR_QuickStart-darwin-arm64
```

</details>

***

## Using MOTAR QuickStart&#x20;

{% hint style="info" %}

### Installer Utility Note

The MOTAR Installer is a persistent utility. Retain the executable file to manage your instance, including starting, stopping, updating, or removing the platform.
{% endhint %}

#### Install MOTAR

* Select **Install MOTAR**

<figure><img src="/files/k7Th2DoTEpZD1dNIpmuZ" alt="" width="563"><figcaption></figcaption></figure>

{% hint style="warning" %}

### WARNING

***MOTAR** on Windows uses **Windows Subsytem for Linux** (WSL). If WSL is not found, you will be prompted to install WSL.* Follow the instructions in [#wsl-not-installed](#wsl-not-installed "mention")
{% endhint %}

<figure><img src="/files/bRHVs1UEmasvnTe3nB56" alt="" width="563"><figcaption></figcaption></figure>

* During installation several Command/Terminal windows may open, do not close these windows. They will close automatically.

<figure><img src="/files/5212ApWhUdUrbuInyp8m" alt="" width="563"><figcaption></figcaption></figure>

* When the Installer is finished (indicated by the :white\_check\_mark:), you can open your MOTAR page by clicking "**Open MOTAR**"

<figure><img src="/files/hsOfXbkA35QUHeGWVHyZ" alt=""><figcaption></figcaption></figure>

* Your default browser will open and the MOTAR configuration page will be shown.
* Enter your details and upload your **Discovery license**.&#x20;

{% hint style="info" %}
The user/password you create here will be your admin for your MOTAR test instance, keep it handy!
{% endhint %}

<figure><img src="/files/BwEfjQ6wA7LwOfkjxTlo" alt=""><figcaption></figcaption></figure>

#### Finalize MOTAR Setup

Fill out the information on the set up screen including a user name and password. Save this as it will be your first administrator user on the platform.

#### Congratulations!&#x20;

Your MOTAR Instance is now ready to add test content!

Using the MOTAR demo content? Follow our guide here: [MOTAR Tutorials](/welcome/motar-tutorials)

Adding your own content? See our guides here: [ADDITIOINAL FEATURES](/additioinal-features/motar-3d)

### **Issues**?&#x20;

See [#troubleshooting](#troubleshooting "mention")

***

## Additional Features

### Update MOTAR

Updating MOTAR is a simple process requiring only two clicks.&#x20;

**Click "**&#x53;top MOTAR" to **stop** the instance.

<figure><img src="/files/y2mR6tixgy0IBHI2bIPS" alt="" width="563"><figcaption></figcaption></figure>

**Click** "Update MOTAR" to **update** your instance to the latest version (if available).

<figure><img src="/files/WA5aDo9NlYY6bfJREwTb" alt="" width="563"><figcaption></figcaption></figure>

MOTAR will automatically start back up after the update is complete.

***

### Remove MOTAR

Removing MOTAR is a simple button click.

{% hint style="warning" %}

#### Don't Lost Your Data!

Did you use your own content to populate MOTAR and are moving to a fully deployed production version? Before you remove MOTAR, follow this guide to backup your data and import into the new instance!

[Broken mention](broken://pages/QByNki2DLeUSI013uSpN)
{% endhint %}

To remove MOTAR from your local system, simply launch the installer and **click** "Remove MOTAR"

<figure><img src="/files/Vjy7SNd2IEK60TMrPDwW" alt="" width="563"><figcaption></figcaption></figure>

* Confirm "**Yes**" to the popup

<figure><img src="/files/Pxr1MX6stCHSPlALnvP2" alt="" width="563"><figcaption></figcaption></figure>

* All files will be removed and the system will be restored to the original state.

<figure><img src="/files/whGdzUdrHZelrznD4WLK" alt="" width="563"><figcaption></figcaption></figure>

***

### Start/Stop Containers

You can start and stop your MOTAR instance without affecting your test data or assets. If you need to stop MOTAR or just want to spin it down between tests, simply click on the **Stop** button. MOTAR will be stopped with no loss of data.

Ready to start testing again? Simply run the **QuickStart** installer and click **Start**. MOTAR will startup after a few moments and you can continue the demo.

<figure><img src="/files/y2mR6tixgy0IBHI2bIPS" alt="" width="563"><figcaption></figcaption></figure>

***

### Open MOTAR

**Click** the "Open MOTAR" button to launch the MOTAR webpage in your default browser.

<figure><img src="/files/IPqwWhonym5ZwMdvXvWd" alt="" width="563"><figcaption></figcaption></figure>

***

## Troubleshooting

A small guide of solutions to common errors you may encounter during installation.

<details>

<summary><strong>I got the warning "Admin Privileges Required"</strong></summary>

* MOTAR Installer requires Admin privleges to run, select **NO** if prompted&#x20;

<figure><img src="/files/6yPsWjDJi0eLHx1OoUzy" alt="" width="375"><figcaption></figcaption></figure>

**Windows**

* Close the installer and restart as **Admin** *(right click on the installer file and select "Run as Administrator").*

<figure><img src="/files/auGhMRmfW5UBXlqhwsIW" alt="" width="336"><figcaption></figcaption></figure>

**Mac/Linux**

* Close the installer and restart using "sudo"

```
sudo ./~/<your file location>/MOTAR_QuickStart-darwin-arm64
```

</details>

<details>

<summary><strong>I got the warning "WSL Not Installed" on Windows</strong></summary>

MOTAR **requires** Windows Subsystem for Linux (**WSL**) to be installed on the computer. You can learn about WSL from the official Microsoft site: <https://learn.microsoft.com/en-us/windows/wsl/about>

{% hint style="info" %}
**Windows Subsystem for Linux (WSL)** is a Microsoft feature that allows developers and users to run a GNU/Linux environment directly on Windows. It lets you install and run Linux command-line tools, utilities, and applications without needing a separate virtual machine or dual-boot setup.
{% endhint %}

During the initial run, the installer will check your system for WSL, if not found, you will see the following message:

<figure><img src="/files/T88EyrqyplOhnZTxpBst" alt="" width="375"><figcaption></figcaption></figure>

To install WSL (Windows Subsystem for Linux):

* Open a new PowerShell window as **ADMIN**
* Type:&#x20;
  * ```
    wsl --install -d Ubuntu-24.04
    ```
* Ubuntu WSL will install on your machine.&#x20;
* You will be prompted by the installer to create a username/password. The WSL installer will default to your Windows username. Make note of your username and password, you'll need this to remove MOTAR later!

{% hint style="danger" %}
When entering a password, you will not see any indication that you are typing. This is normal behavior, be sure to make note of your password, as you may need it later.
{% endhint %}

{% hint style="warning" %}
If you are on Windows 10 you may be prompted for a reboot. If this happens, simply rerun the MOTAR Installer after reboot.
{% endhint %}

* Once WSL is installed on your machine, **rerun** the MOTAR Installer.

</details>


# Production Installation

#### Production Environment Deployment

{% hint style="danger" %}
**Note**: This documentation is intended for system administrators and DevOps engineers. It covers manual infrastructure provisioning, security protocols, and persistent storage configuration.
{% endhint %}

#### Production License

If your organization is ready to move beyond evaluation and deploy **MOTAR** for **mission-critical** operations, a **Production License** is required. These licenses are designed for:

* **Scalability**: Support for larger user bases, more assets, and high-concurrency workloads.
* **Operational Use**: Ideal for integrated training environments, permanent digital asset repositories, and live XR deployments.
* **Support & Stability**: Includes access to enterprise support and high-availability configurations.

Already have a license? If your organization has already purchased a Starter, Bronze, or Enterprise tier, you can proceed with your existing license file.

If you need to **purchase** a production-grade license, visit our pricing page.

<a href="https://www.motar.com/pricing" class="button primary">Purchase a Production License</a>

### Installing MOTAR

To install MOTAR on a Production Environment, follow our [Advanced Deployment Guide](/welcome/getting-started/production-installation/advanced-deployment-guide)


# Advanced Deployment Guide

A guide to advanced deployment methods for MOTAR

{% hint style="info" %}
**Recommended** for **Scalable Activation** Across Organization&#x20;
{% endhint %}

{% hint style="danger" %}
**This guide is for production deployments only.** If you are looking to evaluate MOTAR locally, refer to the [MOTARQuickStart ](/welcome/getting-started/local-installation/motar-quickstart) / Docker deployment guide instead. The Docker configuration is **not suitable for production use** — deploying it in a live environment may result in broken service connectivity and degraded performance.
{% endhint %}

<details>

<summary><strong>Helm Chart Installation</strong></summary>

### Helm Chart for Kubernetes

{% hint style="danger" %}
This cloud or local installation method is considered an **advanced install option**.
{% endhint %}

You can **install** MOTAR in a high availability fashion and optionally configure MOTAR components for **advanced deployments** (production, multi-node Kubernetes cluster deployments).

You will access the MOTAR Helm installation package through Dynepic's **Helm Repository**.

This Helm chart installs MOTAR with all of its dependencies in a Kubernetes cluster. Our Helm chart also employs non-MOTAR supporting charts, such as:

* A custom Minio chart branched from the Minio public chart.
* The Bitnami PostgreSQL chart.
* The ingress-nginx Kubernetes chart.
* The NATS public chart.

#### Prerequisites

* \[ ] Kubernetes 1.23+
* \[ ] Helm 3.8.0+
* \[ ] PV provisioner support in the underlying infrastructure
* \[ ] ReadWriteMany volumes for deployment scaling

{% hint style="info" %}
**Don't have a Kubernetes cluster yet?** If you are deploying on a single server or EC2 instance and need a simple path to get MOTAR running, see [#single-node-setup-with-microk8s](#single-node-setup-with-microk8s "mention") (Development / Evaluation).&#x20;

**Note** that a single-node MicroK8s instance is **not highly available or horizontally scalable** and is not recommended for large or mission-critical deployments.&#x20;

For true production environments, consider a managed Kubernetes service such as AWS EKS, GKE, or AKS.
{% endhint %}

The MOTAR Helm chart supports deployments in Kubernetes clusters hosted in nearly any cloud provider, local server, and self-hosted cloud. As such, many of the values are left to be filled in by the installing individual.

The default **values.yaml** should provide information sufficient to help you prepare the installation for your circumstance. If you find anything confusing or not intuitive, please reach out via [Contact Us!](/support/contact-us)

Below we will provide some general **recommended values**, and then some recommended values based on deployment type. You will be providing the values to the deployment which overrides the default where the values are set.

{% hint style="info" %}
&#x20;If MOTAR is already installed, proceed to the [Upgrading MOTAR with Helm](https://claude.ai/chat/2c294665-e061-4ca1-ba20-0a71ad3672af#upgrading-motar-with-helm) section below.&#x20;
{% endhint %}

{% hint style="warning" %}
&#x20;If using the Dynepic-provided Helm chart and images, you will need to authenticate with the Dynepic registry to pull the Helm chart, and provide a Secret in the cluster which contains the `dockerconfigjson` to pull the images. See the **imagePullSecret** section below.&#x20;
{% endhint %}

***

#### Step 1 — Configuration

* **Create** a values file in a known directory (replace `your_directory` with your actual path):

```sh
touch /your_directory/your_value.yaml
```

* **Edit** the values file:

```sh
nano /your_directory/your_value.yaml
```

* **Add** the following values. Update any field containing `your` or `you` with your actual values.
* **Save** with `CTRL-X` (if using nano).

{% hint style="warning" %}
Note that `environment` is set to `development` in the samples below. For a live or customer-facing deployment, change this to `production`.
{% endhint %}

**Sample values.yaml — Single Node Using NodePort**

{% code overflow="wrap" %}

```yaml
global:
  motarImageRegistry: harbor.dynepic.net
  domainName: your_domain.com
  initialAdminEmail: you@email.com
  environment: production
  mailConfig:
  reportTargets:
    - you@email.com
  securityTargets:
    - you@email.com
  s3Config:
    source: minio
    url: api-minio.your_domain.com

motar:
  ingress:
  className: nginx
  annotations:
    cert-manager.io/cluster-issuer: letsencrypt-cluster-issuer # If using certmanager clusterIssuer
    nginx.ingress.kubernetes.io/cors-allow-headers: DNT,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type,Range,Authorization,clientid
    nginx.ingress.kubernetes.io/enable-cors: "true"
    nginx.ingress.kubernetes.io/proxy-body-size: "0"
  tls:
    enabled: true
    tlsSecret: "webapps-cert" # Substitute with your tlsSecret
  serviceAccount:
    create: true
    name: motar
  minio:
    ingress:
      enabled: true
      className: nginx
      hostname: api-minio.your_domain.com
      annotations:
        apiVersion: networking.k8s.io/v1
        className: nginx
        cert-manager.io/cluster-issuer: letsencrypt-cluster-issuer # If using CertManager/ClusterIssuer
        nginx.ingress.kubernetes.io/proxy-body-size: "0"
      tls:
        enabled: true
        tlsSecret: "api-minio-cert" # Substitute with your tlsSecret
    consoleIngress:
      enabled: true
      className: "nginx"
      annotations:
        apiVersion: networking.k8s.io/v1
        className: nginx
        cert-manager.io/cluster-issuer: letsencrypt-cluster-issuer # If using CertManager/ClusterIssuer
        nginx.ingress.kubernetes.io/proxy-body-size: "0"
      hosts:
        - console-minio.your_domain.com
      tls:
        enabled: true
        tlsSecret: "console-minio-cert" # Substitute with your tlsSecret

storageClass:
  enabled: true
  provisioner: driver.longhorn.io
  parameters:
    fsType: ext4
    numberOfReplicas: "1"
    staleReplicaTimeout: "30"

ingress-nginx:
  enabled: true
  controller:
    service:
      type: "NodePort"
      nodePorts:
        http: 31080
        https: 31443

minio:
  auth:
    existingSecret: "motar-s3-auth"
    rootUserSecretKey: "rootUser"
    rootPasswordSecretKey: "rootPassword"

postgresql:
  sslDisabled: true
  auth:
    existingSecret: "motar-pg-auth"
    secretKeys:
      adminPasswordKey: "postgres-password"
      motarPasswordKey: "motar-password"
```

{% endcode %}

**Sample values.yaml — AWS EKS**

{% code title="aws\_values.yaml" overflow="wrap" %}

```yaml
global:
  motarImageRegistry: harbor.dynepic.net
  domainName: your_domain.com
  initialAdminEmail: you@email.com
  environment: production
  mailConfig:
  reportTargets:
    - you@email.com
  securityTargets:
    - you@email.com
  s3Config:
    source: minio
    url: api-minio.your_domain.com

motar:
  ingress:
  className: nginx
  annotations:
    cert-manager.io/cluster-issuer: letsencrypt-cluster-issuer # If using certmanager clusterIssuer
    nginx.ingress.kubernetes.io/cors-allow-headers: DNT,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type,Range,Authorization,clientid
    nginx.ingress.kubernetes.io/enable-cors: "true"
    nginx.ingress.kubernetes.io/proxy-body-size: "0"
  tls:
    enabled: true
    tlsSecret: "webapps-cert" # Substitute with your tlsSecret
  serviceAccount:
    create: true
    name: motar
  minio:
    ingress:
      enabled: true
      className: nginx
      hostname: api-minio.your_domain.com
      annotations:
        apiVersion: networking.k8s.io/v1
        className: nginx
        cert-manager.io/cluster-issuer: letsencrypt-cluster-issuer # If using CertManager/ClusterIssuer
        nginx.ingress.kubernetes.io/proxy-body-size: "0"
      tls:
        enabled: true
        tlsSecret: "api-minio-cert" # Substitute with your tlsSecret
    consoleIngress:
      enabled: true
      className: "nginx"
      annotations:
        apiVersion: networking.k8s.io/v1
        className: nginx
        cert-manager.io/cluster-issuer: letsencrypt-cluster-issuer # If using CertManager/ClusterIssuer
        nginx.ingress.kubernetes.io/proxy-body-size: "0"
      hosts:
        - console-minio.your_domain.com
      tls:
        enabled: true
        tlsSecret: "console-minio-cert" # Substitute with your tlsSecret

storageClass:
  enabled: true
  provisioner: kubernetes.io/aws-ebs
  parameters:
    fsType: ext4
    type: gp3

ingress-nginx:
  enabled: true
  controller:
    config:
      use-proxy-protocol: false
    service:
      type: LoadBalancer
      external:
        enabled: false
      internal:
        externalTrafficPolicy: Local
        enabled: true
        annotations:
          service.beta.kubernetes.io/aws-load-balancer-internal: false
          service.beta.kubernetes.io/aws-load-balancer-backend-protocol: tcp
          service.beta.kubernetes.io/aws-load-balancer-cross-zone-load-balancing-enabled: true
          service.beta.kubernetes.io/aws-load-balancer-type: nlb-ip

minio:
  auth:
    existingSecret: "motar-s3-auth"
    rootUserSecretKey: "rootUser"
    rootPasswordSecretKey: "rootPassword"

postgresql:
  sslDisabled: true
  auth:
    existingSecret: "motar-pg-auth"
    secretKeys:
      adminPasswordKey: "postgres-password"
      motarPasswordKey: "motar-password"
```

{% endcode %}

***

#### Step 2 — Prepare the Namespace

* Create the namespace:

```sh
kubectl create ns motar
```

* **Apply** the secrets for S3 storage and PostgreSQL.

{% hint style="warning" %}
**S3 connectivity is required for core MOTAR functionality.** Ensure your global.s3Config.url in values.yaml is reachable from within the cluster with tls to ensure file scanning and external connections function properly. Misconfigured or missing S3 secrets are the most common cause of broken deployments.
{% endhint %}

Both internal Minio and external S3 configurations require secrets for `rootUser` and `rootPassword`. Apply them from a YAML file:

```sh
kubectl apply -f mysecrets.yaml -n motar
```

Example YAML:

```yaml
apiVersion: v1
data:
  rootPassword: base64enc_value
  rootUser: base64enc_value
kind: Secret
metadata:
  labels:
    app.kubernetes.io/part-of: motar
  name: motar-s3-auth
type: Opaque
```

Or apply directly using literals:

```sh
kubectl -n motar create secret generic motar-pg-auth \
  --from-literal=motar-password=supersecret \
  --from-literal=postgres-password=topsecret

kubectl -n motar create secret generic motar-s3-auth \
  --from-literal=rootUser=minioUser \
  --from-literal=rootPassword=topsecretPassword
```

{% hint style="info" %}
&#x20;If you would like to apply a TLS certificate for use on your ingress and are not using CertManager, this is the point to do so.
{% endhint %}

***

#### Step 3 — Deploy the Chart

<pre class="language-sh" data-overflow="wrap"><code class="lang-sh">helm install motar --version <a data-footnote-ref href="#user-content-fn-1">3.</a>2.6 oci://harbor.dynepic.net/helmrelease/motar -f your_values.yaml -n motar
</code></pre>

***

#### Step 4 — Access the Site

If you have correctly configured DNS routing to your hosting device, MOTAR should now be accessible at `https://admin.your_domain.com`.

You have completed Helm setup and may continue to [Step 3 — Access Your MOTAR Instance](https://docs.motar.com/motar-tutorials#id-3-access-your-motar-instance).

</details>

<details>

<summary><strong>NodePort Configuration</strong></summary>

{% hint style="warning" %}
If using a NodePort configuration for your ingress controller, you will need to ensure traffic is routed to the correct port within your deployed environment. Below is a sample setup using an nginx reverse proxy.
{% endhint %}

* **Install** the required services:

```bash
sudo apt update
sudo apt install nginx
sudo apt install libnginx-mod-stream
sudo vim /etc/nginx/nginx.conf
```

* **Include** the proxy passthrough by appending the following outside the `http` block:

```nginx
http {
  # default configuration
}
include /etc/nginx/passthrough.conf;
```

* **Create** `/etc/nginx/passthrough.conf` with ports matching the NodePort values in your values file:

```nginx
stream {
  server {
    listen 80;
    proxy_pass 127.0.0.1:31080;
  }
  server {
    listen 443;
    proxy_pass 127.0.0.1:31443;
  }
}
```

* **Forward** HTTP to HTTPS with a redirect rule. Create a site config:

```bash
sudo vim /etc/nginx/sites-available/your.domain
```

```nginx
server {
  if ($host ~ ^[^.]+\.your\.domain$) {
    return 301 https://$host$request_uri;
  }
  listen 80;
}
```

* Remove the default nginx site and reload:

```bash
sudo rm /etc/nginx/sites-enabled/default
sudo nginx -t
sudo systemctl reload nginx
```

</details>

<details>

<summary><strong>Upgrading MOTAR with Helm</strong></summary>

To upgrade an existing MOTAR installation to a new chart version:

```sh
helm upgrade motar --version <new_version> oci://harbor.dynepic.net/helmrelease/motar -f your_values.yaml -n motar
```

Replace `<new_version>` with the target chart version. Your existing values file can be reused unless otherwise noted in the release notes.

</details>

<details>

<summary><strong>Troubleshooting FAQ</strong></summary>

**Services are running but the platform is not loading or media is missing.**

This is most commonly caused by S3 connectivity not being established. Verify:

1. Your `global.s3Config.url` in values.yaml is correct and reachable from within the cluster.
2. The `motar-s3-auth` secret was applied to the `motar` namespace.
3. If using internal Minio, confirm the Minio ingress is healthy: `kubectl get ingress -n motar`

</details>

***

### Optional / Alternative Deployments

<details>

<summary><strong>MOTAR AI Engine with Zero Trust Orchestration Layer (beta) Installation</strong></summary>

> **Note:** This is an advanced configuration.

Our MOTAR system includes a dedicated query server that requires an LLM. The query server interfaces with the LLM using OLLAMA API endpoints. We provide an OCI image containing all necessary components for the query server. To leverage your NVIDIA GPU, ensure the `nvidia-container-toolkit` is installed.&#x20;

If you prefer to manage dependencies yourself, the query server also requires a Redis database and the following Docker environment variables:

```env
LLM_API_HOST:  ${LLM_API_HOST}
PG_USER: ${POSTGRES_USER}
PG_PASS: ${POSTGRES_PASSWORD}
PG_DBNAME: ${POSTGRES_DB}
PG_HOST: ${POSTGRES_HOST}
PG_PORT: ${POSTGRES_PORT}
MINIO_ENDPOINT: ${MINIO_ENDPOINT}
MINIO_ACCESS_KEY: ${MINIO_ROOT_USER}
MINIO_SECRET_KEY: ${MINIO_ROOT_PASSWORD}
REDIS_HOST: ${REDIS_HOST}
REDIS_PORT: ${REDIS_PORT}
REDIS_DB: ${REDIS_DB}
```

* `PG_*` variables: Access to MOTAR's PostgreSQL database.
* `MINIO_*` variables: Credentials for your MOTAR MinIO instance.

***

**Example: Running OLLAMA and Redis Containers**

**OLLAMA:**

```yaml
ollama:
    image: ollama/ollama:latest
    container_name: ollama
    restart: unless-stopped
    runtime: nvidia
    ports:
        - "11434:11434"
    volumes:
        - ollama_models:/models
    environment:
        LOG_LEVEL: debug
        OLLAMA_MODELS: /models
        OLLAMA_DEBUG: 1
    entrypoint: ["/bin/bash"]
    command: ["-c", "dpkg --configure -a && apt update && apt install curl -y && sleep 5 && ollama serve & sleep 15 && ollama pull llama3 && pkill ollama && ollama serve"]
    healthcheck:
        test: ["CMD-SHELL", "curl -sf http://localhost:11434/api/tags | grep llama3"]
        interval: 10s
        timeout: 5s
        retries: 60
        start_period: 15s
```

**Redis:**

```yaml
redis:
    image: redis:7-alpine
    container_name: redis
    restart: unless-stopped
    volumes:
        - redis_data:/data
```

***

**MOTAR Configuration (External Query Server)**

Ensure MOTAR can access your query server. Example values file (AI section only):

```yaml
motar:
    ai:
        enabled: false  # Only deploys AI dependencies via Helm
        queryServer:
            external:
                enabled: true
                url: http://IP.OF.QUERY.SERVER
                port: 8000
```

***

**MOTAR Configuration (In-Cluster Deployment)**

To run everything inside your cluster, use a node configured for NVIDIA GPU passthrough. Apply a taint (e.g., `ai`) to schedule the query server and OLLAMA. Example values:

```yaml
ai:
    enabled: true
    llmServer:
        NodeSelector: node-role.kubernetes.io/ai: "true"
        runtimeClassName: "nvidia"
        tolerations:
            - key: "ai"
              operator: "Equal"
              value: true
              effect: "NoSchedule"
        storageSize: 10Gi
        models:
            - llama3:latest
        storageClassName: ""
        resourcesPreset: "gpuMedium"
        resources: {}
    queryServer:
        NodeSelector: node-role.kubernetes.io/ai: "true"
        tolerations:
            - key: "ai"
              operator: "Equal"
              value: true
              effect: "NoSchedule"
        runtimeClassName: "nvidia"
```

***

> Adjust values and configuration as needed for your environment and deployment strategy.

</details>

<details>

<summary><strong>MOTAR Discovery: Connecting an XR Headset</strong></summary>

When testing MOTAR locally using a Discovery license, it is possible to connect wireless XR headsets to your instance. However, this configuration is advanced and highly dependent on your current networking hardware, networking knowledge, and configuration permissions.

{% hint style="warning" %}

#### Proceed with Caution

While none of the following configurations will "break" your system and can be reversed, they may cause a loss of functionality for some users.

**We don't recommend** this configuration if you are **not** comfortable with altering both your network and the headset configuration.
{% endhint %}

Your network and hardware should meet the following criteria:

* An accessible and configurable router
* Developer permissions on the XR headset
* Admin permissions on the hosting computer

Connecting a wireless XR device to your local MOTAR test install may require the following changes based on your network and headset hardware:

* **Router Based Configuration** — requires a configurable network router
  * Customized record(s) added to the network router
* **Device Based Configuration**
  * Hosting and configuring files directly on an XR headset
  * Update local host files and/or updates to primary DNS
  * Local Domain Name Service changes

#### Meta Quest 3 Configuration

*Coming soon.* For questions in the meantime, please [contact us](https://docs.motar.com/support/contact-us).

</details>

***

<details>

<summary><strong>Single-Node Setup with MicroK8s</strong></summary>

Single-Node Setup with MicroK8s (Development / Evaluation)

{% hint style="warning" %}
**This setup is not suitable for production.** A single-node MicroK8s instance has no high availability, no horizontal scaling, and no redundancy. It is appropriate for development, evaluation, or getting MOTAR running correctly while you plan your production infrastructure. For mission-critical or large-scale deployments, use a managed Kubernetes service such as **AWS EKS**, **GKE**, or **AKS**.
{% endhint %}

{% hint style="info" %}
This page is for teams that **do not already have a Kubernetes cluster** running. If you have an existing cluster (e.g. AWS EKS, GKE, or self-managed), skip this page and proceed directly to the Advanced Deployment Guide.
{% endhint %}

MOTAR's Helm-based deployment requires a running Kubernetes cluster. If you are deploying on a single server or EC2 instance and do not have a cluster set up, **MicroK8s** provides a simple path to get a correct Kubernetes environment running quickly. The same MOTAR Helm chart and values.yaml used here will work against any managed Kubernetes cluster when you are ready to scale.

> **Note:** MOTAR support covers the Helm chart deployment and platform configuration. Setting up and administering your Kubernetes environment is outside the scope of MOTAR support. This page provides general guidance to help you get started.

***

### Prerequisites

* An EC2 instance or server running **Ubuntu 24.04 LTS** (recommended)
* SSH access to the instance
* `sudo` privileges
* Minimum recommended specs: 4 vCPU, 8GB RAM, 50GB storage (adjust based on your workload)

***

### Step 1 — Install MicroK8s

MicroK8s is distributed via [snap](https://snapcraft.io/microk8s) and installs in a single command.

```bash
sudo snap install microk8s --classic
```

Add your user to the `microk8s` group to avoid needing `sudo` for every command:

```bash
sudo usermod -aG microk8s $USER
newgrp microk8s
```

Verify the cluster is ready:

```bash
microk8s status --wait-ready
```

***

### Step 2 — Enable Required Add-ons

MicroK8s uses add-ons for core functionality. Enable the following:

```bash
microk8s enable dns storage ingress
```

| Add-on    | Purpose                                                  |
| --------- | -------------------------------------------------------- |
| `dns`     | Internal cluster DNS resolution                          |
| `storage` | Persistent volume provisioning (required for MOTAR data) |
| `ingress` | HTTP/HTTPS ingress controller                            |

***

### Step 3 — Configure kubectl

MicroK8s ships with its own `kubectl`. You can either use it directly with the `microk8s kubectl` prefix, or alias it for convenience:

```bash
alias kubectl='microk8s kubectl'
```

To make the alias permanent, add it to your `~/.bashrc` or `~/.bash_profile`:

```bash
echo "alias kubectl='microk8s kubectl'" >> ~/.bashrc
source ~/.bashrc
```

Verify cluster access:

```bash
kubectl get nodes
```

You should see your node listed with a `Ready` status.

***

### Step 4 — Install Helm

MOTAR is deployed via Helm. Install it with:

```bash
sudo snap install helm --classic
```

Verify the installation:

```bash
helm version
```

***

### Next Step

Once MicroK8s is running and Helm is installed, you are ready to deploy MOTAR.

***

For full MicroK8s documentation, visit [canonical.com/microk8s](https://canonical.com/microk8s).

</details>

> #### Following the Installation and Tutorial Guide?
>
> If you are following along with the tutorial, you should be ready to access and configure your MOTAR Instance. Click the link below to return:
>
> [https://docs.motar.com/motar-tutorials#id-3-access-your-motar-instance](https://docs.motar.com/motar-tutorials#id-3-access-your-motar-instance "mention")

[^1]: Version number may be different. Check for the lastest version.


# MOTAR Tutorials

A step-by-step tutorial to get you familiar with your MOTAR instance by walking you through adding users, studio groups and assets.

***

{% hint style="warning" %}

### Warning: *You cannot login as multiple users in a single browser session.*

*If you would like to manage multiple users while testing MOTAR, you can open a new "incognito" tab and login as the second user or use a different browser for the second user.*
{% endhint %}

## 1 - Add Platform Owner and Platform Branding

{% stepper %}
{% step %}
**Click** the blue "Edit" button to add the **Owning company** details

**Cosmic Horizon** is the owning company name for this tutorial and most of this information will already be completed based on the license that you uploaded. The Company Image and Favicon for Cosmic Horizon can be found at:&#x20;

**`MOTAR-Tutorial-Files/Platform-Branding/Company Icon/`**`Cosmic-Horizons-Company-Image-100x100.png`

Some information will be auto-populated from the License. **Your information may vary, depending on your license.**

\
Fill in any other missing information for the Platform Owner page and **click** "Save"

<figure><img src="/files/Nz6eN49MhxLh8NA9ZP1s" alt=""><figcaption><p>Platform Owner details page</p></figcaption></figure>
{% endstep %}

{% step %}
**Click** on the Platform Branding tab and **click** the blue "Edit" button.

For this tutorial, fill out the fields using the following:

{% hint style="info" %}
If you are not conducting a trial of MOTAR, and are setting up a MOTAR Instance for your own use, you will input your company's information and upload your company's branding.&#x20;
{% endhint %}

<details>

<summary>Platform Branding Details</summary>

*If you are setting up a MOTAR Instance for your organization, you may input the information for those specific Partners.*

<pre data-title="Contact Support Email: " data-overflow="wrap"><code><strong>support@cosmic-horizons.com
</strong></code></pre>

{% code title="Account Creator Email:" overflow="wrap" %}

```
accounts@cosmic-horizons.com
```

{% endcode %}

{% code title="Platform Name: " overflow="wrap" %}

```
Multidimensional Ecosystem
```

{% endcode %}

{% code title="Landing Page Image:" overflow="wrap" %}

```
MOTAR-Tutorial-Files/Platform-Branding/Landing-Page-Image/ME-Landing-Page-Image-845x850.png
```

{% endcode %}

{% code title="Platform Brand Image:" overflow="wrap" %}

```
MOTAR-Tutorial-Files/Platform-Branding/Platform-Brand-Image/ME-Platform-Branding-Image-480x140.png
```

{% endcode %}

{% code title="Navigation Brand Image:" overflow="wrap" %}

```
MOTAR-Tutorial-Files/Platform-Branding/Navigation-Brand-Image/ME-Navigation-Brand-Image-No-BG-120x35.png
```

{% endcode %}

</details>

<figure><img src="/files/ugS4iKDZtUdy6rcwOCWn" alt=""><figcaption><p>Platform Branding with all details completed</p></figcaption></figure>
{% endstep %}
{% endstepper %}

***

## 2 - Create Partners/Contractors - Studio Groups - and Users

{% stepper %}
{% step %}

### Create Partners/Contractors

> A partner/contractor is an external organization that is allowed on your platform, they can **only** access content that has been shared with them

* Navigate to the Partners or Contractors tab located on the left navigation menu
* Click "+ Partner/Contractor"&#x20;

<figure><img src="/files/MMUCnzRSCSqTpRAGJv7G" alt=""><figcaption><p>"+ Partner" button location</p></figcaption></figure>

* The Partner/Contractor Details pop-up will open

<figure><img src="/files/oNUBsUqIWc12PlRUaK6v" alt=""><figcaption><p>Partner Details pop-up</p></figcaption></figure>

* Enter Partner/Contractor Details

> In this tutorial, we will create two partners/contractors, **Awesome XR** and **New Horizon XR**. These partners will be tasked with creating 3D models and immersive application development

* Enter each partner/contractor into the details pop-up
* **Click** "Add" button to save the new partner/contractor

*Expand the following section for Tutorial Partners/Contractors details.*&#x20;

<details>

<summary>Partners/Contractors Details</summary>

*If you are setting up a MOTAR Instance for your organization, you may input the information for those specific Partners.*

## Awesome XR

{% code title="Company Name: " overflow="wrap" %}

```
AwesomeXR
```

{% endcode %}

{% code title="Company Description: " overflow="wrap" %}

```
An XR Content Creator.
```

{% endcode %}

{% code title="Company Handle: " overflow="wrap" %}

```
@awesomexr
```

{% endcode %}

{% code title="Company Address: " overflow="wrap" %}

```
1969 Artemis Dr., Cape Canaveral, FL 32920
```

{% endcode %}

{% code title="Company Image:  " overflow="wrap" %}

```
MOTAR-Tutorial-Files/Company-Image-&-Favicon/AwesomeXR/AwesomeXR-Company-Image.png
```

{% endcode %}

{% code title="Contact First Name: " overflow="wrap" %}

```
Peter
```

{% endcode %}

{% code title="Contact Last Name: " overflow="wrap" %}

```
Lankton
```

{% endcode %}

{% code title="Contact Email: " overflow="wrap" %}

```
p.lankton@awesomexr.com
```

{% endcode %}

{% code title="Contact Phone Number: " overflow="wrap" %}

```
555-555-1234
```

{% endcode %}

***

## New Horizon XR

{% code title="Company Name: " overflow="wrap" %}

```
New Horizon XR
```

{% endcode %}

{% code title="Company Description: " overflow="wrap" %}

```
An XR Content Creator.
```

{% endcode %}

{% code title="Company Handle: " overflow="wrap" %}

```
@newhorizonxr
```

{% endcode %}

{% code title="Company Address: " overflow="wrap" %}

```
23 Jordan Way, Chapel Hill, NC 27514
```

{% endcode %}

{% code title="Company Image:  " overflow="wrap" %}

```
MOTAR-Tutorial-Files/Company-Image-&-Favicon/New-Horizon-XR/New-Horizon-XR-Company-Image.png
```

{% endcode %}

{% code title="Contact First Name: " overflow="wrap" %}

```
Andromeda
```

{% endcode %}

{% code title="Contact Last Name: " overflow="wrap" %}

```
Polaris
```

{% endcode %}

{% code title="Contact Email: " overflow="wrap" %}

```
a.polaris@newhorizonxr.com
```

{% endcode %}

{% code title="Contact Phone Number: " overflow="wrap" %}

```
555-555-5678
```

{% endcode %}

</details>

Once you have enter **both** Tutorial Partners, your Active Partners screen should match the following image:

<figure><img src="/files/p2lliJccR93gIPlqYpZM" alt=""><figcaption><p>Active Partners list (Tutorial Partners added)</p></figcaption></figure>
{% endstep %}

{% step %}

### Create Studio Groups

> A **Studio Group** functions like a department within a commercial organization. Users assigned to a Studio group are granted the "creator" role, giving them access to the Studio service.&#x20;
>
> Additionally, listings can be permissioned to specific Studio Groups, ensuring that only members of the appropriate group can access or manage them.&#x20;

* Navigate to the Studio Groups tab located on the left navigation menu
* **Click** "+ Studio Group"

<figure><img src="/files/YeSEBylhdVlaZujPSfS2" alt=""><figcaption><p>Active Studio Groups list (currently empty)</p></figcaption></figure>

* The Studio Group Details pop-up will open

<figure><img src="/files/eowIuiCwueAZat5O8GCm" alt=""><figcaption><p>Adding a Studio Group</p></figcaption></figure>

* Enter Studio Group details:&#x20;

> In this tutorial, you will create two Studio Groups: **Awesome XR Studio** and **New Horizon XR Studio**. These represent the functional studios for each partner, and individual users will be assigned to them accordingly.

* Enter each Studio Group into the details pop-up
* **Click** "Add" button to save the new Studio Group

{% hint style="info" %}
Although the Studio Groups created in this tutorial may appear identical to the Partners added in the previous step, it's important to understand that a single Partner can have multiple Studio Groups, similar to departments within a company. For example, **Awesome XR** might include both an **Production Studio Group** and an **Distribution Studio Group**. This structure allows for highly customizable permission settings across different teams or functions.
{% endhint %}

*Expand the following section for* Studio Group *details.*&#x20;

<details>

<summary>Studio Group Details</summary>

If you are setting up a MOTAR Instance for your organization, input the information for those specific Studio Groups.

### Awesome XR Studio

{% code title="Studio Group Name: " overflow="wrap" %}

```
Awesome XR Studio
```

{% endcode %}

{% code title="Studio Group Description: " overflow="wrap" %}

```
XR content creation team.
```

{% endcode %}

<pre data-title="Studio Group Handle: " data-overflow="wrap"><code><strong>@awesomexrstudio
</strong></code></pre>

{% code title="Studio Group Image:  " overflow="wrap" %}

```
MOTAR-Tutorial-Files/Company-Image-&-Favicon/AwesomeXR/AwesomeXR-Company-Image.png
```

{% endcode %}

{% code title="Contact First Name: " overflow="wrap" %}

```
Athena
```

{% endcode %}

{% code title="Contact Last Name: " overflow="wrap" %}

```
Pollo
```

{% endcode %}

{% code title="Contact Email: " overflow="wrap" %}

```
a.pollo@awesomexr.com
```

{% endcode %}

{% code title="Contact Phone Number: " overflow="wrap" %}

```
555-555-1234
```

{% endcode %}

***

### New Horizon XR Studio

{% code title="Studio Group Name: " overflow="wrap" %}

```
New Horizon XR Studio
```

{% endcode %}

{% code title="Studio Group Description: " overflow="wrap" %}

```
XR content creation team.
```

{% endcode %}

<pre data-title="Studio Group Handle: " data-overflow="wrap"><code><strong>@newhorizonxrstudio
</strong></code></pre>

{% code title="Studio Group Image:  " overflow="wrap" %}

```
MOTAR-Tutorial-Files/Company-Image-&-Favicon/New-Horizon-XR/New-Horizon-XR-Company-Image.png
```

{% endcode %}

{% code title="Contact First Name: " overflow="wrap" %}

```
Andromeda
```

{% endcode %}

{% code title="Contact Last Name: " overflow="wrap" %}

```
Polaris
```

{% endcode %}

{% code title="Contact Email: " overflow="wrap" %}

```
a.polaris@newhorizonxr.com
```

{% endcode %}

{% code title="Contact Phone Number: " overflow="wrap" %}

```
555-555-5678
```

{% endcode %}

</details>

Once you have enter **both** Tutorial Studio Groups, your Active Studio Groups screen should match the following image:

<figure><img src="/files/zRYQLJk4THZ6E9BDeYvg" alt=""><figcaption><p>The Studio Groups Tab</p></figcaption></figure>
{% endstep %}

{% step %}

### Create Users

* Navigate to the Users tab located on the left navigation menu
* **Click** "+ Add New User"

<figure><img src="/files/Sn2C9jrytM0GeljD6UnC" alt=""><figcaption></figcaption></figure>

* The User Details pop-up will open

<figure><img src="/files/LYISSMxP4sndKAdIuvGd" alt=""><figcaption><p>User Details pop-up</p></figcaption></figure>

The pop-up contains three sections that must be completed in order. You must fill out all required fields in the current section before proceeding to the next. Use the tabs below to view each section:

{% tabs %}
{% tab title="User Details" %}

<figure><img src="/files/LYISSMxP4sndKAdIuvGd" alt=""><figcaption><p>User Details tab</p></figcaption></figure>
{% endtab %}

{% tab title="User Role(s)" %}

<figure><img src="/files/504rjtUa8Kofe3kWu2DD" alt=""><figcaption><p>User Role(s) tab</p></figcaption></figure>
{% endtab %}

{% tab title="Summary" %}

<figure><img src="/files/qX7iVxq5jZavGRPZE7v8" alt=""><figcaption><p>User Summary tab</p></figcaption></figure>
{% endtab %}
{% endtabs %}

> MOTAR offers multiple user roles:
>
> * **Standard User**: This role provides access to the platform features allowed by your license. It is selected by default. Standard users can interact with content according to the permissions set by the license.
> * **Auditor**: In addition to standard features, auditors can view, download, use, and distribute Hub listings. This role is ideal for users who need to audit or evaluate assets.
> * **Admin**: Admins have full access to the platform, including all administrative tools and settings.&#x20;
>   * **In this tutorial, you created an admin user during the initial installation setup.**

{% hint style="warning" %}
During this tutorial, we will switch between multiple user accounts. Each user must be assigned a password during creation, and they will be required to set a new password upon their first login.

For convenience, we’ve provided a **temporary password** and a **final password** that can be used across all tutorial users. These are intended for instructional use only, **do not use them for any real or secure accounts**.
{% endhint %}

For this **tutorial**, add the following **four** users via the users tab from the left menu, assign them to their respective **Partner Companies** and provision their respective roles.&#x20;

<details>

<summary>User Details</summary>

*All other **required** information (Salutation, etc.) can be arbitrary for this tutorial.* &#x20;

> For convenience, use the following shared passwords for all tutorial users:
>
> * **Temporary Password (used when creating the user profile):**&#x20;
>   * `Welcome12345!Test`
> * **Final Password (used when logging in for the first time, required):**&#x20;
>   * `Zebra$19plane!echo`
> * **Important:** These passwords are for **instructional use only**. Do not use them for securing real accounts.

***

{% hint style="info" %}
User handles are auto-generated during user creation. For this tutorial, each user will have **firstname-lastname** user handles. These will be noted during later steps.
{% endhint %}

## User 1

{% code title="First Name:" overflow="wrap" %}

```
John
```

{% endcode %}

{% code title="Last Name:" overflow="wrap" %}

```
Allen
```

{% endcode %}

{% code title="Primary Email:" overflow="wrap" %}

```
john@awesomexr.com
```

{% endcode %}

{% code title="Title:" overflow="wrap" %}

```
CTO
```

{% endcode %}

{% code title="Partner Company:" overflow="wrap" %}

```
Awesome XR
```

{% endcode %}

{% code title="Country:" overflow="wrap" %}

```
United States
```

{% endcode %}

{% code title="Role:" overflow="wrap" %}

```
Auditor
```

{% endcode %}

{% code title="Temporary Password:" overflow="wrap" %}

```
Welcome12345!Test
```

{% endcode %}

***

***

## User 2

{% code title="First Name:" overflow="wrap" %}

```
Kalvin
```

{% endcode %}

{% code title="Last Name:" overflow="wrap" %}

```
Smith
```

{% endcode %}

{% code title="Primary Email:" overflow="wrap" %}

```
kalvin@awesomexr.com
```

{% endcode %}

{% code title="Title:" overflow="wrap" %}

```
Manager
```

{% endcode %}

{% code title="Partner Company:" overflow="wrap" %}

```
Awesome XR
```

{% endcode %}

{% code title="Country:" overflow="wrap" %}

```
United States
```

{% endcode %}

{% code title="Role:" overflow="wrap" %}

```
Admin
```

{% endcode %}

{% code title="Temporary Password:" overflow="wrap" %}

```
Welcome12345!Test
```

{% endcode %}

***

***

## User 3

{% code title="First Name:" overflow="wrap" %}

```
Adam
```

{% endcode %}

{% code title="Last Name:" overflow="wrap" %}

```
Coder
```

{% endcode %}

{% code title="Primary Email:" overflow="wrap" %}

```
adam@newhorizonxr.com
```

{% endcode %}

{% code title="Title:" overflow="wrap" %}

```
Developer
```

{% endcode %}

{% code title="Partner Company:" overflow="wrap" %}

```
New Horizon XR
```

{% endcode %}

{% code title="Country:" overflow="wrap" %}

```
United States
```

{% endcode %}

{% code title="Role:" overflow="wrap" %}

```
Auditor
```

{% endcode %}

{% code title="Temporary Password:" overflow="wrap" %}

```
Welcome12345!Test
```

{% endcode %}

***

***

## User 4

{% code title="First Name:" overflow="wrap" %}

```
Tiffani
```

{% endcode %}

{% code title="Last Name:" overflow="wrap" %}

```
Bee
```

{% endcode %}

{% code title="Primary Email:" overflow="wrap" %}

```
tiff@newhorizonxr.com
```

{% endcode %}

{% code title="Title:" overflow="wrap" %}

```
Producer
```

{% endcode %}

```
Partner Company:

New Horizon XR
```

{% code title="Country:" overflow="wrap" %}

```
United States
```

{% endcode %}

{% code title="Role:" overflow="wrap" %}

```
Admin
```

{% endcode %}

{% code title="Temporary Password:" overflow="wrap" %}

```
Welcome12345!Test
```

{% endcode %}

***

</details>

Once you have enter **all four** Tutorial Users, your Active Users screen should match the following image:

<figure><img src="/files/OoYUDqARoBwLobwM4QuH" alt=""><figcaption><p>New users added</p></figcaption></figure>
{% endstep %}

{% step %}

### 3 - Add Users to Studio Groups

Now we want to **add** those **users** into their respective studio groups.&#x20;

* **Click** on "Studio Groups" in left menu
* **Click** the "Edit pencil" and open **New Horizons XR Studio** group page

<figure><img src="/files/c7KIRKiCGMfeGI9uLVqc" alt=""><figcaption></figcaption></figure>

* **Click** on the "Users" tab

<figure><img src="/files/j7y1ksminUb8pFZnVTZi" alt=""><figcaption></figcaption></figure>

* **Click** the "+ User" button

<figure><img src="/files/haftNDb3EJct4trGuecu" alt=""><figcaption></figcaption></figure>

* Add Adam and Tiffani to this studio group by **clicking** the "+ Add" button next to their profiles
* **Click** "Done"

<figure><img src="/files/okWuyRuQUFZfEgEtITkI" alt=""><figcaption><p>Studio Gropu Add Users pop-up</p></figcaption></figure>

* Repeat these steps for the **Awesome XR** Studio&#x20;
* *Add **John** and **Kalvin to Awesome XR***
  {% endstep %}

{% step %}

### Logout

**Logout** of the platform as the Owning Company Admin by clicking the navigator menu > "Logout"

<figure><img src="/files/2xmtPOmSAd03EJsZ0Ega" alt=""><figcaption><p>Logout location</p></figcaption></figure>
{% endstep %}
{% endstepper %}

Now that you have Partners/Contractors, Studio Groups, and Users, you are ready to add content!

***

## 4 - Add Content to MOTAR Instance

As mentioned in the **Introduction video**, you are working with external partners who are aiding your corporation with **3D models** and **immersive application** development.&#x20;

This **content** needs to be added to the **MOTAR platform**, so that all company and partner users can access the content to achieve the contract's objectives.&#x20;

In this next step, you will first add the MOTAR Tutorial Video that you watched at the start of this tutorial to the MOTAR Instance, so that it can be referenced by company and partner users throughout the contract.&#x20;

Following that, you will add various 3D models that have been created by the Awesome XR Partner Organization, that will be used to create the application training users how to fly a UFO.

***

* Login as **Kalvin Smith** of the AwesomeXR

<figure><img src="/files/JlhnCaUjgkr9DDaXRRlx" alt=""><figcaption><p>MOTAR Login screen</p></figcaption></figure>

> Since this will be your first time logging in as this user, you will be required to change the password. Here are the logins:
>
> * **Username**:&#x20;
>   * `kalvin-smith`
> * **Temporary Password (used when creating the user profile):**&#x20;
>   * `Welcome12345!Test`
> * **Final Password (used when logging in for the first time, required):**&#x20;
>   * `Zebra$19plane!echo`

* **Navigate** to the Studio service

<figure><img src="/files/7nfjg3ubSdaFAykWuTuW" alt=""><figcaption><p>Studio page</p></figcaption></figure>

{% hint style="warning" %}

### The following steps may require you to log in and out of various users.

*You cannot login as multiple users in a single browser session!*

\
*If you would like to manage multiple users while testing MOTAR, you can open a new "incognito" tab and login as the second user **or** use a different browser for the second user.*
{% endhint %}

### **Create a Video Listing**

<details>

<summary>Video Listing Guide</summary>

Using the video downloaded from the [Broken mention](broken://pages/4ZrWu216oQkhsbq4nR9n), create a new video asset.

<figure><img src="/files/D3lyHCE6kicTPqImxY1G" alt=""><figcaption><p>Video Listing Details</p></figcaption></figure>

* **Click** on the "Create Video" button to open the new listing modal
  * **Modal: What Type of Listing are you creating?**
    * Select **New HUB Listing**

Use the following information for the video listing details:

* **Asset File Path:**
  * `MOTAR-Tutorial-Files/Listings/Video/MOTAR-Ghost-Tutorial-Video-v2.mp4`
* **Listing Name:**
  * *MOTAR Ghost Tutorial Video*
* **Listing Description:**
  * *This tutorial will guide you through the MOTAR Ghost installation on your laptop or in your preferred cloud environment.*
* **Thumbnail Image Path:**
  * `MOTAR-Tutorial-Files/Listings/App/learn_to_fly_ufo_icon.png`
* **Click** the "Create" button
* **Settings:**
  * Select **Standard**
* **Permission Wizard:**
  * **Click** the "plus icon" in the **Public Modify** section to grant full rights to the user
* **Check** the box:
  * *“I certify that the information above is correct and ready to share”*
* **Click** "Publish"
* When prompted, choose **"Keep the current permissions"**

{% hint style="success" %}
Now that you have your first asset, return to the Hub and check it out!
{% endhint %}

* Navigate to the Hub Service

<figure><img src="/files/jHOY51irO2roRC3rqFt8" alt=""><figcaption><p>Hub discover page</p></figcaption></figure>

* Watch your uploaded video

<figure><img src="/files/LUcm6Oh89EAzMik0oQ4f" alt=""><figcaption><p>Video listing Hub details</p></figcaption></figure>

* Return to the Studio service

<figure><img src="/files/SOxTtw2Ic8xlHb5m9F9M" alt=""><figcaption><p>Studio service page</p></figcaption></figure>

</details>

### Create 3D Model Listings

<details>

<summary>Power Cell Model Listings Guide</summary>

*For this step you will create three versions of a Power Cell. This will teach you about the Digital Thread and Remixes!*

Use the details below to create three 3D model listings.

#### Blue UFO Power Cell - V1.0

<figure><img src="/files/gnua3WkdMRM0fy0zpfeZ" alt=""><figcaption><p>3D Model Listing Details</p></figcaption></figure>

* Click on the **Create Model** icon
* **What Type of Listing are you creating?**
  * Select **New HUB Listing**

**Upload**

* **Asset File Path:**
  * `MOTAR-Tutorial-Files/Listings/3D-Model/Powercell/1-Blue-Power-Cell/UFO_Powercell_1.glb`

**Info**

* **Listing Name:**
  * *Blue UFO Power Cell*
* **Listing Description:**
  * *A Power Cell found near the crashed UFO found in the Outer Banks of North Carolina. This is believed to be the energy source of the UFO. Observations note that this Power Cell glows blue.*
* **Thumbnail Image Path:**
  * `MOTAR-Tutorial-Files/Listings/3D-Model/Powercell/1-Blue-Power-Cell/UFO_Powercell_1.png`
* **3D Preview File:** (Optional: REQUIRED for viewing when [MOTAR Holodeck](/motar-core-services/intro-to-core-services/devices/motar-holodeck))
  * `MOTAR-Ghst-Tutorial-Files/Listings/3D-Model/Powercell/1-Blue-Power-Cell/UFO_Powercell_1.glb`
* **Click** "Create"

**Settings**

* **Polycount:**
  * *10,000 – 100,000*
* **Textures Included:** Yes
* **Animations Included:** No
* **Click** "Save"

**Permission Wizard:**

* **Click** the "plus" icon in the **Partners Modify** section
  * Add **Cosmic Horizon** and their partners to grant exclusive rights to this listing
* **Check** the box:
  * *“I certify that the information above is correct and ready to share”*
* **Click** "Publish"
  * Select **Keep Current Permissions**

***

#### Yellow UFO Power Cell - V1.1

<figure><img src="/files/WW9OAQvPM1k0SeWHMBWD" alt=""><figcaption><p>3D Model child remix</p></figcaption></figure>

* **Click** on the "Create Model" icon to open the new listing modal
  * Modal: What Type of Listing are you creating?
    * Select **Add a new Version to my own listing**
* What Type of Version are you adding?
  * Select **Add a Remix Version**
* Select the asset to make a version of:
  * Choose ***Blue Power Cell** V1.0*
* Select Where you would like your new Version to Go:
  * Select **Add a Child Version**

**Upload**

* **Asset File Path:**
  * `MOTAR-Tutorial-Files/Listings/3D-Model/Powercell/1-Yellow-Power-Cell/UFO_Powercell_2.glb`

**Info**

* **Listing Name:**
  * Yellow UFO Power Cell
* **Listing Description:**
  * Found near the crash site, this Power Cell is believed to be the energy source for the crashed UFO found in the Tahoe National Forest. Dissimilar to the original Power Cell, this Power Cell glows Yellow.
* **Thumbnail Image Path:**
  * `MOTAR-Tutorial-Files/Listings/3D-Model/Powercell/1-Yellow-Power-Cell/UFO_Powercell_2.png`
* **3D Preview File:** (Optional: REQUIRED for viewing when [MOTAR Holodeck](/motar-core-services/intro-to-core-services/devices/motar-holodeck))
  * `MOTAR-Tutorial-Files/Listings/3D-Model/Powercell/2-Yellow-Power-Cell/UFO_Powercell_2.glb`
* Click **Create**

**Settings**

* **Polycount:**
  * *10,000 – 100,000*
* **Textures Included:** Yes
* **Animations Included:** No
* **Click** "Save"

**Permission Wizard:**

* **Click** the "plus icon" in the **Partners Modify** section
  * Add **Cosmic Horizon** and their partners to grant exclusive rights to this listing
* **Check** the box:
  * *“I certify that the information above is correct and ready to share”*
* **Click** Publish"
  * Select **Keep Current Permissions**

***

#### Purple UFO Power Cell - V2.0

<figure><img src="/files/kAdsHc7FMI9FHaJrBmOG" alt=""><figcaption></figcaption></figure>

* **Click** on the "Create Model" icon to open the new listing. modal
  * Modal: What Type of Listing are you creating?
    * Select **Add a new Version to my own listing**
* What Type of Version are you adding?
  * Select **Add a Remix Version**
* Select the asset to make a version of:
  * Choose ***Blue Power Cell** V1.0*
* Select Where you would like your new Version to Go:
  * Select **Add a Parent Version**

**Upload**

* **Asset File Path:**
  * `MOTAR-Tutorial-Files/Listings/3D-Model/Powercell/1-Purple-Power-Cell/UFO_Powercell_3.glb`

**Info**

* **Listing Name:**
  * Purple UFO Power Cell
* **Listing Description:**
  * Power Cell found near the UFO crash site in the Appalachian Mountains. Unlike the other two Power Cells, this one has a purple aura.
* **Thumbnail Image Path:**
  * `MOTAR-Tutorial-Files/Listings/3D-Model/Powercell/1-Purple-Power-Cell/UFO_Powercell_3.png`
* **3D Preview File:** (Optional: REQUIRED for viewing when [MOTAR Holodeck](/motar-core-services/intro-to-core-services/devices/motar-holodeck))
  * `MOTAR-Tutorial-Files/Listings/3D-Model/Powercell/2-Purple-Power-Cell/UFO_Powercell_3.glb`
* **Click** "Create"

**Settings**

* **Polycount:**
  * *10,000 – 100,000*
* **Textures Included:** Yes
* **Animations Included:** No
* **Click** "Save"

**Permission Wizard:**

* **Click** the "plus" icon in the **Partners Modify** section
  * Add **Cosmic Horizon** and their partners to grant exclusive rights to this listing
* **Check** the box:
  * *“I certify that the information above is correct and ready to share”*
* **Click** "Publish"
  * Select **Keep Current Permissions**

</details>

<details>

<summary>Flashlight Model Listings Guide</summary>

Now you will create two versions of a Flashlight listing. *(Version 1.0 without texture and Version 1.1 Remix with texture).*&#x20;

#### Untextured Flashlight

<figure><img src="/files/C9cwD5NAzaFo5EximZNS" alt=""><figcaption><p>Flashlight listing</p></figcaption></figure>

* **Click** on the "Create Model" icon to open the new listing modal
  * **What Type of Listing are you creating?**
    * Select **New HUB Listing**

**Upload**

* **Asset File Path:**
  * `MOTAR Tutorial Files > Listings > 3D Model > Flashlight > 1. Untextured Flashlight > Dynepic_Flashlight_1.gltf`

**Info**

* **Listing Name:**
  * MOTAR Demo Flashlight
* **Listing Description:**
  * A 3D Model of a Flashligh&#x74;*.*
* **Thumbnail Image Path:**
  * `MOTAR Tutorial Files > Listings > 3D Model > Flashlight > 1. Untextured Flashlight > Dynepic_Flashlight_1_ThumbnailImage_1.png`
* Click **Create**

**Settings**

* **Polycount:**
  * *1,000 – 10,000*
* **Textures Included:** No
* **Animations Included:** No
* **Click** "Save"

**Permission Wizard:**

* **Click** the "plus" icon in the **Partners Modify** section
  * Add **Cosmic Horizon** and their partners to grant exclusive rights to this listing
* **Check** the box:
  * *“I certify that the information above is correct and ready to share”*
* **Click** "Publish"
  * Select **Keep Current Permissions**

***

#### Textured Flashlight

<figure><img src="/files/wLDf3t7BRLwucixLiGTy" alt=""><figcaption><p>Textured Flashlight</p></figcaption></figure>

* What Type of Listing are you creating?
  * Select **Add a new Version to my own listing**
* What Type of Version are you adding?
  * Select **Add a Remix Version**
* Select the asset to make a version of:
  * Choose **MOTAR Demo Flashlight**
* Select Where you would like your new Version to Go:
  * Select **Add a Child Version**

**Upload**

* **Asset File Path:**
  * `MOTAR-Tutorial-Files/Listings/3D-Model/Flashlight/2-Textured-Flashlight/Dynepic_Flashlight_2.gltf`

**Info**

* **Listing Name:**
  * MOTAR Demo Flashlight
* **Listing Description:**
  * A 3D Model of a Flashligh&#x74;*.*
* **Thumbnail Image Path:**
  * `MOTAR-Tutorial-Files/Listings/3D-Model/Flashlight/2-Textured-Flashlight/Dynepic_Flashlight_2_ThumbnailImage_1.png`
* **Click** "Create"

**Settings**

* **Polycount:**
  * *1,000 – 10,000*
* **Textures Included:** Yes
* **Animations Included:** No
* Click **Save**

**Permission Wizard:**

* **Click** the "plus" icon in the **Partners Modify** section
  * Add **Cosmic Horizon** and their partners to grant exclusive rights to this listing
* **Check** the box:
  * *“I certify that the information above is correct and ready to share”*
* **Click** "Publish"
  * Select **Keep Current Permissions**

</details>

<details>

<summary>UFO Control Panel Model Listing Guide</summary>

*Now you will create a model listing for the UFO Control Panel. This model has **animations***!

#### UFO Control Panel

<figure><img src="/files/LKNKEpX38CFwDndWPa0C" alt=""><figcaption><p>UFO Control Panel listing</p></figcaption></figure>

* **Click** on the "Create Mode"l icon to open the new listing modal
  * **Modal: What Type of Listing are you creating?**
    * Select **New HUB Listing**

#### Upload

* **Asset File Path:**
  * `MOTAR-Tutorial-Files/Listings/3D-Model/UFO-Control-Panel/UFO_Control_Panel.glb`

#### Info

* **Listing Name:**
  * *UFO Control Panel*
* **Listing Description:**
  * *A digital twin of the control panel from inside the crashed UFO found in the Outer Banks of North Carolina.*
* **Thumbnail Image Path:**
  * `MOTAR-Tutorial-Files/Listings/3D-Model/UFO-Control-Panel/UFO_Control_Panel_1.png`
* **3D Preview File (Optional** but REQUIRED when [MOTAR Holodeck](/motar-core-services/intro-to-core-services/devices/motar-holodeck)**):**
  * `MOTAR-Tutorial-Files/Listings/3D-Model/UFO-Control-Panel/UFO_Control_Panel.glb`
* **Click** "Create"

#### Settings

* **Polycount:**\
  *10,000 – 100,000*
* **Textures Included:** Yes
* **Animations Included:** Yes
* **Click** "Save"

#### Permission Wizard

* **Click** the "plus" icon in the **Partners Modify** section
* Add **Cosmic Horizon** and their partners to grant exclusive rights to this listing
* **Check** the box:\
  *“I certify that the information above is correct and ready to share”*
* **Click** "Publish"
* When prompted, select **Keep Current Permissions**

</details>

> Now that you have several listings on Hub, we will log out of the current user.

* Log out of Kalvin Smith

<figure><img src="/files/jyVMkJnShS6KnKhv4Cj4" alt="" width="563"><figcaption><p>Logout location</p></figcaption></figure>

***

### Create an App Listing

The **assets** you uploaded to MOTAR in the previous step have been leveraged by the New Horizon XR Team to create an XR application teaching a user how to Fly the UFOs that have been found across the world.&#x20;

This application needs to be **uploaded** to MOTAR, so that it can be securely distributed to members of the company that will fly the UFOs back to the laboratory for further research and analysis.

* Log in as **Tiffani Bee** of New Horizon XR

> Since this will be your first time logging in as this user, you will be required to change the password. Here are the logins:
>
> * **Username**:&#x20;
>   * `tiffani-bee`
> * **Temporary Password (used when creating the user profile):**&#x20;
>   * `Welcome12345!Test`
> * **Final Password (used when logging in for the first time, required):**&#x20;
>   * `Zebra$19plane!echo`

<details>

<summary>App Listing Guide</summary>

* From the Studio service, **click** the "App" icon

<figure><img src="/files/Tb4QcesSC6VQzi4o4UY0" alt="" width="563"><figcaption><p>Create App button</p></figcaption></figure>

* Select "New Hub Listing"

<figure><img src="/files/3DQTWe9AOx9nbO04peBG" alt=""><figcaption><p>Listing Type selection</p></figcaption></figure>

* Enter the required fields (listed below)

<figure><img src="/files/P5RMpZONpw5lPPpd8TNz" alt=""><figcaption><p>Required Fields</p></figcaption></figure>

* Once the required fields have been entered, the "Create" button will enable
* **Click** "Create"

Your listing will now be created and the Info tab will automatically open.&#x20;

Enter the following details and download the listed files for this listing:

**App Listing Details**

* Listing Name
  * **Learn to Fly UFO**&#x20;
* Listing Description
  * **An alien ship has crashed in a barn. Can you find all the power cells and fly away?**&#x20;
* Thumbnail
  * **MOTAR Tutorial Files > Listings > App > learn\_to\_fly\_ufo\_icon.png**
* Sample Images
  * **MOTAR Tutorial Files > Listings > App > learn\_to\_fly\_ufo\_preview\_01.png**
  * **MOTAR Tutorial Files > Listings > App > learn\_to\_fly\_ufo\_preview\_02.png**
  * **MOTAR Tutorial Files > Listings > App > learn\_to\_fly\_ufo\_preview\_03.png**
  * **MOTAR Tutorial Files > Listings > App > learn\_to\_fly\_ufo\_preview\_04.png**
  * **MOTAR Tutorial Files > Listings > App > learn\_to\_fly\_ufo\_preview\_05.png**
* Does your App run in a web browser?
  * **No**
* Settings
  * **n/a**
* Distribution
  * Listing File Path (download the pre-compiled application before starting)
  * **MOTAR Tutorial Files > Listings > App > learn\_to\_fly\_ufo\_demo.apk**
  * **Meta Quest 3**
  * **learn\_to\_fly\_ufo.apk**
  * **Package Name:** com.Dynepic.LearntoFlyUFO
* SDKs&#x20;
  * **none**
* Permissions&#x20;
  * **Click on the plus in the "Cosmic Horizon Modify" section to only give members of Cosmic Horizon rights to this listing**
  * **Check the “I certify that the information above is correct and ready to share” box**
* Click **"Submit App for Review"**

</details>

{% hint style="info" %}
Now that the app as been created, we will go to **Admin** and approve the app. For this tutorial, we will stay logged in as Tiffani. In a normal workflow, app creation and approval would not be the same person.
{% endhint %}

### Approve the App

* Use the **TopNav** menu on the far **left** to navigate to the **Admin** service
* From the left menu, navigate to **App Review**
* Locate the app created in the previous step
* **Check** the “I have reviewed the app….” box and **approve** the app
* Use the **TopNav** menu on the far left to navigate to the **Studio service**
* From the studio group service, **find your app** and **click** the "Edit pencil", then **click** on "Publish"
* Keep **Current** Permissions Settings
* **Navigate** to the Hub service and see app in Production
* **Log out**

> ## Congratulations!&#x20;
>
> You've successfully learned how to add listings to your instance, approve apps, and create Users, Studio Groups, and Partners. You've covered all the foundational steps needed to manage your MOTAR environment.
>
> The next section moves into more intermediate-to-advanced territory: setting up VR headsets and installing applications on them using our companion app. If you don't have access to a VR headset or prefer to pause here, feel free to continue exploring your MOTAR instance by logging in as different users and experimenting with what you've built so far.

***

## Optional Steps

<details>

<summary>Connecting an XR Headset to your Instance</summary>

***COMING SOON!***

Connecting your XR Headset to your local MOTAR instance is and advanced setup requiring updates to both your network router and your headset's network configuration.&#x20;

This process may be different for every user can cannot be completly covered in an online guide.&#x20;

For more control and reliability, it is recommended you install MOTAR using the [Advanced Deployment Guide](/welcome/getting-started/production-installation/advanced-deployment-guide) for cloud hosting and connect to your instance via a domain. \
This would allow MOTAR 3D and App connections without network modifications.

</details>

<details>

<summary>Install MOTAR 3D to VR Headsets</summary>

**MOTAR 3D** is an immersive XR companion application that allows you to quickly discover, install, and launch immersive content found on the Hub and begin collaborative learning through a virtual environment on any XR device, no matter where your team members are located.&#x20;

MOTAR 3D is compatible with the following devices.

* Meta Quest 2
* Meta Quest 3
* Meta Quest Pro
* Vive Focus 3

It even works seamlessly with **Meta Quest for Business**.&#x20;

Instructions for downloading and installing MOTAR 3D can be found [HERE](/additioinal-features/motar-3d)

{% hint style="warning" %}
Side loading applications to Meta Quest devices requires a Meta Developer account and for the device to be in "Devleoper Mode".&#x20;
{% endhint %}

</details>

<details>

<summary>Install the App to the Headset</summary>

Your pre-existing app is now **ready for distribution**. Loading apps onto a **VR** device depends on your current organization setup.&#x20;

Whether your ogranization uses **Meta Quest for Business**, Meta Quest Devloper Hub, or sideloading,  learn how by following the app installtion guide: [MOTAR 3D](/additioinal-features/motar-3d#installing-applications-on-a-vr-device)

</details>

<details>

<summary>Launch an Application</summary>

You can **launch** your application in two ways.&#x20;

From within **MOTAR 3D**, by clicking "Launch" on the app listing

OR

**Launch** directly from Hub!

* Log into Hub.&#x20;
* Locate the application and open the Hub listing Page.&#x20;
* Click “Launch with MOTAR 3D” in the top right corner.

<figure><img src="/files/CgakwjBKZbb4R1LRwOxc" alt=""><figcaption></figcaption></figure>

If MOTAR 3D is **installed** on the Headset, click “Continue on Headset.”

<figure><img src="/files/PvRY3E66EBQ3hLccKXqi" alt=""><figcaption></figcaption></figure>

**Follow the instructions** on the MOTAR Devices page to sync the headset.

* Launch MOTAR 3D.
* Sync the device.

<figure><img src="/files/wO87sPeYybmPHYlZ3Z3I" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
Launcing applications via web or MOTAR 3D on Meta Quest devices requires the application be installed prior to launching.
{% endhint %}

</details>

<details>

<summary>Build an XR Application Using the MOTAR SDK for Unity</summary>

Ready to put your development skills to the test? Dive into our complete Unity XR sample project and see how easy it is to create immersive experiences using the MOTAR SDK for Unity. In this guide, you'll learn how to:

* Set up the MOTAR SDK in a Unity project
* Integrate the MOTAR XR Rig into your scene
* Compile and prepare your application for hosting on your MOTAR instance

Whether you're exploring XR for the first time or looking to extend your MOTAR experience, this project is a great place to start!

👉 [**Get Started with the Learn to Fly UFO Complete Project**](broken://pages/eP6dJt0EMPCMrJFh5eM5)

</details>


# Platform Branding


# Partners and Contractors


# Studio Groups


# Demo Content


# Users


# MOTAR Lab 2025

MOTAR Lab 2025 was held on 29 May 2025. This video recording of the lab details step-by-step setting up a MOTAR local instance with a government use license.

{% embed url="<https://vimeo.com/1089208770>" %}


# Learn to Fly UFO - XR App Build Tutorial

This guide will walk you through create a compiled Android application targeting Meta Quest devices, using the Unity Editor and the MOTAR SDK for Unity.

{% hint style="info" %}
This comprehensive tutorial will walk you through the complete Unity project setup and creation.&#x20;
{% endhint %}

Each **section** will guide you through the entire process, from installing **Unity** to compiling the application! Don't be worried if you have never opened Unity or created an application, this tutorial was built with you in mind!

{% hint style="warning" %}
If you are an **experienced developer** you may want to skip the tutorial app and just dive into the **MOTAR SDK for Unity** docs! [MOTAR SDK for Unity](/motar-core-services/intro-to-core-services/devices/motar-sdk-for-unity)
{% endhint %}

### Ready to Fly?&#x20;

This tutorial may take up to or over an hour, depending on your system and comfort with development. To begin Click **Next** > Prerequisites below!


# Prerequisites

***

Before proceeding, ensure your system meets the following requirements:\
:rocket: **MOTAR Account** with MOTAR Studio permissions\
:desktop: **System Requirements**: Verify your computer meets Unity’s system requirements: Unity - System \
💾 **Storage**: At least **3GB free storage space** for installation

Optional Requirements\
🔲**VR Headset**: Meta Quest 2, Quest 3, or Quest Pro<br>

If using a **Meta Quest** for local testing, ensure it is in **Developer Mode** ( [MOTAR 3D](/additioinal-features/motar-3d#meta-quest-device-developer) ). Also, have a **USB-C cable** for easy app loading.

{% hint style="info" %}
If you have Unity 2022.3 installed, simply create a new Universal 3D project and skip to [Broken mention](broken://pages/VUsmlzeEXJLeius50YSC)
{% endhint %}

***

### 1. Install and Configure Unity Hub

#### 1.1 Install Unity Hub

1. **Download Unity Hub** from the official [Unity website](https://unity.com/download).
   1. **Unity Editor**: Version **2022.3+ LTS** (This tutorial was built with **2022.3.38**)
2. **Launch the installer** and follow the on-screen instructions.
3. If prompted, **read and agree** to the license agreement.
4. **Skip** Unity Editor installation if prompted (this will be covered later).
5. **Skip** license activation if prompted (this will be covered later).

***

#### 1.2 Create a Unity ID

If you **already have a Unity ID**, skip to 1.3 Activate a License.

1. **Open Unity Hub** and **log in** or **create an account**.
2. If not prompted to log in, **click the Account icon** (top-right corner) and select **Create Account**.
3. Follow the website prompts to **complete account creation**.
4. Once your account is created, **log in to Unity Hub**.

***

#### 1.3 Activate a License

If you **already have an active license**, skip to 1.4 Install Unity Editor.

1. **Click the Account icon** in Unity Hub and select **Manage Licenses**.
2. Click **Add License**.
3. Choose either:
   * **Free Personal License (**&#x72;ecommende&#x64;**)**
   * **Activate with a serial number**
4. Follow the on-screen prompts to complete license activation.

***

#### 1.4 Install Unity Editor

1. Open Unity Hub and select the **Installs** tab.
2. Click **Install Editor**.
3. Locate the latest **Unity 2022.3 LTS** (with **Android Build Support**).
4. If the version **does not appear**, go to the **Archive tab** and download **Unity 2022.3.38** from the Unity Download Archive.
5. Click **Install** and ensure the following **modules are selected**:
   * ✅ Android Build Support
   * ✅ Microsoft Visual Studio Community 2019 (**Optional** for coding in Unity)
6. Click **Continue** and follow installation prompts.
7. If prompted, **agree** to Android SDK and NDK License terms.
8. Click **Install** (Installation may take several minutes).

***

### 2. Create a Unity Project

#### 2.1 Start a New Project

1. Open Unity Hub and select the **Projects** tab.
2. Click **New Project**.
3. Select the **Universal 3D Core** template under the **Core** tab. (this may require downloding the template)
4. Enter a **Project Name** and choose a **File Path** to store it.
5. Click **Create** to launch Unity.


# Install Sample Project

## Setting Up Your Unity Project with the MOTAR SDK

### Prerequisites

* Unity 2022.3+ (SDK supports Unity 2021.3 and up)
* Unity Editor installed
* Basic familiarity with Unity’s Package Manager and Project Settings

{% hint style="warning" %}
If your project uses an older version of Unity and cannot be updated, please reach out for assistance.
{% endhint %}

***

### Installing the MOTAR SDK via Scoped Registry

* Open **Unity Editor** and navigate to **Edit > Project Settings**.
* In the **Project Settings** window, select **Package Manager**.
* Add a new **Scoped Registry** with the following details:
  * **Name**: MOTAR
  * **URL**: `https://registry.hub.motar.com`
  * **Scope(s)**: `com.motar`
* Click **Save** and close **Project Settings**.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXdSpLVVA7LDM97-avf9kvrPC7TSkYmHAbqOyaoZksx5xNZhJTe7lWN5xDF8hYVxrQrzQYU6cph7L-bzEjSJ_8ihcvT9dWnXmlcCool5JwQ1tcTXWhjd6z883expqHfr7FXfWOdyOQ?key=qX-PfMadnNws3SscZCg7guPi" alt=""><figcaption></figcaption></figure>

* Open **Package Manager** (`Window > Package Manager`).
* Change the dropdown from **Packages: In Project** to **My Registries** (Unity might take a minute to detect the registry).
* Under **Dynepic**, select **MOTAR SDK** and click **Install**.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXeIwVszdsUcGR8YQNSGXgmOLyMc9HyavSGFUTCK-Jlv6fvdH4VBbjMobn9ZKRWo2cv8FWruJtOkc-jO3UdmV_D1If4qpkH7pXS_Z3kCy1KYj7wpeMnnfqwZywiY76fak_8rqYOOTw?key=qX-PfMadnNws3SscZCg7guPi" alt=""><figcaption></figcaption></figure>

* Click **Yes** to enable new input system backends (required for UI interaction).&#x20;

{% hint style="danger" %}
Unity will restart.
{% endhint %}

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXenCmXdNMxDyBvfd4KzSW_TNPGzevTjR3oUppHdTNbg_TG4LHknAMGFu4mATyhBjdoqvjckbtadjrErQ-5dS6NClsNUzX3v0n70Ya6NImMoKdr5d-vyFDDzX9bi4Ofy3Qb54qW-8w?key=qX-PfMadnNws3SscZCg7guPi" alt=""><figcaption></figcaption></figure>

***

### Importing Samples

<figure><img src="/files/NYbyQ9SMs77s6SXPfkV1" alt=""><figcaption></figcaption></figure>

#### Device Sync Sample

1. Open **Package Manager** and select **MOTAR SDK** under **Dynepic**.
2. Click on **Samples**.
3. Find **Device Sync** and click **Import**.
4. Navigate to `Assets/Samples/MOTAR SDK/<current version>/Device Sync/Scenes`.
5. Open the **MOTARDeviceSyncAndAuthentication** scene.
6. When prompted, click **Import TMP Essentials**.

#### Avatar Sample

1. Open **Package Manager** and select **MOTAR SDK** under **Dynepic**.
2. Click on **Samples**.
3. Find **Avatar** and click **Import**.

#### Learn to Fly UFO (URP Only) Sample

1. Open **Package Manager** and select **MOTAR SDK** under **Dynepic**.
2. Click on **Samples**.
3. Find **Learn to Fly UFO (URP Only)** and click **Import**.

***

You are now ready to begin setting up the Unity scene(s).&#x20;

Continue to: [Broken mention](broken://pages/85br9IvaUswcek4ifG0f)


# Set Up the Scenes

Setting Up the Scenes

1. Navigate to `Assets -> Samples -> MOTAR SDK -> 1.0.0 -> Learn to Fly UFO (URP Only) -> Scenes`.
2. Open **BarnScene**.

<figure><img src="/files/ZyNTAUu66J3gxmA70EZx" alt="" width="373"><figcaption></figcaption></figure>

#### Adding the Player

* Navigate to `Assets -> Samples -> MOTAR SDK -> 1.0.0 -> Avatar -> Resources`.

<figure><img src="/files/3M7ijeHdaixarRDxvbyX" alt="" width="375"><figcaption></figcaption></figure>

* Drag **MOTAR\_Player** prefab into the **Hierarchy** window.

<figure><img src="/files/UY07n61oNlGtxxZjZTzY" alt="" width="323"><figcaption></figcaption></figure>

* Set its **Position** to `(0, 0, 7)` and **Rotation** to `(0, 180, 0)`.

<figure><img src="/files/cSfsI8NIzk3PgGZpIEFX" alt="" width="362"><figcaption></figcaption></figure>

#### Changing Movement Controls

* Locate the **Left Controller** inside **MOTAR\_Player** (`MOTAR_Player -> Camera Offset`).&#x20;

<figure><img src="/files/cQVEfGai8iVvtHJ7b9OK" alt="" width="336"><figcaption></figcaption></figure>

* Find the component **MOTAR Controller Manager**. In the **Inspector** window
* Uncheck **Smooth Motion** to enable teleport movement.

<figure><img src="/files/t3sDMel5Oim9oc8zrr6P" alt="" width="375"><figcaption></figcaption></figure>

#### Linking Player to UFO Animation

* In **Hierarchy**, find **UFO\_1** inside **UFO\_Assets**.

<figure><img src="/files/PZk3ksxcXZefTBoBdZK1" alt="" width="375"><figcaption></figcaption></figure>

* Locate the **UFO Event Manager** component in the **Inspector** window

<figure><img src="/files/pL23qbLgK3fU4VMIZJ0F" alt="" width="336"><figcaption></figcaption></figure>

* Click **+** under **On UFO Animation End ()**.

<figure><img src="/files/UnLV47YbjAbQEhVB5poM" alt="" width="338"><figcaption></figcaption></figure>

* Drag **MOTAR\_Vignette\_1** from **MOTAR\_Player -> Camera Offset -> Main Camera** into the new event.

<figure><img src="/files/xkdNsyQXV1EKfOwSGAtO" alt="" width="360"><figcaption><p>The Player prefab</p></figcaption></figure>

<figure><img src="/files/Jh4g2jXLlzhHAdJ4bBWh" alt="" width="342"><figcaption><p>Prefab added to the  UFO Animation End ()</p></figcaption></figure>

* From the "No Function" dropdown, select **MOTARVignette -> FadeOut()**.

<figure><img src="/files/KUt951XrdW3LoMXYOwzH" alt="" width="390"><figcaption><p>Select the function through the popout menus</p></figcaption></figure>

<figure><img src="/files/0n5q0z3mmW2kFNDZIbnf" alt=""><figcaption><p>FadeOut function added to the UFO Animation End ()</p></figcaption></figure>

* Navigate to **MOTAR\_Vignette\_1,**&#x20;
  * Alternatively, click **Add Component**
  * Type **MOTARLoadScene**&#x20;
*

```
<figure><img src="/files/exFGhaTJ4hl1ERxLkXfb" alt=""><figcaption></figcaption></figure>
```

* Press **Enter** on your keyboard to add the script.
* Set **Scene Index** to **2** in **MOTARLoadScene**.

<figure><img src="/files/LgAwfPvtyDrcKfH2eAUB" alt=""><figcaption></figcaption></figure>

* Under **MOTAR Vignette**, click **+** under **Fade Out Ended ()**.

<figure><img src="/files/FOgCml1Dx6SxZWdQ62D2" alt=""><figcaption></figcaption></figure>

* Drag **MOTAR\_Vignette\_1** into the event and select **MOTARLoadScene -> LoadScene()**.

<figure><img src="/files/B5KupQ5Ah9v0AWuLlUda" alt=""><figcaption></figcaption></figure>

* **Save** the scene.

#### Copying Player to the Final Scene

* In **BarnScene**, select **MOTAR\_Player** and copy it (`Edit -> Copy`).
* Open `Assets -> Samples -> MOTAR SDK -> 1.0.0 -> Learn to Fly UFO (URP Only) -> Scenes -> UFOScene`.
* Paste **MOTAR\_Player** into the **Hierarchy**.
* Set its **Position** to `(0, 0, 0)` and **Rotation** to `(0, 0, 0)`.

<figure><img src="/files/VmcK0Nq8JxAW0eXRYS95" alt=""><figcaption></figcaption></figure>

#### Fading Player in the Final Scene

* In **Hierarchy**, find **RestartButton** inside **UI -> Canvas\_Ending**.

<figure><img src="/files/ddqhsihStATNHEJP8OUj" alt=""><figcaption></figcaption></figure>

* Locate the **Button** component.

<figure><img src="/files/R3mIPCsrNnGA0MDxbY2k" alt=""><figcaption></figcaption></figure>

* Click **+** under **On Click ()**.

<figure><img src="/files/yjw0lZYvNTYoxzZQXU7g" alt=""><figcaption></figcaption></figure>

* Drag **MOTAR\_Vignette\_1** from **MOTAR\_Player -> Camera Offset -> Main Camera** into the event.
* Select **MOTARVignette -> FadeOut()**.

<figure><img src="/files/pIYUWwDQx2jTo7RrG9b2" alt=""><figcaption></figcaption></figure>

* Locate **MOTARLoadScene** in **MOTAR\_Vignette\_1**.
* Change **Scene Index** to **1**.

<figure><img src="/files/1y6lbLn6nGVjMi6g4S5t" alt=""><figcaption></figcaption></figure>

* **Save** the scene.

***

###


# Set Up XR Controls

### Setting Up XR Controls

* Open **Edit -> Project Settings**.
* Navigate to **XR Plugin Management**.
* Click **Install XR Plugin Management**.

<figure><img src="/files/k5SKBVZxFh8vHUX7hFpi" alt="" width="491"><figcaption></figcaption></figure>

* Under **XR Plug-in Management**, check **OpenXR** for **Android**. (Unity will install some plugins)

<figure><img src="/files/HWr5wtWrTlgwJ7vUgcIA" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
Make sure you have the Android tab selected. You will do the same for the Desktop tab!
{% endhint %}

* You may see a red ! under OpenXR

  * Goto XR Plug-in Management > Project Validation
  * Select Fix All

  <figure><img src="/files/YilzxEyXv8fJ9d95xn4R" alt=""><figcaption></figcaption></figure>
* Under **XR Plug-in Management**, select **OpenXR**
* Under **Enabled Interaction Profiles**, add **Oculus Touch Controller Profile**.
* Enable **Meta Quest Support** under **OpenXR Feature Groups**.

<figure><img src="/files/xNNb1WKOSxngtTJn0CoH" alt="" width="563"><figcaption></figcaption></figure>

***

#### Repeat these steps for the Desktop tab:

{% hint style="info" %}
Desktop settings will not have the Meta Quest support but will allow you to test in the Unity Editor
{% endhint %}

<figure><img src="/files/YuqR3mufUxUT2P6QPdc4" alt=""><figcaption></figcaption></figure>

You are ready to link your application to MOTAR!


# Configure the MOTAR SDK

In order to allow your application to sync with MOTAR you will need to add a Configuration file.&#x20;

### Get the Client ID and Secret from Studio

* Log into Studio
* Locate the app listing you created earlier in the Tutorial "Learn to Fly UFO"
* Click **Settings**
* Keep this page open and return to Unity.

<figure><img src="/files/EO7XRxNzWs0stKTuMSxg" alt=""><figcaption></figcaption></figure>

### Create / Modify the Configuration File

* In your Unity project, **Click** MOTAR SDK&#x20;

  <figure><img src="/files/wSsn2rP3HxVkQ3WZWxvR" alt=""><figcaption></figcaption></figure>
* A new MOTAR Configuration window will open.&#x20;

*If an app has already been linked, the window will show you the current ID/Secret for your app.*&#x20;

{% hint style="danger" %}
Modifying the configuration file may disconnect your app from the app listing! Ensure you have the correct ID and Secret for your application.
{% endhint %}

* Copy and Paste your Client ID and Secret from Studio, into the fields:<br>

  <figure><img src="/files/OSyKJuCtehAplwSYm9fk" alt="" width="281"><figcaption></figcaption></figure>
* Click **Generate**
* Once added, a file will be generated and is located in the Assets\MOTAR directory

<figure><img src="/files/xMmj2IeEOj8cInuw14FW" alt=""><figcaption></figcaption></figure>

{% hint style="success" %}
You application has now been connected and is ready to test and build!&#x20;
{% endhint %}


# Build the Application

### Configuring Build Settings

* Open **File -> Build Settings**.
* Verify the following scenes are under **Scenes in Build**:
  * `MOTARDeviceSyncAndAuthentication`
  * `BarnScene`
  * `UFOScene`
* Remove **SampleScene** if present.
* Select **Android** as the platform and click **Switch Platform**.
* Navigate to **Edit -> Project Settings -> XR Plug-in Management -> Project Validation**.
* Click **Fix** on any errors regarding supported architectures.

***

### Configure Player Settings

* Open Edit > Project Settings
* Click on Player
* Update Company Name / Product Name / Version

  *(for this tutorial, **match** the entries listed below)*

<figure><img src="/files/jb1rygOlzFVFAgTNkeoU" alt=""><figcaption></figcaption></figure>

* Ensure the Android tab is selected and scroll to **Other Settings**

<figure><img src="/files/EvNgRGFhXTJNjIYuBdLS" alt=""><figcaption></figcaption></figure>

* Scroll to Identification

<figure><img src="/files/RKAwQtgzAy7ZeKlrXPs2" alt=""><figcaption></figcaption></figure>

* Ensure your Package Name is named "com.Dynepic.LearntoFlyUFO"&#x20;

{% hint style="info" %}
This name will be entered into the Studio listing distribution and is used to launch the app from MOTAR 3D

Unity auto generates this name based on the Company
{% endhint %}

### Building the Application

* Open **File -> Build Settings**.
* Ensure **Platform** is set to **Android**.
* Ensure **Active Input Handling** is set to **New** in **Player Settings**.
* Return to **Build Settings** and click **Build**.
* Enter a memorable file name and save the build.
* Unity will begin compiling the application (this may take several minutes).

{% hint style="danger" %}
BuildiBuilding or compiling an application for Android can be complex, often depending on your local system environment. If you encounter build errors, check the Unity console—it will point you to the exact issue and may provide helpful troubleshooting tips.
{% endhint %}


# Intro to Core Services

<div data-full-width="true"><figure><img src="/files/Se7RfHa3GkZHexqtmFAj" alt="" width="375"><figcaption></figcaption></figure></div>

## MOTAR

At its core, MOTAR is the centralized foundation for deploying, organizing, and managing digital assets across your organization. Built on a zero-trust security architecture, it provides a secure, permission-based environment for XR operations, whether hosted on-premise, in the cloud, or via a third-party provider.

#### Key Capabilities

* Unified Management: Manage all internal and external content via a single authentication method.
* Enterprise Services: Five integrated services designed to work seamlessly across the platform.
* Developer-First Tools: Open APIs and SDKs provide the necessary framework for building immersive applications.
* Secure Distribution: Ensure version control and protected access from initial deployment to the end-user.
* Scalable Operations: A secure pipeline to manage assets, create applications, and deliver multi-modal training.

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-type="content-ref"></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td>Admin</td><td>Configure, Brand, and Manage Accounts and App Release.</td><td><a href="/pages/eikQ3F3nqDSlU0FeqJKN">/pages/eikQ3F3nqDSlU0FeqJKN</a></td><td><a href="/files/k1FnUhIUsY6QquDuh7Ie">/files/k1FnUhIUsY6QquDuh7Ie</a></td></tr><tr><td>Devices</td><td>Securely authenticate your XR headset.</td><td><a href="/pages/zSMQTirl9G87M56MSZma">/pages/zSMQTirl9G87M56MSZma</a></td><td><a href="/files/SvsFqEvPcj7V8tKORC9i">/files/SvsFqEvPcj7V8tKORC9i</a></td></tr><tr><td>Hub</td><td>Permissions-based Digital Asset Management with Digital Thread.</td><td><a href="/pages/fHEdYVayuQ0jPXcyQSbW">/pages/fHEdYVayuQ0jPXcyQSbW</a></td><td><a href="/files/fCwCTN84WWKenFtzu1kg">/files/fCwCTN84WWKenFtzu1kg</a></td></tr><tr><td>Studio</td><td>Create and Distribute Content (3D Models, Apps, etc.)</td><td><a href="/pages/Xr60LCU6KunYgZhxVR94">/pages/Xr60LCU6KunYgZhxVR94</a></td><td><a href="/files/OQVFW9KUw33I8CjKVp91">/files/OQVFW9KUw33I8CjKVp91</a></td></tr><tr><td>MOTAR SDK</td><td>Adds secure user authentication and User Profile Access.</td><td><a href="/pages/yqZucIEU1WtO4Nu8Qxw0">/pages/yqZucIEU1WtO4Nu8Qxw0</a></td><td><a href="/files/X0xeaHmJM0V7bePqVyRp">/files/X0xeaHmJM0V7bePqVyRp</a></td></tr><tr><td>Profile</td><td>Manage your profile and learner record.</td><td><a href="/pages/vLXLKtKgeoczSCmTFsC0">/pages/vLXLKtKgeoczSCmTFsC0</a></td><td><a href="/files/UdssDnM90h3HgTOoAadN">/files/UdssDnM90h3HgTOoAadN</a></td></tr></tbody></table>

***

#### Extended Capabilities

**MOTAR Core** continues to evolve beyond asset management. These new features expand the platform’s reach, unlocking additional ways to integrate, deploy, and scale immersive experiences without compromising security or ownership.&#x20;

Built directly on **Core** services, they plug into your existing workflows and give teams more flexibility to solve real operational problems, without adding complexity.

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-type="content-ref"></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td>MOTAR AI (Beta)</td><td>The MOTAR AI Engine with Zero Trust Orchestration Layer (beta) learns from yoru content and allows queries based on the MOTAR Permissions.</td><td><a href="/pages/q64DPF9vrJNu2PpfGIJL">/pages/q64DPF9vrJNu2PpfGIJL</a></td><td><a href="/files/gFTNs75WOImcV7JxEjDx">/files/gFTNs75WOImcV7JxEjDx</a></td></tr><tr><td>Holodeck</td><td>On Demand XR Rendering of Digital Assets for Training &#x26; Ops.</td><td><a href="/pages/byoTmJufpsXZeJWzarjI">/pages/byoTmJufpsXZeJWzarjI</a></td><td><a href="/files/lXEAZRQqp0nRShd3kqvM">/files/lXEAZRQqp0nRShd3kqvM</a></td></tr><tr><td>Learner Record</td><td>The Learning Records Store is a complete view of learner performance in one place. Track progress, measure readiness, and unlock insights across every app, device, and training experience.</td><td><a href="/pages/nLbOXqgEeUErkQ58q8ot">/pages/nLbOXqgEeUErkQ58q8ot</a></td><td><a href="/files/UdssDnM90h3HgTOoAadN">/files/UdssDnM90h3HgTOoAadN</a></td></tr><tr><td>MOTAR CertIQ</td><td>Portable Digital Records, tamper-proof smart certificates that travel with the learner. MOTAR CertIQ embeds full CMI5/xAPI training data directly into each certificate, allowing credentials earned offline to be securely uploaded into MOTAR.</td><td><a href="/pages/NVUKC190OIBiWPFwE8XQ">/pages/NVUKC190OIBiWPFwE8XQ</a></td><td><a href="/files/aLlb4xw8BEDgJ2woN3Gb">/files/aLlb4xw8BEDgJ2woN3Gb</a></td></tr></tbody></table>


# Admin

Configure, Brand, and Manage Accounts and App Release

## MOTAR Admin Overview

MOTAR Admin allows users to configure, brand and manage accounts and app release.

<figure><img src="/files/G3zlIw65WxHAqIP6UAA9" alt=""><figcaption></figcaption></figure>

## **How to Use MOTAR Admin On A Commercial License**

<table data-card-size="large" data-view="cards"><thead><tr><th data-type="content-ref"></th><th></th></tr></thead><tbody><tr><td><a href="/pages/nviWMNayHIaz5ZqRcEIX">/pages/nviWMNayHIaz5ZqRcEIX</a></td><td></td></tr><tr><td><a href="/pages/HZLFzDep9frofPcQcsXL">/pages/HZLFzDep9frofPcQcsXL</a></td><td></td></tr><tr><td><a href="/pages/7XleRmSOwsNyGvD1iP3J">/pages/7XleRmSOwsNyGvD1iP3J</a></td><td></td></tr><tr><td><a href="/pages/bSU9uOrYThmrC9UwBip4">/pages/bSU9uOrYThmrC9UwBip4</a></td><td></td></tr></tbody></table>


# Owning Company

For Self Managed Organizations, **Owning Company** is the organization that purchased the MOTAR Ghost Instance. The Owning Company is established in the license file when a MOTAR License is procured. This information can be confirmed on the Owning Company page within the MOTAR Admin Service.&#x20;

<figure><img src="/files/ZScT1IutaSFSctNju4pT" alt=""><figcaption><p>The Owning Company fields will be pre-filled from the MOTAR License file.</p></figcaption></figure>

Some fields on the Owning Company can be updated if necessary. Additionally, you will also need to upload a company image and favicon to the MOTAR instance.

<figure><img src="/files/zZ0d5DGcTgKKDA6MS3dw" alt=""><figcaption></figcaption></figure>


# Platform Branding

MOTAR can be white-labeled with your company's branding on the Platform Branding tab. Here, you will set the:

* Contact Support Email
* Account Creation Support Email
* Platform Name

You will also set the Landing Page, Platform Brand, and Navigation Brand images for the platform. Use the Preview Image on the right-hand side of the page to see what the Landing Page will look like with the new Branding information.

<figure><img src="/files/qGEL591ECQWLjOwHiD1d" alt=""><figcaption><p>MOTAR Instance Platform Branding</p></figcaption></figure>


# Platform Licensing

Use this tab to view your current license details, or upload a new license.

<figure><img src="/files/OP98nrVDjR0FsEgX0SLV" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
Licenses can be updated with the same provisioning as the original instance. Example, if you have a commercial license, you would not be able to install a government license here[^1].
{% endhint %}

[^1]:


# Platform Version Updates

Guide to updating your MOTAR Instance to the latest version.

{% hint style="warning" %}

### CAUTION

Before updating MOTAR, you should take a backup of your instance. See: [Backup & Restore Data](/motar-core-services/intro-to-core-services/admin/owning-company/backup-and-restore-data)
{% endhint %}

The Platform Version tab has a version checker that will tell you when there is a new version available to update:

When a new version is available, <mark style="color:red;">(!)</mark> will show next to the Platform Version tab.

Note the Installed Version vs Available Version in the image below.
\\

<figure><img src="/files/l0HlMyUBvKfuQ9nJGUH3" alt=""><figcaption><p>The Platform Version tab notes a new version is available.</p></figcaption></figure>

**Updating** your MOTAR Ghost to the latest version is **highly dependent** on your **installation** method. Choose the method below that matches your installation. If you do not know what type of installation you have, consult your platform admin.

{% hint style="danger" %}

### WARNING

Updating the platform version requires some degree of technical knowledge pertaining to your company's server architecture and installation method.&#x20;

Please review the steps below and if you are unsure of any of the steps, **DO NOT PROCEED,** reach out to your company administrator or [Contact Us!](/support/contact-us)
{% endhint %}

Choose the guide based on your installation method:

<details>

<summary>HELM Installation</summary>

#### Upgrade

{% hint style="danger" %}

### WARNING

If you did not provide **secrets** for HELM install, **do NOT** **delete** the **secrets** . The update process will recreate secrets and motar won't be able to access your data.
{% endhint %}

To update the MOTAR version on your HELM install, run:

{% code overflow="wrap" %}

```shell
# Replace {new version} with the latest release number (e.g. 1.2.3)
# Replace {yourvalues.yaml} with your Helm values file

helm upgrade motar --version {new version} oci://harbor.dynepic.net/helmrelease/motar -f {yourvalues.yaml} -n motar
```

{% endcode %}

#### Uninstall/Upgrade

{% hint style="warning" %}

If you **uninstall** instead of upgrade, you need to **backup** your secrets and your instance first!
{% endhint %}

* *Backup your secrets file (secrets backup is not covered in this guide. If you need assistance on how to backup your secrets, refer to your IT administrator.*
* *Backup your MOTAR Instance:* [Broken mention](broken://pages/QByNki2DLeUSI013uSpN)

Once you have backed up everything, you can run:

```sh
helm uninstall motar -n motar
```

Once the uninstall process completes you can start the install process by running:

<pre class="language-sh" data-overflow="wrap"><code class="lang-sh"># Replace {new version} with the latest release number (e.g. 1.2.3)
# Replace {yourvalues.yaml} with your Helm values file

<strong>helm install motar --version {new version} oci://harbor.dynepic.net/helmrelease/motar -f {yourvalues.yaml} -n motar
</strong></code></pre>

{% hint style="warning" %}
The relevant **secrets** will persist (do not delete the ones that stayed)
{% endhint %}

If secrets were deleted you will need to destroy persistent volumes

If you uninstall MOTAR before updating, you will need to restore from backup.\
Follow this guide to restore your data: [Broken mention](broken://pages/QByNki2DLeUSI013uSpN)

</details>

***

<details>

<summary>ARGO Installation</summary>

Update the MOTAR version number  to in your settings to the latest version number listed in your Platform Verision tab.&#x20;

*See example below.*

<figure><img src="/files/3XRetrN1Xjd5GT679THX" alt=""><figcaption></figcaption></figure>

</details>

***

<details>

<summary>DOCKER Installation</summary>

{% hint style="warning" %}
The following guide is for Docker installtion/update on a Linux/Mac machine. For Windows machines, see the Tutorial setup installation guide: [/pages/C4IBgTqQMu1wRhcgqfTh#id-2.-installing-motar-with-docker](https://docs.motar.com/motar-core-services/intro-to-core-services/admin/owning-company/pages/C4IBgTqQMu1wRhcgqfTh#id-2.-installing-motar-with-docker "mention")

For an **easier** install process, **download** the MOTAR Installer for **Windows**:

{% embed url="<https://dyn-downloads.s3.us-east-1.amazonaws.com/MOTAR.Installer.exe>" %}

**Instructions** can be found here: [Broken mention](broken://pages/1i9AjJkceAKzepNzLT4P)
{% endhint %}

Installing via Docker

* Download the correct install package for your operating system. &#x20;
  * <https://github.com/Dynepic/MOTAR/tree/main/Docker-Installation-Packages>
* *If you do not have access to this link, please reach out to*[ *motar@dynepic.com*](mailto:motar@dynepic.com) *for assistance.*&#x20;

If you want to shut down your instance during the update run:

```
docker compose down 
```

{% hint style="success" %}
Take note of where you download the MOTAR installation package because you will need it to configure the MOTAR Environment.
{% endhint %}

***

{% code overflow="wrap" %}

```sh
# Replace <version-number> with the MOTAR version you downloaded (e.g., 1.2.3)
cd /path/to/motar/download/directory/motar-<version-number>-beta-docker-compose/EasySetup
```

{% endcode %}

### Check and Configure Docker

{% hint style="warning" %}
Before running Docker commands, ensure the Docker desktop app is running.
{% endhint %}

* Open your terminal window
  1. Search **Terminal** in Spolight or find it in Application > Utilities
* Run the following **command** to check if Docker Compose is installed:

```shell
docker compose version
```

* You should see a result like this example *(your result may vary):*

```sh
Docker Compose version v2.31.0-desktop.2
```

* If no errors, continue, otherwise if you encounter a permission error, prepend sudo to the command:&#x20;

```sh
sudo docker compose version
```

* Make sure your Docker is running by typing:

```sh
docker ps
```

* As an **example**, if docker is running, but there are no containers running you may see output like this *(if you have containers running you may see additional details beneath these headings)*:

```sh
CONTAINER ID   IMAGE     COMMAND   CREATED   STATUS    PORTS     NAMES
```

* If you get the proper response, continue to [#linux-mac-1](#linux-mac-1 "mention"), otherwise if you encounter a permission error, use the sudo command:

```sh
sudo docker ps
```

{% hint style="warning" %}
If you still encounter an error or do not see the expected output (see below), please follow Docker’s documentation for fixing your Docker or Docker Compose.
{% endhint %}

**With Docker running it is time to Configure your MOTAR Environment**

### Configure Your MOTAR Environment

While in Terminal, you will configure your MOTAR Docker package.

1. **Change directory** to the location you saved the MOTAR docker compose install package from [#motar-installation-packages](#motar-installation-packages "mention")

{% hint style="info" %}
This is the folder where you saved your **motar-**[**3.0.1**](#user-content-fn-1)[^1]**-docker-compose.tar.gz** file.
{% endhint %}

{% code overflow="wrap" %}

```sh
cd /<path to motar-docker-compose package> # Change to your MOTAR download directory
# Example: cd /downloads/
```

{% endcode %}

2. **Unpack** the MOTAR installation file (if you already unpacked the file, you may skip to step 3)

<pre class="language-sh"><code class="lang-sh"># Replace &#x3C;version-number> with the MOTAR version you downloaded (e.g., 1.2.3)
tar -xvf motar-<a data-footnote-ref href="#user-content-fn-2">3.0.1</a>-beta-docker-compose.tar.gz
</code></pre>

3. Once the file is **unpacked**, you will need to change directory into the EasySetup folder.

<pre class="language-sh"><code class="lang-sh">cd motar-<a data-footnote-ref href="#user-content-fn-2">3.0.1</a>-beta-docker-compose/EasySetup
</code></pre>

{% hint style="warning" %}
For other more **advanced** options, replace the child sub-directory with ‘SelfProxy-Advanced’ or ‘EasyDNS’.  **This walk-through will only provide instructions for ‘EasySetup’.**

Reach out to <motar@dynepic.com> with questions.
{% endhint %}

4. **Before** launching MOTAR, you'll need to **copy sample environment files** and update with your deployment’s specifics. Sample environment files are provided to help you get started.

{% code overflow="wrap" %}

```sh
#Replace <version-number> with the MOTAR version you downloaded (e.g., 1.2.3)
cd /path/to/motar/download/directory/motar-3.0.1-beta-docker-compose/EasySetup
```

{% endcode %}

```sh
cp ../sample_env .env
```

<pre class="language-sh"><code class="lang-sh"><strong>cp ../sample_motar_env motar.env
</strong></code></pre>

{% hint style="info" %}
For this demo the URL for your MOTAR intance will be set to "motarghost.com".&#x20;
{% endhint %}

{% hint style="success" %}
**MOTAR images** are hosted in Dynepic’s private **Harbor** repository. Follow these steps to authenticate
{% endhint %}

### Deploying MOTAR with Docker Compose

{% hint style="success" %}
MOTAR can be deployed in different configurations. Choose the setup that best suits your needs.
{% endhint %}

1. Ensure you are still in the EasySetup folder in **Terminal**

{% code overflow="wrap" %}

```sh
#Replace <version-number> with the MOTAR version you downloaded (e.g., 1.2.3)
cd motar-<version-number>/EasySetup #Your installation directory
docker compose up -d # brings up the deployment in the background
```

{% endcode %}

{% hint style="danger" %}
Deployment of MOTAR on your local machine will take 3-5 minutes.
{% endhint %}

*You should see the following progress/message(s)*

```sh
 ✔[+] Running 19/19
 ✔ Network motar_motar            Created 
 ✔ Container minio                Healthy 
 ✔ Container motar-traefik-1      Started 
 ✔ Container nats                 Started 
 ✔ Container dnsmasq              Started 
 ✔ Container postgres             Healthy 
 ✔ Container clamav               Started 
 ✔ Container db-init              Exited  
 ✔ Container obj_init             Exited  
 ✔ Container assets               Healthy 
 ✔ Container scanner              Started 
 ✔ Container devices              Started 
 ✔ Container hub                  Started 
 ✔ Container admin                Started 
 ✔ Container studio               Started 
 ✔ Container login                Started 
 ✔ Container studio-permissions   Started 
 ✔ Container hub-permissions      Started 
 ✔ Container devices-permissions  Started  
```

{% hint style="warning" %}
&#x20;**Launching** a browser window may direct your admin page to <mark style="color:red;">**https\://**</mark>\
&#x20;to avoid this, launch in a private window. This should keep the path **http\://**
{% endhint %}

### Configuring Network & Domain Routing

To ensure your client device can resolve domain names correctly, configure your DNS settings.

1. Use the following **Terminal** command to backup your 'hosts' file:

```sh
cp /etc/hosts /etc/hosts_bak
```

2. Append your 'hosts' file with the following command:

{% code overflow="wrap" fullWidth="true" %}

```sh
IP="127.0.0.1"
BASE_URL="motarghost.com"
echo "$IP admin.$BASE_URL hub.$BASE_URL studio.$BASE_URL devices.$BASE_URL api-minio.$BASE_URL  login.$BASE_URL console-minio.$BASE_URL minio" | sudo tee -a /etc/hosts
```

{% endcode %}

</details>

<br>

[^1]: Version numbers may vary. Please refer to the downloaded file.

[^2]: Replace with the MOTAR version you downloaded (e.g., 1.2.3)


# Backup & Restore Data

Manage data is where you would initiate a backup of the current platforms data and/or restore the platform from a previously backed up file[^1].

Login as the Platform Owner  and go to the Admin Section > Managed Data tab and **click** "Backup Data".

{% hint style="info" %}
An information list will show each backup and when the backup was performed. Backups are **NOT** stored on the instance!
{% endhint %}

<figure><img src="/files/K6PBDO47Hi3KP1anJCZh" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
The backup file is saved locally! It is your responsibility to ensure this file is stored properly and in a secure location.&#x20;
{% endhint %}

A save file dialog popup will prompt you to save the backup file locally. This file contains ALL of your instance data (all users, assets, etc).

<figure><img src="/files/aj3RaQDvhOru9Yc88KTR" alt=""><figcaption><p>Backup creation popup during loading...</p></figcaption></figure>

{% hint style="info" %}
Your download time may vary depending on the amount of data stored and your bandwidth, please **be patient** while the file is compressed and downloaded.
{% endhint %}

## Restore from Backup

{% hint style="danger" %}

## WARNING!

Restoring MOTAR from a backup is **ABSOLUTELY destructive**! ALL data will be restored to the backup version and **any data** entered since the backup **will be lost**. This includes assets, studios, users and partners/contractors.
{% endhint %}

Restoring your instance from a backup is performed from the same menu as backing up.

#### As a Platform Manager navigate to the Manage Data tab:<br>

<figure><img src="/files/ZbugMo0sJ1SgyDuE3E5T" alt=""><figcaption><p>Manage Data</p></figcaption></figure>

#### Select **Restore Data**

A popup will open. Read carefully and **click** "Select File to Restore"

<figure><img src="/files/W4Eie2DpwCTnSxr14myU" alt=""><figcaption></figcaption></figure>

A file manager window will open. Select the backup file you would like to restore.&#x20;

{% hint style="info" %}
If the \*.enc backup file downloaded does not show up in the file dialog, change your settings to **show "All Files"**
{% endhint %}

During the restore process, your screen will **only** show a loading wheel.&#x20;

This process may take **several minutes**, depending on your bandwidth and data size. Please **be patient** and do not close the browser!

<figure><img src="/files/tpKEM4jJPnQV9OVV2BTa" alt=""><figcaption><p>Loading screen during a restore.</p></figcaption></figure>

{% hint style="info" %}
We are currently updating the system to give you feedback during the data restoration process. For now, you will need to **wait** up to 10 mintues and then **refresh** the page. You will be required to login to MOTAR.
{% endhint %}

#### Once the data is restored, you will be logged out of the system and will need to log back in.

If you have any questions or have issues restoring your data: [Contact Us!](/support/contact-us)

[^1]:


# Platform Manager (Third-Party Managed)

A **Platform Manager** is a company designated by the platform owner to manage the platform. This requires a *Third-Party Managed* license type. For example, a Defense contractor may select this platform configuration if they want to sell a product to the US Government that uses MOTAR as a component of their product offering. The Defense Contractor can manage the platform as the Platform Manager and the US Government can be the Platform Owner.

<figure><img src="/files/VlrBhBGOG63CG8miKPdl" alt=""><figcaption></figcaption></figure>

The "Company Name" field for the Platform Manger is set in your instances license file and cannot be updated. All other input fields can be modified.&#x20;

Additionally, **clicking** the "Add User" button the New Account flow to add users into this managing company. The company field will be preselected in the drop down on the new account modal.<br>

<figure><img src="/files/CqtLaXg5WVmnshBEwuV8" alt=""><figcaption></figcaption></figure>


# App Review

**Click** on the "App Review" tab found on the left side of the admin application to see all apps that have been submitted for review.

<figure><img src="/files/wo5egrrU74Av7rhs9OX1" alt=""><figcaption></figcaption></figure>

* **Click** the "Review" button next to the application that you want to review.

<figure><img src="/files/Z1saJkekijSP8FL0CFGf" alt=""><figcaption></figcaption></figure>

Once you either approve or reject an app, it will no longer be on this app review list. The creator will then see their *in review* status update accordingly.


# Users

**Click** on the "Users" tab found on the left side of the admin application.

<figure><img src="/files/OcRMDEj9qYJmcsvRUiUK" alt=""><figcaption></figcaption></figure>

The Users tab has multiple filter options to include:

{% tabs %}
{% tab title="Select User Type" %}

* Owning Company
* Partner or Contractor\*&#x20;
* Individual
* Managing Company&#x20;
  {% endtab %}

{% tab title="Filter By Role" %}

* Auditor
* Admin
* Creator
* No Role
  {% endtab %}

{% tab title="Filter By Studio Group" %}
List will contain platform "Studio Groups"
{% endtab %}

{% tab title="Filter By Partner or Contractor" %}
List will contain platform "Partners" or "Contractors"
{% endtab %}
{% endtabs %}

The active users tab will display current "active" platform users. The table contains:

### **Active Users Tab**

#### **Users**&#x20;

* Name/Company/Handle

#### **Moderation Status**

* Coming soon

#### **Role(s)**

* **Standard** - This role will give the user access to the platform as defined by the license.
* **Admin** - The Admin role will give the user access to the admin features of the platform.
* **Auditor** - The auditor role will give the user access to discover, download, use and distribute on hub listings.
* **Studio Lead** - A Studio Lead is a memeber of of one or more studio groups in which they can access and manage all of that studio's listings regardless of their user type or permissions.
* **Creator** - Given to users when they are added to a studio group. This gives them access to the Studio service where they can create listings.

{% hint style="warning" %}
For Government users, some restrictions apply as to who can be assigned a role, see below:
{% endhint %}

| User Type         | Standard Role | Admin Role | Auditor Role |
| ----------------- | ------------- | ---------- | ------------ |
| US Government     | Required      | Optional   | Optional     |
| Contractor-US Gov | Required      | Optional   | Optional     |
| Foreign Gov       | Required      | N/A        | N/A          |
| Public            | Required      | N/A        | N/A          |

#### **User Types (commercial or government)**

{% hint style="info" %}
Your instance will have either commercial or government user types. See details for each below.
{% endhint %}

User types are determined by the platform license.&#x20;

#### **GOVERNMENT - US Government User**

<figure><img src="/files/kFCDmcgA37UYdKD4V6h3" alt="" width="375"><figcaption></figcaption></figure>

A US Government user is defined as a user who is directly employed by the U.S. Government. This user type includes members of the Armed Forces, DoD Civilian employees, and employees of Federal Agencies or organizations, such as the CIA, Department of Veterans Affairs, or NASA

#### **GOVERNMENT -** US Government Contractor

<figure><img src="/files/OAizGcO77oQYwHKczXBb" alt="" width="375"><figcaption></figcaption></figure>

The US Government user type is defined as a user who is employed by a third-party company (private, public, owned, or tribal owned) that is contracted or paid by the Federal Government, or an agency/department of the Federal Government, to provide goods or services.

#### **GOVERNMENT -** Foreign Government

There are two types:

1. Foreign Military - A Foreign Military user refers to an individual who is a member of the armed forced of a country other than the United States.
2. Foreign Civilian - A Foreign Government Civilian is a user that is employed by a foreign government in a non-military and non-diplomatic role.

<figure><img src="/files/xbd8imHqJiKE3iNnhtDx" alt="" width="375"><figcaption></figcaption></figure>

<figure><img src="/files/pdLBm2EaIIV68xo5X5Zl" alt="" width="375"><figcaption></figcaption></figure>

#### **GOVERNMENT -** Public

<figure><img src="/files/lAmRCajnEAdSndrbT3u5" alt="" width="375"><figcaption></figcaption></figure>

A Public User is a user who does not meet the criteria for any of the above user types. Public users can only interact with existing content, and not create or remix content.

#### COMMERCIAL - Owning Company Member

<figure><img src="/files/nmvQF6Q0YAer83Lqy2td" alt="" width="409"><figcaption></figcaption></figure>

An Owning company member is an individual who works for the same company that owns the platform.

#### COMMERCIAL - Partner Company Member

<figure><img src="/files/W03OPYpHkSdHXwlYtRlv" alt="" width="409"><figcaption></figcaption></figure>

A Partner company member is an individual who works for one of the partner companies on the platform.

#### COMMERCIAL - Managing Company Member

<figure><img src="/files/MwjBNbPloh6KMtqMGxzk" alt="" width="409"><figcaption></figcaption></figure>

If your platform is managed by a third party you may have users that work for that particular company. You can differentiate them from any other partner company by designating them as members of the management company.

#### COMMERCIAL - Individual Member

<figure><img src="/files/OfqqlB4fMFILHUGM6kvy" alt="" width="409"><figcaption></figcaption></figure>

Individual members are members that you can allow onto your platform but don't have any associateion with a company.&#x20;

#### Actions

<figure><img src="/files/euaEfRDAhYRP2xHotJPe" alt="" width="72"><figcaption></figcaption></figure>

**Clicking** on the "edit pencil" in the actions column will take the admin to that users profile page where they can make changes.

***

####

#### Moderate


# Create User

**Click** the "+ Add New User" button to begin the *create new user flow*.

<figure><img src="/files/4NekHDpDeTKZyINz2pMX" alt=""><figcaption></figcaption></figure>

### Creating Users for Commercial and Government

{% hint style="warning" %}
The flow for commercial and government user types is essentially the same. User details, role  and summary. Government users have the additional sections for the agency and designation. Differences are shown below.&#x20;
{% endhint %}

#### User details:

{% columns %}
{% column %}
**Commercial**

* First / Last Name
* User Handle
* Title
* Primary Email
* User Type
  * Owning Company Member
  * Managing Company Member
  * Partner Company Member
  * None (Individual)
* Country
  {% endcolumn %}

{% column %}
**Government**

* First / Last Name
* User Handle
* Title
* Primary Email
* Military Grade
* Rank / Rank Abreviation
* Legal User Type
  * US Government
  * US Government Contractor
  * Foreign Government
  * Public
* Country
  {% endcolumn %}
  {% endcolumns %}

\
**Commercial** user details section of the add a new user flow:

<figure><img src="/files/5LlrFBvoEnjAQbnjeDGU" alt=""><figcaption></figcaption></figure>

G**overnment** user details section of the add a new user flow:

<figure><img src="/files/Idk4vbKC21KyelGy4jMS" alt=""><figcaption></figcaption></figure>

Fill out the required fields and **click "**&#x4E;ext" to move to the users role section. Each platform user will receive the standard permission by default. Make a role selection and click next. Note that some user types are only allowed certain roles [(see role(s))](https://app.gitbook.com/o/-LVczVIRnIFIRo5llDYg/s/VJV84grXWXSLppsAzVKx/~/edit/~/changes/480/motar-core-services/intro-to-core-services/admin/users#role-s)<br>

**Commercial and Government** role section of the add new user flow:

<figure><img src="/files/zEOZzoaGoyN3TbrQ1Mf7" alt=""><figcaption></figcaption></figure>

<details>

<summary>For <strong>Government Users Only</strong> - Agency and Designation Details</summary>

**Select** which Government Agency this account is associated with and **click** "Next".

<figure><img src="/files/Qf2kPfq1RBZqwkshBcK8" alt=""><figcaption><p>Government Agency</p></figcaption></figure>

**Enter** the details regarding the users government designation and **click** "Summary".

<figure><img src="/files/D8O7q7ZyJRfpo3QOpDKY" alt=""><figcaption><p>Designation Detail</p></figcaption></figure>

</details>

Once the role is set **click** "Next" to set the accounts temporary password within the summary view. After meeting the requirements **click "**&#x53;ummary".<br>

**Commercial and Government** summary section of the add new user flow:

{% hint style="warning" %}
User handle should be unique and can only contain lower characters, numbers and dashes. It should not No contain empty spaces.
{% endhint %}

<figure><img src="/files/OBg8YYskVkaUqtYI84pg" alt=""><figcaption></figcaption></figure>

**Click** "Create" user and you will now see that user on the active users tab.&#x20;

<figure><img src="/files/Mgnia54ylcVo1NaJEC8b" alt=""><figcaption></figcaption></figure>

Repeat the process for any additional users.


# Bulk Upload - Users

## Bulk Upload

You can quickly add multiple users to your workspace by uploading a CSV file. The number of users you can import at once is determined by your current user cap.

* **Navigate** to the User tab and **click** Import Users

<figure><img src="/files/dsv7vDnTHbqepV4PFLem" alt=""><figcaption></figcaption></figure>

* A warning will pop up

<figure><img src="/files/ABRdQgA7LmqT9o17h9GW" alt="" width="375"><figcaption></figcaption></figure>

* You are required to download the current User Report before importing more users.&#x20;
  * Click Download User Reports
  * A CSV of a current users will download.

<figure><img src="/files/KEXJKH9XH0wqQ9G0a3Y6" alt=""><figcaption></figcaption></figure>

* The Import button will unlock after downloading the report
* Click Import More Users
* You can download a template CSV for bulk importing

<figure><img src="/files/AaPhWmZWzPUlSMmMdy0R" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}

## WARNING

To ensure your import does not fail, follow the template guide for required fields.&#x20;
{% endhint %}

* Enter a temporary password into the space provided. All new users will receive the same password and will be required to change it upon first login.
* Select and upload your CSV
* Your file will be scanned and compared to your active users, if you will user limits, you will be alerted

<figure><img src="/files/WK1uowtAMD3XVJRZFfkx" alt=""><figcaption></figcaption></figure>

* If not issues are found, the Import \[#] Users button will be enbled
* **Click** Import \[#] Users
* During import, you will see a progress bar

<figure><img src="/files/pfkgRptklVkcP6H7CfPT" alt="" width="375"><figcaption></figcaption></figure>

* You will also see progress at the bottom right of the screen, this applies to the entire platform and will show for all admins currently logged in.

<figure><img src="/files/Bk7gm6mGgE4BB2BIOcrT" alt="" width="351"><figcaption></figcaption></figure>

* When the import is comlete, you will see details on the import&#x20;

<figure><img src="/files/M8bcx0Wg5T0ziIeNjRZl" alt=""><figcaption></figcaption></figure>


# Managing Users

Admins have the ability to edit user details by clicking on the users tab on the left side of the admin application. &#x20;

The **Users** tab has multiple filter options to include:

{% tabs %}
{% tab title="Legal User Type" %}

* US Government
* Contractor-US Gov
* Foreign Gov
* Public
  {% endtab %}

{% tab title="Filter By Role" %}

* Auditor
* Admin
* Creator
* No Role
  {% endtab %}

{% tab title="Filter By Studio Group" %}
List will contain platform "Studio Groups"
{% endtab %}

{% tab title="Filter By Contractor " %}
List will contain platform "Contractor"
{% endtab %}
{% endtabs %}

## Active Users

The active users tab will display current "active" platform users. The table contains:\
\
**User Info**

* First / Last Name
* User handle

**Moderation Status**

The users current moderation status.

**Role(s)**

The users assigned roles within the platform.

**Account Type**

The users designated account type.

<figure><img src="/files/OcRMDEj9qYJmcsvRUiUK" alt=""><figcaption></figcaption></figure>

**Click** the "Edit" pencil under the actions column of any user to open their profile page.&#x20;

<figure><img src="/files/euaEfRDAhYRP2xHotJPe" alt="" width="72"><figcaption></figcaption></figure>

Here the admin can navigate and edit any of the following tabs in the users profile:

* Edit User
* Password
* Moderation - Coming soon
* Studio Groups
* Learner Record
* Deactivate User&#x20;

<figure><img src="/files/4FzV5I7GIa4yLQ5PykJT" alt=""><figcaption></figcaption></figure>

After making a change you must **click** "Submit Changes" to **save**.

<figure><img src="/files/EbBYJDIwwwjcHNx2p6sX" alt=""><figcaption></figcaption></figure>

### Password

Admin can reset a users password to a temporory one that will automatically have them reset once they log in using that temporary password.&#x20;

<figure><img src="/files/BFV8mdY4IAemy66KFIkp" alt=""><figcaption></figcaption></figure>

#### Studio Groups

A studio group is a collective of users who create, upload, and manage content on MOTAR. Assets on MOTAR are created and managed by the Studio Group, not by individuals (this prevents assets from being locked by an individual user). The Studio group can represent an entire organization or a specific part of an organization.

**Click** the "Add to Studio Group" button to bring up the *add user to stidio group* modal.

<figure><img src="/files/2IHTjnEvCXck82qxqBz8" alt=""><figcaption></figcaption></figure>

**Select t**he studio group you wish to add the user to and **Click** the "Add" button. You can also type the studio group's name.

<figure><img src="/files/q0h7n6MTQZxb4X0OAt8z" alt=""><figcaption></figcaption></figure>

Once a user is added to a studio group, they will automatically be assigned the [creator role.](https://app.gitbook.com/o/-LVczVIRnIFIRo5llDYg/s/VJV84grXWXSLppsAzVKx/~/edit/~/changes/480/motar-core-services/intro-to-core-services/admin/users#role-s)

<figure><img src="/files/9MnV6GwpFwLR2cj2Tyh7" alt=""><figcaption></figcaption></figure>

#### Deactivate&#x20;

**Click** on the "edit pencil" next to the user whom you want to deactivate. The admin user will be redirected to the "edit view".

![](/files/lMCjLXmk8jZIVLOyU9kI)<br>

From the edit view tab, **Click** on the "Deactivate User" tab. On this view the admin user can "deactivate" an "active" platform user. This action will deactivate the user and list the user to the "deactivated users" tab within the users menu.&#x20;

**Select** the "Deactivate Account" input field, **Type** "Deactivate Account" and **Click** "Deactivate"

<figure><img src="/files/tRvPJ6vJgzJrhPvDUByj" alt=""><figcaption></figcaption></figure>

**Select** the "Deactivate Button" to complete the flow.

## Deactivated Users

The deactivated users tab will display deactivated platform users. On this view the following is visible to the admin:

* User Info
* Deactivated "status chip"
* Activate User button

### Activate User

**Select** the "Activate User" button to "*activate*" the user again! This will move the user back to the "Active Users" tab.&#x20;

After reactivation the user can login to the platform again.

<figure><img src="/files/Bi7Jm1Dgu6tjoq2iUBIs" alt=""><figcaption></figcaption></figure>

Changing or Removing Partner Company

To change or remove a user from a Partner company, see [Managing Users](/motar-core-services/intro-to-core-services/admin/partners-or-contractors/managing-users)


# Reports

A dedicated workspace for tracking organizational knowledge and asset engagement.

**Click** on the "Reports" tab found on the left side of the admin application.

<figure><img src="/files/vSmtYG9UXUewLyfRdxcm" alt=""><figcaption></figcaption></figure>

* Search or use the dropdown to select an asset
* **Click "**&#x47;enerate Report"

<figure><img src="/files/KWvfhzp2g52UrM5LEbA0" alt=""><figcaption></figcaption></figure>

* Filter by users, studio groups, or partners/contractors

<figure><img src="/files/SasDkUYCA6d7MYUX7IPj" alt=""><figcaption></figcaption></figure>

* **Click "**&#x44;ownload Results"
  * Report will generate and automatically download.


# Studio Groups

**Click** on the "Studio Groups" tab found on the left side of the admin application.

<figure><img src="/files/bZKvjWiHnd6e8fi4SKxg" alt=""><figcaption></figcaption></figure>

The **Studio Groups** tab supports filtering through search.

## Active Studio Groups

The active studio groups tab will display current "*active*" studio groups. The table contains:

* Studio Group Info
  * Name
  * Phone Number
  * Email
* Members Count
* Sandbox Listings Total
  * Visible
  * Total
* Production Listings Total
  * Visible&#x20;
  * Total
* Actions
  * Edit Partner Details
  * View Users
  * Vist Listings
  * View Analytics

## Deactivated

The deactivated tab will display "*deactivated*" studio groups. On this view the following is visible to the admin:

* Name
  * Studio Group Name
  * Phone Number
  * Deactivated Status Chip
* Actions
  * Activate Partner button


# Add Studio Groups

**Click** the "+ Studio Group" button to add a new group.

<figure><img src="/files/bZKvjWiHnd6e8fi4SKxg" alt=""><figcaption></figcaption></figure>

The button will launch the Add Studio Group Modal. The admin is required to fill in the fields shown on the modal below to create a new studio group.

<figure><img src="/files/uWMoPN9oisxjP0zla4HW" alt=""><figcaption></figcaption></figure>

After filling out the required fields, **Click** the "Add" button to create the desired studio group.


# Modify Studio Groups

**Click** on a studio group to open the studio group page to see:

* Details
* Users
* Listings

### Details

The details tab is open by default and it is here that you can edit the studio groups.

<figure><img src="/files/Uxa0bs2Gu2FrGB4O5lOw" alt=""><figcaption></figcaption></figure>

**Click** the "Edit" button to modify items and then save your changes.&#x20;

### Users

Users who have been added to studio groups are under the users tab. Here you can toggle on if that user should be a lead, you can view the user details which takes you to the [users profile](https://app.gitbook.com/o/-LVczVIRnIFIRo5llDYg/s/VJV84grXWXSLppsAzVKx/~/edit/~/changes/480/motar-core-services/intro-to-core-services/profile) page or you can remove that user from the studio group.&#x20;

A **Studio Lead** is a member of one or more studio groups in which they can access and manage all of that studio's listings regardless of their user type or permissions.

<figure><img src="/files/o7BtoyKAYmwO4rEUrXB1" alt=""><figcaption></figcaption></figure>

To add a new user, **click** the "Add New User" button and select users from the Add User to Studio Group modal. Simply **click** "+ Add" next to their name.&#x20;

<figure><img src="/files/CddkXDPBLmiLWU3QAxIE" alt=""><figcaption></figcaption></figure>

You can add multiple users at the same time by **clicking** the "+ Add" button. If you change your mind, simply **click** the "Remove" button next to their name.&#x20;

<figure><img src="/files/95MBvFjlAeIFUmnrO7N3" alt=""><figcaption></figcaption></figure>

The user can always be added back into the group.&#x20;

{% hint style="warning" %}
Studio groups must maintain at least one **studio group lead** at all times. You must first assign a new lead if you wish to remove the only one currently in that role first.
{% endhint %}

## Listings

All listings that were made under that studio group show up on the listings tab of the studio group page. This list shows the name of the listing, the type, and who created it.&#x20;

<figure><img src="/files/AghlQ64IYaUwSAV8e4eA" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Listings can not be removed from this page. Users must go to the studio service and delete the listing from there.
{% endhint %}


# Deactivate/Reactivate Studio Groups

A quick guide on deactivating studio groups.

**Click** the :pencil2:  icon to Edit the Studio Group.

<figure><img src="/files/cRdaJrIPZ55xCfcbGnOh" alt=""><figcaption></figcaption></figure>

The Studio Group Details page will open.

**Click** on the '<mark style="color:red;">**Deactivate Studio Group**</mark>' link.

<figure><img src="/files/CQKsXlKu5YekTId3g1G1" alt=""><figcaption></figcaption></figure>

The studio will now be <mark style="color:red;">**deactivated**</mark>.&#x20;

You will be **returned** to the Active Studio Groups page.&#x20;

All Deactivated Studio Groups are found in the '**Deactivated**' tab.

### Re-Activate Studio Group

**Click** the "Activate Studio Group" button to "re-activate" a studio group. Clicking this button will move the group from the Deactivated tab back to the Active Studio Groups tab.

<figure><img src="/files/y1FWDFZRGApQX8wLBxqE" alt=""><figcaption></figcaption></figure>


# Partners or Contractors

A guide on how to manage Partners\* in your Organization.

{% hint style="info" %}
\***Partners (commercial) or Contractors (government)** are determined by your license type and they function the same. The documentation below we will reflect the commercial partner side, however, understand, that if you have a government instance you will see contractors in lieu of partners.&#x20;
{% endhint %}

**Click** on the "+ Partners\*" tab found on the left side of the admin application.

<figure><img src="/files/syLdvA2PfqFeITLFBWPR" alt=""><figcaption></figcaption></figure>

The *Partners***\*** tab supports filtering through search and will display current "active" partner\* accounts in a table that contains:&#x20;

* Partner\* Information
  * Name
  * Phone
  * Contact Email
* Needs Attention notification
* Partner\* Members
* Actions
  * Edit
    * Edit Partner\* details
    * Deactivate Partner\*
  * View user list

The *Deactivated* tab will display any deactivated Partners\*. On this view the following is visible to the admin:

* Name
  * Partner\* Name
  * Phone Number
  * Deactivated Status Chip
* Actions
  * Activate Partner\* button

<figure><img src="/files/3z2f1o2N7R5p3jFJJ5YA" alt=""><figcaption></figcaption></figure>


# Active Partners

A guide on how to add Active Partners\* to your Organization.

{% hint style="info" %}
\***Partners (commercial) or Contractors (government)** are determined by your license type and they function the same. The documentation below we will reflect the commercial partner side, however, understand, that if you have a government instance you will see contractors in lieu of partners.&#x20;
{% endhint %}

**Click** the "+ Partner\*" button to add a new Partner\* company.

<figure><img src="/files/Te8sf9xVt7XPtsOdClRk" alt=""><figcaption></figcaption></figure>

The button will launch the Add Partner\* Company Modal. The admin is required to fill in the fields shown on the modal below to create a new Partner\* Company.

<figure><img src="/files/4bh1yoZAfbtelC9uz362" alt=""><figcaption></figcaption></figure>

After filling out the required fields, **Click** the "Add" button.

### Editing Partners\*

**Click** the ✏️ icon to access that Partner\*.&#x20;

<figure><img src="/files/4pdUcTy6MTKCUQM7lj2y" alt=""><figcaption></figcaption></figure>

The pencil opens that Partners\* page where you have the option to edit details or deactivate.

<figure><img src="/files/wq4UfkZ5QFB3J1pzdyFK" alt=""><figcaption></figcaption></figure>

**Clicking** <mark style="color:$danger;">**Deactivate**</mark> will prompt you with a modal to move this Partner\* to the deactivated tab.

<figure><img src="/files/KDu7hwKtdihqrFc9kA26" alt=""><figcaption></figcaption></figure>

**Type** "Deactivate Partner\*" in the text box.

**Click** the "Deactivate" button.

All Deactivated Partners are found in the '**Deactivated**' tab.

***


# Deactivated

A quick guide of deactivated Partners\*.

The deactivated tab shows all Partner\* companies that have been deactivated on the platform. From here you can search for a specific Partner\* or reactivate a Partner\* back to the Active Partner\* tab.

<figure><img src="/files/GoSTV1CLLpxltwog7dTI" alt=""><figcaption></figcaption></figure>

### Activate Partner\*

**Clicking** the "Activate Partne&#x72;**\*"** button will "re-activate" the Partner\* and move them from the Deactivated tab back to the Active Partner\* tab.


# Managing Users

Partner Group users are managed from the Partners section rather than the Users screen.

### Adding a User to a Partner Group

1. Navigate to **Partners** in the left sidebar
2. Select the Partner Group
3. Open the **Users** tab
4. Select **+ User**
5. A modal will appear listing all users not currently assigned to a Partner Group
6. Select the user and click **Add**

{% hint style="info" %}
Each user can only belong to one Partner Group at a time. Users already assigned to a Partner Group will not appear in this list.&#x20;
{% endhint %}

***

### Changing a User's Partner Organization

A user's Partner Organization can be changed at any time. However, this is managed from the **Partners** section rather than the Users screen.

{% hint style="info" %}
If a user is already assigned to a Partner Group, they must be removed from their current group before they can be added to a new one.
{% endhint %}

#### Remove the user from their current Partner Group

* Navigate to **Partners** in the left sidebar
* Select the user's current Partner Group
* Open the **Users** tab
* Locate the user and select **Remove**

#### Add the user to the new Partner Group

* Navigate to the new Partner Group
* Open the **Users** tab
* Select **Add User**
* The user will appear in the list and can be added to the new group

{% hint style="warning" %}
Removing a user from a Partner Group does not delete the user account. The user will remain in the system and can be reassigned to any Partner Group at any time.&#x20;
{% endhint %}


# Lists

A dedicated workspace for tracking organizational knowledge and asset engagement.

**Click** on the "Lists" tab found on the left side of the admin application to see

* Hardware
* API Keys

### Hardware

The hardware type can be configured to what you would like your apps to be able to use on their distribution. Any visible options on this list will be selectable to the user when creating a distribution.&#x20;

<figure><img src="/files/QE9eMhOT45UjHqqYD99y" alt=""><figcaption></figcaption></figure>

**Clicking** "Add Hardware" at the bottom of the screen will open up the new hardware category modal

<figure><img src="/files/Deoo8CebNdcgwwUTtX1V" alt=""><figcaption></figcaption></figure>

Fill in the hardware name and upload a thumbnail. **Click** "Add" and your new hardware category will show at the bottom of the existing list. You must add a subelement under the category.

<figure><img src="/files/FRoEWigOHuRgRaHrGGRg" alt=""><figcaption></figcaption></figure>

**Click** the "Add Sub Element" button to and fill out the information for a subelement and then **click** "Add".

<figure><img src="/files/iK3prB5M3C69XKn8ZSNb" alt=""><figcaption></figcaption></figure>

Your new sub element will be added

<figure><img src="/files/wOScC2l3sicqTKY2RRWr" alt=""><figcaption></figcaption></figure>

### API Keys

An **API key** (Application Programming Interface key) is a unique code used to identify and authenticate an application or developer when it makes a request to an API. It functions like a digital ID badge or a secret token, ensuring that only authorized programs can access the API's services

<figure><img src="/files/YzDagrKuhiIWurXOqvFy" alt=""><figcaption></figcaption></figure>

**Click** "+ New Key" to generate a new key at the bottom of the list.

API keys can be made active or inactive using the toggle.


# Configuration

A dedicated workspace for tracking organizational knowledge and asset engagement.

There will be slight differences on the configure platform page depending on the environment of your instance (commercial or government).&#x20;

**Click** on the "Configuration" tab found on the left side of the admin application to configure

* Data marking Support
* Support Email
* Documentation Redirect
* AI Engine Capability
* Record Importing
* [Login Requirements](https://app.gitbook.com/o/-LVczVIRnIFIRo5llDYg/s/VJV84grXWXSLppsAzVKx/~/edit/~/changes/480/motar-core-services/intro-to-core-services/admin/configuration/single-sign-on-sso)
* [MOTAR 3D](https://app.gitbook.com/o/-LVczVIRnIFIRo5llDYg/s/VJV84grXWXSLppsAzVKx/~/edit/~/changes/480/additioinal-features/motar-3d)

### Configure Commercial&#x20;

<figure><img src="/files/jrGzkeGb0oAjGNVT3PWb" alt=""><figcaption></figcaption></figure>

### Configure Government

<figure><img src="/files/xonker2gN2ey73hQbcNP" alt=""><figcaption></figcaption></figure>


# Single Sign On (SSO)

How to configure MOTAR to use Single Sign On

## SSO Configurations

For the purposes of this demo we will walk through setting up Google's single sign on. You can do this with any of the following by visiting their site and following their specific instructions:

* Google (demonstrated below)
* Linkedin
* Apple
* Facebook
* Meta

### Configuring Google SSO for the Platform

{% hint style="warning" %}
To enable Google Single Sign-On (SSO) for your platform instance, an admin must complete the following steps.
{% endhint %}

#### Prerequisites

1. **Admin access** – You must be logged in as a platform administrator.
2. **Google account** – Ensure you have a Google account to access Google Cloud.
3. **Google Cloud project** – You need a project in the [Google Cloud Console](https://console.cloud.google.com/).
   * Follow Google’s guide on creating a project if you do not already have one.
   * You will need to create credentials for OAuth 2.0 to obtain a **Client ID**. Refer to Google’s OAuth documentation for detailed instructions.
     * <https://developers.google.com/identity/protocols/oauth2>

{% hint style="danger" %}
Google documentation and steps are subject to change.
{% endhint %}

<figure><img src="/files/P9hPRtHFN6GIlksgOKzL" alt=""><figcaption></figcaption></figure>

#### Platform Configuration

1. Navigate to **Platform Config / Login Requirements** in the admin interface.
2. Navigate to Configure Platform on the left side under Admin
   1. **Check** "Google" as your authentication method.

<figure><img src="/files/VBSfj0Kmct6O2ibcc8XC" alt=""><figcaption></figcaption></figure>

Enter the following details for Google:

* **Google Client ID** – Copy this from your Google Cloud project’s OAuth credentials.
* **Login Service Domain** – The domain used for your Google SSO login, read-only.
* **Click** "Save" to apply the changes.

<figure><img src="/files/02BBpP9PmrWkY9vQ45P4" alt=""><figcaption></figcaption></figure>

Once saved, your platform will use Google SSO for user authentication. Users will be redirected to Google to log in.


# Devices

Securely authenticate your XR headset.

## MOTAR Devices Overview

MOTAR Devices allows users to sync a device to their MOTAR account.  Once the initial sync is complete, the user will create a pin code to simplify authentication of the synced headset during future uses.&#x20;

<figure><img src="/files/rMvyfM9QcWzVSopJvIn9" alt=""><figcaption><p>MOTAR Device Sync</p></figcaption></figure>

## **Access**

MOTAR Devices service is available to users with a MOTAR account.

<figure><img src="/files/0uiKHIiJlJmrNEAfAOIR" alt=""><figcaption><p>Device on the Service Dropdown</p></figcaption></figure>

The Devices page on the web can be found by navigating to the Services drop down and **selecting** "Devices"

<figure><img src="/files/sTXu5SL93ArwAUFi6O2U" alt=""><figcaption></figcaption></figure>

{% content-ref url="/pages/Azc4PYQcub0D8bgLo1ES" %}
[MOTAR 3D](/motar-core-services/intro-to-core-services/devices/motar-3d)
{% endcontent-ref %}


# Device Syncing

### Sync to MOTAR Web

{% hint style="info" %}
The following steps use a VR Headset as a device example.
{% endhint %}

**Launch** the **MOTAR 3D Application** in the VR Headset.&#x20;

* When **MOTAR 3D** launches for the first time, you will be presented with the "Sync Device" screen. This allows users to sync their headset to their user profile in MOTAR.&#x20;
* Your MOTAR 3D version comes preloaded with your instance **URL.**

<figure><img src="/files/3nRNqQWhDifSRDnHycQC" alt=""><figcaption></figcaption></figure>

* Simply **login** to the URL generated *(devices.test.dynepic.net is shown in this example)* and enter the auto-generated code.

### Manual URL entry

You can also manually enter a MOTAR instance URL by **clicking** the "Sync to a different URL" link at the bottom of the screen.

This will open the URL entry input.&#x20;

* Enter the domain for your MOTAR Instance (example: motar.com)

{% hint style="info" %}
No need to include **http or www** in the address.
{% endhint %}

<figure><img src="/files/EbzXZXjN3JNFR4lpyu6q" alt=""><figcaption></figcaption></figure>

If your URL is entered correctly, MOTAR 3D will generate a **Sync Code**. This code is then entered into the devices page on your MOTAR Instance. &#x20;

<figure><img src="/files/MbAXwI17EJyMI4XrhJEw" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
The Sync Code will expire if the following steps are not completed in the allotted time. The time remaining is displayed below the 8-digit sync code in the VR Headset modal.
{% endhint %}

* On a computer or mobile web browser, **Login** to the "Motar Devices" service from a preferred browser window.

<figure><img src="/files/AN3osMuVZr622o9emlq0" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/idgr3pMg1QHavrR2z6cw" alt=""><figcaption></figcaption></figure>

* **Enter** the *Sync Code* that is displayed in the VR Headset into the Enter Sync Code from Device" field.

<figure><img src="/files/17qVyZwccf1HSVMaWUR5" alt=""><figcaption></figcaption></figure>

* **Click** "Sync Device"

A confirmation will be displayed confirming the device was synced successfully and you can return to the VR Headset.

<figure><img src="/files/djZrbrZODsooyXAypABR" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
If the VR Headset is not synced successfully, an error message will be displayed. The user may either **CLICK** the **TRY AGAIN** button to be returned to the **MOTAR DEVICES** screen.
{% endhint %}

In the VR Headset, a confirmation message will be displayed confirming the device was synced successfully.

<figure><img src="/files/cxhqw23AXUmORO0VATK5" alt=""><figcaption></figcaption></figure>

**Click "**&#x43;ontinue". If you've synced before you will be directed to the Hub on MOTAR 3&#x44;**.**&#x20;

<figure><img src="/files/6O1Fja7mTyKMWuiycULn" alt=""><figcaption></figcaption></figure>

From here, you can view MOTAR 3D compatible assets (which you have permissions for) and launch installed applications.&#x20;

{% hint style="warning" %}
Application installation may vary depending on your organization. Check with your administrator for details.
{% endhint %}

If this is your first type ever syncing your device, you will be promoted to create a pin code.

{% content-ref url="/pages/60eUMdLgar7KdX4aDYId" %}
[Device PIN Codes](/motar-core-services/intro-to-core-services/devices/device-pin-codes)
{% endcontent-ref %}


# Device PIN Codes

The MOTAR Devices service allows users to create and manage PIN Codes for synced VR devices.  This feature is currently in Beta and only available to specific vendors.

## Create a PIN Code in MOTAR Devices Service

{% hint style="info" %}
After a device has been synced, the user will be required to input a PIN code every time the synced device is used. &#x20;

To sync a device, please reference instructions found at the link below.
{% endhint %}

{% content-ref url="/pages/OoEKEpvcgyXhsE5Ai7Kb" %}
[Device Syncing](/motar-core-services/intro-to-core-services/devices/device-syncing)
{% endcontent-ref %}

<figure><img src="/files/AI06G355TH5nhw2bOt7k" alt=""><figcaption></figcaption></figure>

Once a device has been synced, **Login** to the "MOTAR Devices" Service to create a PIN code. The page can be accessed using the link below or by **selecting** "Devices" from the MOTAR Services dropdown menu.

<figure><img src="/files/8Xh6xgHj0DupAnYc04PP" alt=""><figcaption></figcaption></figure>

**Click** the "Create / Change Pin" button. The user will be redirected to the Pin Code management page.

<figure><img src="/files/8WcTVRqvTpyjnudr9aEi" alt=""><figcaption></figcaption></figure>

**Enter** a unique 4-digit Pin Code into the text field. **Retype** the previously entered Pin Codeinto the second text field. **CLICK** the **"Set Pin"** button.

<figure><img src="/files/XsJiGNBDZSNtNpYtSqAR" alt="" width="470"><figcaption></figcaption></figure>

A confirmation modal will be displayed, confirming the PIN was successfully set.  **Click** the "Dismiss" button.

The PIN Code is now available for use in the synced device.

## Use a PIN Code in Devices

{% hint style="info" %}
The following steps use a VR Headset as a device example.
{% endhint %}

**Launch MOTAR** in the VR headset. The following modal will be displayed prompting the user to enter their four digit PIN code.

<figure><img src="/files/exdg1WADMg6M9oOVeFi0" alt="" width="563"><figcaption></figcaption></figure>

**Enter** the unique Pin Code previously created in the MOTAR Devices service.

**Click** the "Confirm User Pin" button.

{% hint style="info" %}
If the incorrect PIN Code is entered, an error message will be displayed. The user will need to reset the PIN Code in MOTAR Devices service. Please see below for required steps.
{% endhint %}

<figure><img src="/files/em8QBpEOVoQBfHhZ1mD8" alt=""><figcaption></figcaption></figure>


# MOTAR 3D

A companion app to your MOTAR Instance.

<figure><img src="/files/x53N4CuDvtC5cD31BXCe" alt=""><figcaption><p>MOTAR 3D</p></figcaption></figure>

## Get MOTAR 3D

MOTAR 3D is available for download in the "Configure Platform" menu of the Admin service.

<figure><img src="/files/HmuUM0ISqyNRl8JHreyT" alt=""><figcaption></figcaption></figure>

There are two builds: **Meta Quest** and **Vive**. Each is customized for your platform during creation and includes your domain for device syncing.

Depending on organizational procedures, applications can be obtained in one of two ways:

* **Download Link** – Direct download from the platform. Can be installed to sideload to XR headsets.
* **Download URL** – A shareable link that can be integrated with third-party MDM solutions or provided to users for direct headset installation.

{% hint style="info" %}
The download URL is publicly accessible and can be acquired by an admin.
{% endhint %}

***

## Installing MOTAR 3D

How you install MOTAR 3D depends on your organization and XR device. MOTAR 3D is available for Meta Quest and HTC Vive (currently)

**Choose** your installation method below:

<details>

<summary>Meta Quest for Business</summary>

Guide to adding prebuilt apps to your Meta Quest for Business admin console.

{% hint style="danger" %}
**WARNING** : **Before** launching an app on a **Meta Quest** device, ensure your Meta Quest device is operating on at least **v76**. \
*Due to a bug in Meta Quest OS **v74** apps may not launch properly.*
{% endhint %}

### Prerequisites <a href="#prerequisites" id="prerequisites"></a>

This guide is for Meta Quest for Business admins and will walk you through the process of adding MOTAR 3D to the admin dashboard.

Your account must have an admin role assigned with relevant permissions before you can create an app in Meta Admin Center. If you are unsure of your access permissions, contact your Meta admin or visit [Meta’s Manage admin roles and product access](https://work.meta.com/help/327223042205658) page to learn more.

### Add an App <a href="#add-app" id="add-app"></a>

1. Go to [**https://work.meta.com/admin/products**](https://work.meta.com/admin/products) and login with your admin account.
2. To add an app from an APK file to your organization’s apps in Admin Center, click **Apps** icon in the left menu of Admin Center.
3. In Manage apps, click **+ Add App** in the top right
4. Pick **Externally hosted**
5. Add details
   1. **App name: MOTAR 3D**
   2. **Link to APK File: \[past URL link from Studio]**
6. Add visuals *(optional)*
   1. **Add Icon (right click on the image below and download)**

      <figure><img src="/files/SZu0FW0p7MWIA9M3Fewg" alt="" width="375"><figcaption></figcaption></figure>

</details>

<details>

<summary>Meta Quest Device - Developer Mode</summary>

{% hint style="danger" %}
**WARNING** : **Before** launching an app on a **Meta Quest** device, ensure your Meta Quest device is operating on at least **v76**. \
*Due to a bug in Meta Quest OS **v74** apps may not launch properly.*
{% endhint %}

### First Time Setup (Developer Mode)

1. Create a developer account with Meta. You can do this by going to this[ **link**](https://accountscenter.meta.com/) and completing their signup process.
2. Verify your developer account by providing a credit card or mobile number.
3. If you have not used your headset, complete the initial headset setup/first time user experience before continuing.
4. Install the Meta Horizon app on your phone and log in with your newly created Meta account. (This step is an optional part of the first time user setup in the headset and may have been completed previously.)
   1. Download for Android[ **here**](https://play.google.com/store/apps/details?id=com.oculus.twilight\&hl=en_US)
   2. Download for iOS[ **here**](https://apps.apple.com/us/app/meta-horizon/id1366478176)
5. Login to the headset using the same developer account.
   1. You may have to logout if your current account in the headset is not the same as the developer account setup in **step 1**.
6. Login to the phone app with the same developer account.
7. Connect your headset to the app if not completed during **step 3**.
8. From your phone, enable Developer Mode under the Headset Settings.
9. Open toolbar
10. You can find this option by going to **Menu > Devices > Pick the device you wish to use > Headset Settings > Developer Mode**. Toggle Developer Mode to **ON**

<figure><img src="/files/i8QC6cHJ7zrEHcd3CgYZ" alt=""><figcaption></figcaption></figure>

## How to Install an App

There are three ways\* to side-load an app onto the Meta Quest headset, using the **Meta Quest Developer Hub** (via Wi-Fi or link cable), the **SideQuest application**, or the **Command Line** (via a link cable).

### Meta Quest Developer Hub (MQDH)

* Follow Meta’s device setup guide[ **here**](https://developers.meta.com/horizon/documentation/unity/unity-env-device-setup/)
* The following steps may repeat portions of the Meta guide
* Download the Meta Quest Developer Hub(ODH)[ **here**](https://developer.oculus.com/downloads/package/oculus-developer-hub-win).
  1. Next, install it by double clicking on it and running through the installation wizard.
* Login with your developer account
* Connect your Meta Quest headset to your computer via the[ **Link Cable or AirLink**](https://www.meta.com/help/quest/articles/headsets-and-accessories/oculus-link/connect-with-air-link/?srsltid=AfmBOop5IuBcpgHpW2NYOZQCFW1ZaMB1pn-0WIjeGY4bfoTKG5cas3wS)
* After setting your device to **Developer Mode**, you can open up the **Developer Hub** app to view your "connected" device under the **Device Manager** tab.

<figure><img src="/files/pjNNJly1DNLalogLjXYk" alt="" width="271"><figcaption><p>MQDH <strong>Device</strong> <strong>Manager</strong></p></figcaption></figure>

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXewQ543WUwuYy8ZOr-1AQBgLAhvrygie8C7at3rn14ZyTZ7uuBXWNK9LWoH5U4UnR8aMkeGlEtkASptSmEXGvHfFbM7BZOkdN569vYXizFV4-o50L_HuSGXC8WaAVWzGvPEnOef?key=94UzjZoz3rxYBFT-uST1_cPz" alt=""><figcaption></figcaption></figure>

* You should see your device connected under the **Devices** tab. If you do not see your device and it is connected via a USB-C cable, click "**Set Up New Device**" and follow the on screen instructions.

<figure><img src="/files/lv7A5HBzGdfNaVzcrwoS" alt="" width="249"><figcaption><p>MQDH <strong>Devices</strong></p></figcaption></figure>

<figure><img src="/files/S4nywN5gDe9d9X45blBb" alt=""><figcaption><p>MQDH Device <strong>added</strong> but not connected.</p></figcaption></figure>

<figure><img src="/files/TltRy02UhtlaoXZr2LuG" alt=""><figcaption><p>MQDH Device <strong>connected</strong>.</p></figcaption></figure>

* Click the **“add build”** button to select and install your APK to the headset.

<figure><img src="/files/HsB6tbR4w2FuN6hFZFvq" alt=""><figcaption><p>MQDH <strong>add a build (APK)</strong></p></figcaption></figure>

* Your apk will now **install** on your Meta Quest 3.
* To launch the app, see [#launching-apps](#launching-apps "mention")

***

</details>

<details>

<summary>Vive Focus 3</summary>

## Manually Install an APK on a Vive Focus Device

MOTAR 3D is available for download here:

[https://dyn-downloads.s3.us-east-1.amazonaws.com/motar3d\_3-2-1\_vive.apk <br>](<https://dyn-downloads.s3.us-east-1.amazonaws.com/motar3d_3-2-1_vive.apk&#xD;&#xA;>)

{% hint style="warning" %}
Installing apps on your Focus 3 requires a USB-C cable. Plug the cable into your computer and then into the device. You may need to 'authorize' the computer in the headset.
{% endhint %}

**On Your Computer**

Once your computer is **connected** to your Focus 3, you should see the device folder in your computer file explorer.
\
Drag the **downloaded** MOTAR 3D to the Focus 3 "Downloads" folder. <br>

**On Your Focus 3**

Put on your Focus 3 and navigate to "Storage/Downloads" Click on the MOTAR 3D file and choose "Install"<br>

</details>

<details>

<summary>SideQuest</summary>

**SideQuest** is a 3rd party tool which allows installing software outside of the Meta Quest Store (ad hoc). SideQuest is community run and the developers work closely with Meta to allow developers a platform for showcasing their early work. Recently, Meta has allowed some integration with SideQuest via the Meta Quest Labs.

* Download the SideQuest application[ **here**](https://sidequestvr.com/setup-howto). Next, install it by double clicking on it and running through the installation wizard.
* Once installed, connect your headset to the computer via[ **Link Cable or AirLink**](https://www.meta.com/help/quest/articles/headsets-and-accessories/oculus-link/connect-with-air-link/?srsltid=AfmBOop5IuBcpgHpW2NYOZQCFW1ZaMB1pn-0WIjeGY4bfoTKG5cas3wS)
  * You should see your device in the upper left corner

<figure><img src="/files/IM0MPbiTYdNkpzBZKg1m" alt="" width="217"><figcaption><p>SideQuest with a Quest connected.</p></figcaption></figure>

* Click the “**Install APK**” button and select your APK

<figure><img src="/files/PkLmSgzXoXNIFkIrET9T" alt="" width="374"><figcaption><p>SideQuest <strong>Install APK</strong></p></figcaption></figure>

* The install status can be seen in the “**Running Tasks**” tab.

<figure><img src="/files/pUSNHrdTYHkr9lTJan34" alt="" width="374"><figcaption><p>SideQuest check <strong>running tasks.</strong></p></figcaption></figure>

<figure><img src="/files/CIttIVjq02THUSofkOHR" alt="" width="375"><figcaption><p>SideQuest current running <strong>task list.</strong></p></figcaption></figure>

</details>

<details>

<summary>Command Line ADB Install (Windows only)</summary>

### Command Line (via Link Cable)

#### Windows/PC Only

1. Install ADB Drivers from[ **here**](https://developer.oculus.com/downloads/package/oculus-adb-drivers/). ADB is the software that lets PCs transfer and installs apps onto Android-based devices like Oculus standalone headsets. When the download finishes, unzip the downloaded file folder. Now **right-click** on **android\_winusb.inf** and click **Install**. When prompted click open followed by yes to get a message that says, **"The operation completed successfully."**
2. Next, you need to download the SDK platform tools from[ **here**](https://developer.android.com/studio/releases/platform-tools). Extract the contents of the platform-tools folder to an easy-to-find folder on your PC, such as **C:\ADB\users\\"YourName"** by selecting **all** the contents of the folder and copying(CTRL+C) and pasting(CTRL+V) it into the new location.
3. Make sure your headset is connected to your PC via a link cable(or compatible USB cable).
4. Open the **Command Prompt.** Right-click on the Windows **Start** button at the bottom left of your screen and click **Command Prompt (Administrator)** or click on the windows icon and type "cmd" and press enter.
5. In the command prompt type "**adb**" and a string of text should pop up if you completed everything correctly, but this message will pop up if the ADB drivers and platform tools weren't installed properly: **'adb' is not recognized as an internal or external command, operable program or batch file**.
6. Type **"ADB devices"** to view **"List of devices attached"** with the device listed below(represented by a list of numbers and letters). It will most likely say "unauthorized" next to that so you will need to put on your headset and select **"Always allow from this computer"** or **"allow"** to allow your Oculus to connect to your PC. After this, in the command prompt, it should say **"device"** instead of unauthorized.
7. Install the app via command line by manually entering in the file path and app name or **copying the path**. To copy the path, hold shift, right-click on the APK file, and select "copy as path".
8. In the command prompt, type **adb install -r command** followed by the **full path** to the sideloaded app you want to install then press enter. It should say **"success"** in the command prompt if everything worked correctly. Example:

```
adb install -r C:\Users\YourName\Downloads\MyCoolNewApp.apk
```

</details>

## **MOTAR 3D Controls**

**MOTAR 3D controls** are accessed by ‘**looking**’ at your **left hand** watch.

<figure><img src="/files/vYMcjTkaLvcFnAj6ne0w" alt=""><figcaption></figcaption></figure>

This will open the MOTAR 3D **Control Panel**

<figure><img src="/files/JxSswpgRvHW5bICxP1Pm" alt=""><figcaption></figcaption></figure>

Options include:

* **Holodeck Assets** - Opens the Holodeck assets loaded in the scene.\*
  * The following CMI5 metrics can be viewed by selecting the asset and looking at the left panel for the following asset types:
    * Audio
    * Video

<figure><img src="/files/DX4TdmaY1HidmUDHp7eC" alt=""><figcaption></figcaption></figure>

* **Passthrough** (toggle) - Toggles the **passthrough** (if available on your headset)
* **Hub** - Opens the **Hub**.\*

\**Each menu will toggle the other.*

### Launching Apps

{% hint style="danger" %}
**WARNING** : **Before** launching an app on a **Meta Quest** device, ensure you have your Guardian activated and set to RoomScale. \
Due to Meta update **v74**, **inactive** Guardians and **Stationary** guardians may prevent apps from launching properly.
{% endhint %}

If an app is installed on your device and you have permissions to launch the app, you can launch directly from MOTAR 3D.

* **Select** the app from the Hub menu by **clicking** on the listing card.
* **Click** "Launch" from the menu on the right.

{% hint style="warning" %}
If an app is launchable, the "Launch" button will be enabled. Otherwise, you will not be able to launch the app.
{% endhint %}

<figure><img src="/files/TD0evkEBO1Ypgj4XWBhX" alt=""><figcaption></figcaption></figure>

***

### Multiplayer Session

Currently, MOTAR 3D allows multi-user collaboration. If your MOTAR License has the multiplayer feature enabled\*, simply login to MOTAR 3D. Anyone in your organization (using the same URL to sync their device) will be able to join you in the Holodeck!\
\**Currently only available for Commercial Licenses.*

<figure><img src="/files/BlhVVtqyUR3A00yrTDyO" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Not sure what license features you have? Check with your Platform Admin or [Contact Us!](/support/contact-us)
{% endhint %}

***

### AI Chat & Query (Beta)

With the new AI Chat (beta) you can query our secure, permissions aware AI.&#x20;

* **Open** the control menu and **click** the AI button

<figure><img src="/files/vvLnJ0b3AYn6X8UeGwvq" alt="" width="563"><figcaption></figcaption></figure>

* A new AI chat window will **open**
* **Click** the 'mic' icon to speak a question\*

<figure><img src="/files/qn0EFYvyKJ0HWLDbsKmP" alt="" width="563"><figcaption></figcaption></figure>

{% hint style="warning" %}
In this beta version, speach to text on some devices may take a few moments to process.
{% endhint %}

<figure><img src="/files/09FDR6WhMQfPWH8NFzVa" alt="" width="563"><figcaption></figcaption></figure>

* The AI will answer your question and return information about assets which you have permissions for.

<figure><img src="/files/9eIoClRjkPU2JYA6uWpp" alt="" width="563"><figcaption></figcaption></figure>

***

### Additional Features

#### Using your PIN

When entering a sync code on the Devices page, you are given the option to create a pin code.

**Syncing** your **device** stays "active" for **24 hours**. This allows you to continue using your device without the need to sync. Simply **enter** your **PIN** and continue.

<figure><img src="/files/AI06G355TH5nhw2bOt7k" alt=""><figcaption><p>Pin Entry</p></figcaption></figure>

Successfully entering a PIN will allow you to continue in the application without needing to enter a URL/sync from the web.

<figure><img src="/files/cxhqw23AXUmORO0VATK5" alt=""><figcaption><p>Welcome Screen after Sync</p></figcaption></figure>

#### Saved URLS

URLS entered into the device sync screen are saved locally to make syncing even faster.

<figure><img src="/files/xcQrAB9wyv9jpylupcT7" alt=""><figcaption><p>Saved URL List</p></figcaption></figure>


# MOTAR Holodeck

The MOTAR 3D companion app for Meta Quest allows you to view and interact with the assets you have uploaded. Simply launch MOTAR 3D.

<figure><img src="/files/5Khcx91hF8niBFa70vqk" alt=""><figcaption></figcaption></figure>

After [Syncing your headset](/motar-core-services/intro-to-core-services/devices/motar-3d#device-syncing), you will be brought to the Hub on **MOTAR 3D** showing all assets compatible with **Holodeck**.

### **Controls**

**Controls** are accessed by ‘**looking**’ at your **left hand** watch.

<figure><img src="/files/vYMcjTkaLvcFnAj6ne0w" alt=""><figcaption></figcaption></figure>

This will open the MOTAR 3D **Control Panel**

<figure><img src="/files/JxSswpgRvHW5bICxP1Pm" alt=""><figcaption></figcaption></figure>

Options include:

* **Holodeck Assets** - Opens the Holodeck assets loaded in the scene.\*
* **Passthrough** (toggle) - Toggles the **passthrough** (if available on your headset)
* **Hub** - Opens the **Hub**.\*

\**Each menu will toggle the other.*

### Loading Asset Listings into Holodeck

**Open** any asset listing in the Hub

<figure><img src="/files/oSxMDObuW6dFzzfWUHuk" alt=""><figcaption></figcaption></figure>

* On the listing details compatible assets will have a "View in Holodeck" button.
* **Click** the "View in Holodeck” button located to the right of an asset listing.

<figure><img src="/files/fdIv9vM138F1Yo8xaMVE" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
Not all listings are compatible with Holodeck.&#x20;

Only 3D models with a 3D preview GLB or GLTF and standard videos are currently compatible.
{% endhint %}

* Videos, audio, and images load in a Pop-out window.&#x20;
* All 3D models will load on a pedestal in the center of the space.

<figure><img src="/files/80vfjnbLcKfHcwDFQgfu" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
Large models will load in scaled down. To see a model actual size, simply open the Holodeck Assets menu and choose "Scale 1:1"
{% endhint %}

### **Holodeck Asset Listings**

To manipulate objects in the Holodeck, open the control menu and **select** "Holodeck Assets".

<figure><img src="/files/zsBPrzfNH7QsSWSpIb8u" alt=""><figcaption></figcaption></figure>

The Holodeck Assets menu will show all objects currently loaded into the Holodeck.

Expanding the dropdown will show options for 3D models:

* Unlock Movement - Default of ON - allows the model to be moved in space.
* Scale 1:1 - Scales the model to the original dimensions
* Loop Animation - If animations are saved with the model, toggling this will loop the animation.
* Cycle Animation - If animations are saved with the model, toggling this will cycle through all available animations.
* Animation Selection - A selectable list of available animations.
* Reset Model - Resets the model to the pedestal and scales down.

### Asset Metrics

The following CMI5 metrics can be viewed by selecting the asset and looking at the left panel for the following asset types:

* Audio
* Video

<figure><img src="/files/9uZU6YWIBeMvQoTUU9tl" alt=""><figcaption></figcaption></figure>

### Launching Applications

<figure><img src="/files/ddILXkE3GFebMAl3P5Lk" alt=""><figcaption></figcaption></figure>

If an app is **installed** on the **device**, the Listing button will show “**Launch**” and the app can be launched with Holodeck.

{% hint style="danger" %}
**WARNING** : **Before** launching an app on a **Meta Quest** device, ensure you have your Guardian activated and set to RoomScale. \
Due to Meta update **v74**, **inactive** Guardians and **Stationary** guardians may prevent apps from launching properly.
{% endhint %}

<figure><img src="/files/TD0evkEBO1Ypgj4XWBhX" alt=""><figcaption></figcaption></figure>


# MOTAR SDK for Unity

<figure><img src="/files/WFIHTu2ISOXhF5vTmr9d" alt=""><figcaption></figcaption></figure>

MOTAR's SDK for Unity makes it incredibly easy to develop training apps across devices and have them instantly feature the MOTAR login and User Profile Access.&#x20;


# Installation

The MOTAR SDK for Unity is compatible Unity Editor version **2022.3+ LTS**

The **MOTAR SDK for Unity** is hosted on a publid NPM Registry and is **installed** via the Unity Package Manager as a **Scoped Registry.**

{% hint style="info" %}
For a detailed guide on installing packages via a Scoped Registry, see: [Detailed Scoped Registry Instructions](/motar-core-services/intro-to-core-services/devices/motar-sdk-for-unity/installation/detailed-scoped-registry-instructions)
{% endhint %}

<table data-header-hidden><thead><tr><th></th><th width="454"></th><th data-hidden></th></tr></thead><tbody><tr><td><strong>Name</strong></td><td>MOTAR</td><td></td></tr><tr><td><strong>URL</strong></td><td>https://registry.hub.motar.com</td><td></td></tr><tr><td><strong>Scope(s)</strong></td><td>com.motar</td><td></td></tr></tbody></table>

## Samples

The MOTAR SDK for Unity includes some sample packages in the **Samples** section under the MOTAR entry in the Package Manager. These include:

* Device Sync
* Avatar
* Learn to Fly UFO (URP Only)

To **install** these samples:

* **Select** the MOTAR Package in the Package Manger
* **Click** "Samples"
* **Click** "Import" on the samples you would like to **install**.

<figure><img src="/files/QqcOYNdaFT3PYMqfaua3" alt=""><figcaption></figcaption></figure>

*Details about these sample packages are listed in the sections below.*

### Device Sync

{% hint style="danger" %}
**Required sample!**

Device Sync is **required** if your application will sync with the MOTAR Instance hosted by your organization.&#x20;
{% endhint %}

**Device Sync** allows users to sync their headset with the MOTAR Instance hosted by your organization.&#x20;

*When a user syncs their device, you can access user information via the* [*MOTAR User Profile Class*](/motar-core-services/intro-to-core-services/devices/motar-sdk-for-unity/motar-classes) *and leverage user data in your applications.*

#### Installing Device Sync

Device Sync is a Sample package located in the Dynepic/MOTAR SDK registry.

* After **installing** the SDK, **go to** the Package Manager
* **Click** the Dynepic / MOTAR SDK package entry
* **Click** "Samples" and locate **Device Sync**
* **Click "**&#x49;nstall"

In your project you should now see a **Samples** folder containing the MOTAR SDK Device Sync files.

After device sync imports, the sample will be **installed** in&#x20;

* **Assets\Samples\MOTAR SDK\\\<version>\Device Sync**&#x20;

Included with the scripts is the scene **MOTARDeviceSyncAndAuthentication**

{% hint style="warning" %}
If you don't have **TextmeshPro** installed in your project, it will install automatically request an install when opening the Sync scene.

* From your project window, navigate to Assets -> Samples -> MOTAR SDK -> \[version #] -> Device Sync -> Scenes.
* Double click and load “MOTARDeviceSyncAndAuthentication”.
  {% endhint %}

The **MOTARDeviceSyncAndAuthentication** scene allows users to log into their MOTAR accounts and authorize the headset.

The scene is automatically inserted into your Unity Build settings Scenes as the **FIRST** (0) scene.

<figure><img src="/files/yXIBchgNx8asLGpTQr2p" alt="" width="482"><figcaption></figcaption></figure>

Generally, you should **authenticate** your users before they enter your application. If your app requires a different scene to be the first launched, simply move the **MOTARDeviceSyncAndAuthentication** to the required order.&#x20;

{% hint style="warning" %}
Moving **MOTARDeviceSyncAndAuthentication** means your application will not be authenticated or synced with MOTAR until the scene is launched. Attempts to access user information will be impacted.
{% endhint %}

### Avatar

The MOTAR Avatar **sample** makes development even easier with out-of-the-box XR features.&#x20;

With the Avatar sample package you get:

**MOTAR\_Player -** This XR Rig prefab is wired up ready for you applications. Show user's name, profile image. Locomotion, Interaction, and Camera fading are all built in and accessible.

**MOTAR\_TeleportAnchor -** Add teleportion anchors to your scenes

**AvatarDemoScene -** This demo scene shows you examples of the MOTAR Avatar, object interactions, UI, and Locomotion.&#x20;

### Learn to Fly UFO

The *Learn to Fly UFO* sample package is a fun and interactive way to explore the features of the MOTAR SDK. Whether you're new to Unity or just curious, this sample project guides you through the basics of integrating MOTAR Core and Avatar features from start to finish. **No prior experience required**—just dive in and start experimenting!

{% hint style="warning" %}
The UFO project is meant for Unity **beginners** to see how easy it can be to create an app using the MOTAR SDK for Unity.
{% endhint %}

Follow the tutorial: [Broken mention](broken://pages/eP6dJt0EMPCMrJFh5eM5)


# Detailed Scoped Registry Instructions

The following will guide you on how to install MOTAR SDK for Unity if you have never installed via a Scoped Registry.

## How to install the MOTAR SDK for Unity via Scoped Registries

* **Click** on "Edit" -> Project Settings

<figure><img src="/files/u9sD6aysjXWv2IxdK6dj" alt=""><figcaption></figcaption></figure>

* From the Project Settings window, **click** on "Package Manager"

<figure><img src="/files/f4Qkuh6OApwO3sKSfD1f" alt=""><figcaption></figcaption></figure>

* Add a new scoped registry with the following:
  1. **Name**: MOTAR
  2. **URL**: <https://registry.hub.motar.com>
  3. **Scope(s)**: com.motar

<figure><img src="/files/rWtEEniuhETZ8Th1tZfh" alt=""><figcaption></figcaption></figure>

* **Click** "Save/Apply"
* Close the Project Settings window
* **Click** on "Window" -> Package Manager

<figure><img src="/files/xP8o41fHBEYzg31TzW51" alt=""><figcaption></figcaption></figure>

* From the Package Manager window, **click** on the second drop down and switch it from “Packages: In Project” to “My Registries”.

{% hint style="warning" %}
Unity may take some time to load 'My Registries' after adding a scoped registry. If you do not see 'My Registries', wait a few moments and then retry the dropdown.
{% endhint %}

<figure><img src="/files/cCIZlnq9RAsRxL0Ymo1w" alt=""><figcaption></figcaption></figure>

* Under “Dynepic” **click** “MOTAR SDK”.

<figure><img src="/files/1mhHECkoXxuxdwHfIX5z" alt=""><figcaption></figcaption></figure>

* **Click "**&#x49;nstall".

<figure><img src="/files/4JBbENnHup3Vusy7sx6M" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
During the installation a **warning** about **input systems** will appear. If this popup appears, click “**Yes**”.

Unity will restart after clicking Yes.
{% endhint %}

* The MOTAR SDK is now installed.


# Configuration

MOTAR SDK for Unity is linked to an existing app listing in Studio via a unique ClientID and Secret

{% hint style="warning" %}
Connecting an application in the SDK requires an app listing has been created in Studio in your organization's MOTAR Instance.  See: [Studio](/motar-core-services/intro-to-core-services/studio#motar-studio-overview)
{% endhint %}

### Create / Modify the Configuration File

* In your Unity project, **Click "**&#x4D;OTAR SDK"&#x20;

  <figure><img src="/files/wSsn2rP3HxVkQ3WZWxvR" alt=""><figcaption></figcaption></figure>
* A new MOTAR Configuration window will open.&#x20;

*If an app has already been linked, the window will show you the current ID/Secret for your app.*&#x20;

{% hint style="danger" %}
Modifying the configuration file may disconnect your app from the app listing! Ensure you have the correct ID and Secret for your application.
{% endhint %}

* Paste your Client ID and Secret from Studio, into the fields:<br>

  <figure><img src="/files/OSyKJuCtehAplwSYm9fk" alt="" width="281"><figcaption></figcaption></figure>
* Once added, a file will be generated and is located in the Assets\MOTAR directory

<figure><img src="/files/xMmj2IeEOj8cInuw14FW" alt=""><figcaption></figcaption></figure>

{% hint style="success" %}
You application has now been connected and is ready to test!&#x20;
{% endhint %}


# Prefabs

The following prefabs are included within the MOTAR SDK and Samples packages

## Avatar&#x20;

<figure><img src="/files/6v77ftNcbHyrXqIhYd4V" alt="" width="371"><figcaption></figcaption></figure>

* Allows users to use our pre-made Avatar and add Multiplayer to their Unity application

## Spawn Point

<figure><img src="/files/szl40IymrqU7TEc6ZYeS" alt="" width="371"><figcaption></figcaption></figure>

* Prefab MOTARXR\_SpawnPoint
* Allows users to spawn their MOTARXR\_Rig into a specific location
  * Can have multiple spawn points where user will randomly spawn into one

## Teleport Anchor

<figure><img src="/files/Co2J3J3eQTv33GdJ27Tx" alt="" width="371"><figcaption></figcaption></figure>

* Avatar displays users name & device on UI above their head&#x20;
* Avatar's will fade out as they get too close to one another&#x20;
* Avatar's face will be the users profile photo&#x20;
* Avatar's hands will animate based on device input (Grip/Trigger/Trigger Touch/Thumbstick/Thumbstick touch)&#x20;
  * Hands have some unique poses based on grabbing objects with specific tags&#x20;
  * RoundGrabbable/LCylinderGrabbable/SCylinderGrabbable/WritingGrabbable&#x20;
  * Tags will be automatically added to project when package is imported&#x20;
  * Hands have a Wrist gameObject attached to them that will spawn any "Watch" prefab located in Resources named "MOTARXR\_LefthandWatch" or "MOTARXR\_RightHandWatch"&#x20;
* Supports both Built-In and URP render pipelines&#x20;
  * Toolbar button to convert from one to the other will be automatically added on package install&#x20;
* Sample that contains MultiplayerTest&#x20;
  * A fully put together example utilizing all the features for users to try

## XR Player

<figure><img src="/files/1HEmIh7dXGrggYUxKPsV" alt="" width="371"><figcaption></figcaption></figure>

* Avatar displays users name & device on UI above their head&#x20;
* Avatar's will fade out as they get too close to one another&#x20;
* Avatar's face will be the users profile photo&#x20;
* Avatar's hands will animate based on device input (Grip/Trigger/Trigger Touch/Thumbstick/Thumbstick touch)&#x20;
  * Hands have some unique poses based on grabbing objects with specific tags&#x20;
  * RoundGrabbable/LCylinderGrabbable/SCylinderGrabbable/WritingGrabbable&#x20;
  * Tags will be automatically added to project when package is imported&#x20;
  * Hands have a Wrist gameObject attached to them that will spawn any "Watch" prefab located in Resources named "MOTARXR\_LefthandWatch" or "MOTARXR\_RightHandWatch"&#x20;
* Supports both Built-In and URP render pipelines&#x20;
  * Toolbar button to convert from one to the other will be automatically added on package install&#x20;
* Sample that contains MultiplayerTest&#x20;
  * A fully put together example utilizing all the features for users to try


# MOTAR Classes

A guide to accessible Classes within the SDK.

The MOTAR SDK for Unity allows you to integrate data from the logged in user into your applications via the MOTARProfile Class

{% hint style="info" %}
The data is returned as a [Json.net](http://json.net/) object or a Texture2D where applicable.&#x20;
{% endhint %}

## MOTARProfile Class                                     &#x20;

Namespace: MOTAR\
Assembly: Included in the MOTAR SDK

### Description

Represents a user profile in the MOTAR system. This class provides essential user information such as their handle, name, and profile picture.

{% hint style="info" %}
This class is expected to evolve in future versions to include more data for developers.
{% endhint %}

### Usage

An instance of MOTARProfile is accessible after a user has logged in using the MOTAR SDK Auth / Device Sync their user profile information can be accessed using the **Communications.Connection.userProfile**

{% code title="" %}

```csharp
MOTARProfile userProfile = Communications.Connection.userProfile;
Debug.Log($"User ID: {userProfile.userId}, Handle: {userProfile.handle}");
```

{% endcode %}

| Property       | Type                                                | Description                                                  |
| -------------- | --------------------------------------------------- | ------------------------------------------------------------ |
| userId         | string                                              | The unique identifier for the user.                          |
| prefix         | string                                              | The user’s prefix (Mr., Ms., Dr., etc.)                      |
| firstName      | string                                              | The user's first name.                                       |
| lastName       | string                                              | The user's last name.                                        |
| handle         | string                                              | The user's handle or username.                               |
| title          | string                                              | The user’s title                                             |
| companyInfo    | [MOTARUserCompanyInfo](#motarusercompanyinfo-class) | User Company Info                                            |
| profilePicId   | int                                                 | The name of the company this user belongs to (can be blank). |
| profilePicData | Texture2D                                           | Texture for the profile pic                                  |

## MOTARUserCompanyInfo Class                                     &#x20;

Namespace: MOTAR\
Assembly: Included in the MOTAR SDK

### Description

Represents a user profile company information data in the MOTAR system. This class provides essential user information about the company such as their name, and icon

### Usage

An instance of MOTARUserCompanyInfo as a subset of MOTARProfile and is accessible after a user has logged in using the MOTAR SDK Auth / Device Sync:

| Property | Type      | Description          |
| -------- | --------- | -------------------- |
| name     | string    | The company name.    |
| icon     | int       | The company icon id. |
| iconData | Texture2D | Texture for the icon |

<br>


# Multiplayer - Normcore

## 1 - Getting Started

The following guide was created using Unity 6.0.32 LTS, your editor views may differ. Normecore and MOTAR SDK are both compatible with Unity 2021LTS+.

{% hint style="info" %}
This guide assumes you have a Unity project using the MOTAR SDK, our Avatar, and want to integrate Normcore multiplayer into your project. For more information on setting up your project with the MOTAR SDK for Unity, see [MOTAR SDK for Unity](/motar-core-services/intro-to-core-services/devices/motar-sdk-for-unity)
{% endhint %}

{% hint style="warning" %}
**\*\*Mac Users\*\***

If the user is on a Mac device, please note that the silicon version does not support all plugins that are supported by the Intel version.  It is recommended to download both the silicon and Intel Editors (only one version can be run at a time).
{% endhint %}

## 2 - Project Setup

{% stepper %}
{% step %}

### Install the Normcore Package

Normcore is added with a Scoped Registry, similar to the MOTAR SDK

<details>

<summary><span data-gb-custom-inline data-tag="emoji" data-code="1f528">🔨</span> Install Normcore</summary>

1. Open the Project Settings window and click on “Package Manager.”
2. Inside the Package Manager tab, under “Scoped Registries”, click the plus button underneath MOTAR to add a new scoped registry.
3. Add the following:
   * Name: Normal
   * URL: <https://normcore-registry.normcore.io>
   * Scope(s): com.normalvr

<figure><img src="/files/YT9hwR2hXK7JunfOaFps" alt=""><figcaption></figcaption></figure>

1. Now let’s open the “Package Manager” window by clicking Window -> Package Manager from the top bar toolbar.
   1. Inside the Package Manager, click on “Normal” under “My Registries” on the left side of the window.
   2. Click on “Normcore” and click “Install”.

<figure><img src="/files/57hXBnmLkGDwdyZ0x8HF" alt=""><figcaption></figcaption></figure>

</details>
{% endstep %}
{% endstepper %}

## 3 - Configure the MOTAR SDK

{% stepper %}
{% step %}

### Configure your Avatar

The MOTAR SDK Avatar prefab (loaded with the Samples packages) can be configured to work as a Normcore avatar for multiplayer.&#x20;

<details>

<summary><span data-gb-custom-inline data-tag="emoji" data-code="1f468-1f52c">👨‍🔬</span> Configure Avatar Prefab</summary>

* From the Project window, navigate to Assets -> Samples -> MOTAR SDK -> \<current version> -> Avatar -> Resources.

<figure><img src="/files/u9UcSY03Ho0nav9jqjh2" alt=""><figcaption></figcaption></figure>

* Inside Resources double click on the prefab “MOTAR\_Player.”

<figure><img src="/files/4Qpg1HUHDVM5QewCM8vW" alt=""><figcaption></figcaption></figure>

* Inside the prefab click and drag the gameObject named “Avatar” into the Resources folder we just navigated to.

<figure><img src="/files/72G2MXHRCHi77A3e3dFR" alt=""><figcaption><p>Cloned Avatar prefab</p></figcaption></figure>

{% hint style="warning" %}
This will create a new prefab of just the Avatar’s mesh which we will use to spawn with Normcore.
{% endhint %}

* Let’s rename the new prefab to “MOTAR\_MultiplayerAvatar.”

<figure><img src="/files/sVFRoWQD0R8RWZGhh4P3" alt=""><figcaption><p>New Avatar prefab renamed</p></figcaption></figure>

* Double click on the **new prefab** we just created
* When prompted to save or discard our changes to “MOTAR\_Player” click “Discard Changes".

<figure><img src="/files/S9cZpoNqk5OCaJRdPbvx" alt=""><figcaption><p>Discard changes popup</p></figcaption></figure>

</details>
{% endstep %}

{% step %}

### Attach networking components

Now that we have our new prefab open we need to attach all the Normcore networking components.

<details>

<summary><span data-gb-custom-inline data-tag="emoji" data-code="1f5a5">🖥️</span> Networking Components</summary>

* With the root gameObject “MOTAR\_MultiplayerAvatar” selected click on “Add Component” from the Inspector window.

<figure><img src="/files/2MTCgerAtyGQ4LOHa2a7" alt=""><figcaption></figcaption></figure>

* Search for “Realtime View” and select it to add it.

<figure><img src="/files/8gZHGJkJ6m81tghQKQmv" alt=""><figcaption></figcaption></figure>

* Click on “Add Component” again and search for “Realtime Avatar” then select it to add it.

<figure><img src="/files/0eU68z7H2IjOq6GDiG0G" alt=""><figcaption></figcaption></figure>

</details>
{% endstep %}

{% step %}

### Assign Variables

Now that we have the components added, we need to assign the component variables.

<details>

<summary><span data-gb-custom-inline data-tag="emoji" data-code="1f4d1">📑</span> Variables</summary>

* From the Hierarchy window select and drag the gameObject labeled “**Head**” into the “**Head**” variable slot on the “**Realtime Avata**r” component.
* Now do the same for the “**Left Hand**” and “**Right Hand**” variable slots by dragging the gameObjects labeled “Left Hand” and “Right Hand.”

<figure><img src="/files/8ti2gebWvG1RZ1EH71DJ" alt=""><figcaption></figcaption></figure>

* Click on “Add Component” again and search for “**Realtime Transform**” then select it to add it.

<figure><img src="/files/Zm1Fdq7T4af3ltjBxSnr" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Now let’s move onto the children gameObjects.
{% endhint %}

* From the Hierarchy window select the gameObjects labeled “Head.”
* Remove the current components attached because they’re no longer required.
  1. From the Inspector window click the three dots button on both the “Rigidbody” and “Parent Constraint” components and select “Remove Component.”

<figure><img src="/files/mF9W5Es1tCIYftXRjGj3" alt=""><figcaption><p>Remove both components</p></figcaption></figure>

* With the “Head” gameObject still selected click on “Add Component” in the inspector and search for “Realtime View” then select it to add it.
* Click on “Add Component” again and search for “Realtime Transform” then select it to add it.

<figure><img src="/files/J6m5dhxwhRchK4qrhTKT" alt=""><figcaption></figcaption></figure>

* Now navigate to the child gameObject of the “Head” labeled “Avatar\_FlatHead\_1” and select it.
  1. We need to add back a Rigidbody component so that the Torso’s configurable joint can have a connection.
  2. With “Avatar\_FlatHead\_1” selected click on “Add Component” and search for “Rigidbody” then select it to add it.
  3. On the “Rigidbody” component check off “Use Gravity” and check on “Is Kinematic.”

<figure><img src="/files/OycmSpbdJbuXf4IXjaZW" alt=""><figcaption></figcaption></figure>

* Next navigate to the gameObject labeled “Torso.”
* From the Inspector window, check off “Is Kinematic” on the Rigidbody component.
* We need to fix the missing rigidbody on the first configurable joint.
  1. From the Hierarchy window, click and drag the gameObject labeled “Avatar\_FlatHead\_1” into the variable slot labeled “Connected Body” on the Configurable Joint component.

<figure><img src="/files/8Z3hKWhdj16SxDJpgHqD" alt=""><figcaption><p>Kinematic off and Flathead added to Connected Body</p></figcaption></figure>

* Next navigate to the gameObject labeled “Left Hand.”
* We need to remove the current component *parent constraint* because it’s no longer required.
  1. From the Inspector window click the three dots button on the “Parent Constraint” components and select “Remove Component.”
* Click on “Add Component” again and search for “Realtime Transform” then select it to add it. *“Realtime View” will automatically be added.*

<figure><img src="/files/C9QrxG29ampSZJHQOa8m" alt=""><figcaption></figcaption></figure>

* Next navigate to the gameObject labeled “Right Hand.”
* We need to remove the current component attached because it’s no longer required.
  1. From the Inspector window click the three dots button on the “Parent Constraint” components and select “Remove Component.”
* Click on “Add Component” again and search for “Realtime Transform” then select it to add it. *“Realtime View” will automatically be added.*

<figure><img src="/files/AT1FTgtQcXAYhFfOm0mM" alt=""><figcaption></figcaption></figure>

* That’s all the changes we need to make on this prefab. Click “Save” on the top right of the Scene window and exit the prefab.

{% hint style="warning" %}
Now, if you haven’t already, let’s open the scene you plan on using the avatar in.
{% endhint %}

* From the Hierarchy window select the gameObject labeled “MOTAR\_Player”.
* *If you don’t already have one in your scene, from the Project window navigate to Assets -> Samples -> MOTAR SDK -> 1.0.2 -> Avatar -> Resources and drag the prefab labeled “MOTAR\_Player” into your scene.*
* Open the gameObject and navigate to the gameObject labeled “Avatar.”
* Disable the gameObject by clicking the check box next to the name from the Inspector window.

<figure><img src="/files/hnfAD6vaJjvVuTT539MU" alt=""><figcaption></figcaption></figure>

</details>
{% endstep %}

{% step %}

### :checkered\_flag: Finish Line

<details>

<summary><span data-gb-custom-inline data-tag="emoji" data-code="2705">✅</span> Final Steps</summary>

{% hint style="info" %}
:tada: Now we just have to set up our connection to the network.
{% endhint %}

* With your scene open, click GameObject -> Create Empty from the top toolbar.
* Rename the new gameObject to “Realtime” or whatever best suits your needs.
* With the “Realtime” gameObject selected, from the Inspector window click on “Add Component” and search for “Realtime.”
* Select it to add it to the gameObject.
  1. On the “Realtime” component rename the “Room Name” to something unique.
  2. You’ll need to acquire and add your Normal App Key to the “App Key” variable slot as well.
* With the “Realtime” gameObject still selected  click on “Add Component” in the inspector and search for “Realtime Avatar Manager” then select it to add it.
  1. From the Project window navigate to back to Assets -> Samples -> MOTAR SDK -> 1.0.2 -> Avatar -> Resources and drag the new avatar prefab we created labled “MOTAR\_MultiplayerAvatar” into the “Local Avatar Prefab” variable slot on the “Realtime Avatar Manager” component.

<figure><img src="/files/r3aZccDUU8aXmYQeYExv" alt=""><figcaption></figcaption></figure>

1. Now from the Hierarchy window find the “MOTAR\_Player” gameObject we added earlier and drag it into the “Local Player: Root” variable slot on the “Realtime Avatar Manager” component.
2. Twirl open the child gameObject labeled “Camera Offset” nested inside of “MOTAR\_Player.”

* Find the “Main Camera” gameObject and drag it into the “Local Player: Head” variable slot on the “Realtime Avatar Manager” component.
* Now find the “Left Controller” gameObject and drag it into the “Local Player: Left Hand” variable slot on the “Realtime Avatar Manager” component.
* Lastly, find the “Right Controller” gameObject and drag it into the “Local Player: Right Hand” variable slot on the “Realtime Avatar Manager” component.

<figure><img src="/files/rOoBrEBdUdxvPs1NW3mP" alt=""><figcaption></figcaption></figure>

* Save your scene.
* :checkered\_flag: You’re now all set up and ready!

{% hint style="warning" %}
Additional setup is require for the Avatar hand animations and are not covered in this guide.
{% endhint %}

</details>
{% endstep %}
{% endstepper %}

<br>


# Installing Applications on an XR Device

Applications for standalone XR devices are downloaded as APK files. These files are installed and run directly on the XR device, no computer or cables needed.

**Choose** your installation method below:

**Meta Quest Devices**

<details>

<summary>Meta Horizon managed solutions (MDM)</summary>

Guide to adding prebuilt apps to your Meta Horizon managed solutions (MDM) admin console.

{% hint style="danger" %}
**WARNING** : **Before** launching an app on a **Meta Quest** device, ensure your Meta Quest device is operating on at least **v76**. \
*Due to a bug in Meta Quest OS **v74** apps may not launch properly.*
{% endhint %}

### Prerequisites <a href="#prerequisites" id="prerequisites"></a>

This guide is for **Meta Horizon managed solutions** admins and will walk you through the process of adding an app from MOTAR Hub to the admin dashboard.

Your account must have an admin role assigned with relevant permissions before you can create an app in Meta Admin Center. If you are unsure of your access permissions, contact your Meta admin or visit [Meta’s Manage admin roles and product access](https://work.meta.com/help/327223042205658) page to learn more.

### Get the App Listing URL <a href="#get-the-app-listing-url" id="get-the-app-listing-url"></a>

**Login** to Studio and go to the app listing > Distributions section

Toggle the dropdown arrow (indicated on the above image)

Locate the download URL and **click** the "copy" button.

You will need this URL in the upcoming steps!

### Add an App <a href="#add-app" id="add-app"></a>

1. Go to [**https://work.meta.com/admin/products**](https://work.meta.com/admin/products) and login with your admin account.
2. To add an app from an APK file to your organization’s apps in Admin Center, click **Apps** icon in the left menu of Admin Center.
3. In Manage apps, **click** "+ Add App" in the top right
4. **Pick** "Externally hosted"
5. Add details
   1. **App name: \[Name of your app here]**
   2. **Link to APK File: \[past URL link from Studio]**
6. Add visuals *(optional)*
   1. **Add Icon**
   2. **Add logo**

</details>

<details>

<summary>Meta Quest Developer</summary>

{% hint style="danger" %}
/**WARNING** : **Before** launching an app on a **Meta Quest** device, ensure your Meta Quest device is operating on at least **v76**. \
*Due to a bug in Meta Quest OS **v74** apps may not launch properly.*
{% endhint %}

## Getting Started

The Meta Quest 3 (and Meta Quest 2, Pro, 3s) use files called APKs to install apps. When interacting with an APK downloaded from MOTAR Hub, users can side-load the application to the Meta Quest device.<br>

Installing “ad hoc” applications to a Meta Quest device requires either a Meta Quest for Business MDM account, a developer account, 3rd party software, or a 3rd party MDM\*.

### Meta Horizon managed solutions (MDM)

1. [**https://work.meta.com/help/323729803480003/?helpref=hc\_fnav**<br>](https://work.meta.com/help/323729803480003/?helpref=hc_fnav)Adding apps to the Meta Horizon managed solutions accounts is covered in the above documentation.
2. **Login** to the Meta for Work Admin[ **https://work.meta.com/accounts\_center/**](https://work.meta.com/accounts_center/)
3. Add the **URL** to the **MDM Distribution List.**

{% hint style="warning" %}
3rd party MDM’s differ in functionality and are not covered in this guide. Please contact your MDM provider for details on how to install apps.
{% endhint %}

### First Time Setup (Developer Mode)

1. Create a developer account with Meta. You can do this by going to this[ **link**](https://accountscenter.meta.com/) and completing their signup process.
2. Verify your developer account by providing a credit card or mobile number.
3. If you have not used your headset, complete the initial headset setup/first time user experience before continuing.
4. Install the Meta Horizon app on your phone and log in with your newly created Meta account. (This step is an optional part of the first time user setup in the headset and may have been completed previously.)
   1. Download for Android[ **here**](https://play.google.com/store/apps/details?id=com.oculus.twilight\&hl=en_US)
   2. Download for iOS[ **here**](https://apps.apple.com/us/app/meta-horizon/id1366478176)
5. **Login** to the headset using the same developer account.
   1. You may have to logout if your current account in the headset is not the same as the developer account setup in **step 1**.
6. **Login** to the phone app with the same developer account.
7. Connect your headset to the app if not completed during **step 3**.
8. From your phone, enable Developer Mode under the Headset Settings.
9. **Open** toolbar
10. You can find this option by going to **Menu > Devices > Pick the device you wish to use > Headset Settings > Developer Mode**. Toggle Developer Mode to **ON**

<figure><img src="/files/i8QC6cHJ7zrEHcd3CgYZ" alt=""><figcaption></figcaption></figure>

## How to Install an App

There are three ways\* to side-load an app onto the Meta Quest headset, using the **Meta Quest Developer Hub** (via Wi-Fi or link cable), the **SideQuest application**, or the **Command Line** (via a link cable).

### **Meta Horizon managed solutions** (MDM)

1. [**https://work.meta.com/help/323729803480003/?helpref=hc\_fnav**<br>](https://work.meta.com/help/323729803480003/?helpref=hc_fnav)Adding apps to the Meta for Business accounts is covered in the above documentation.
2. **Login** to the Meta for Work Admin[ **https://work.meta.com/accounts\_center/**](https://work.meta.com/accounts_center/)
3. Add the URL to the **MDM Distribution List**

### Meta Quest Developer Hub (MQDH)

* Follow Meta’s device setup guide[ **here**](https://developers.meta.com/horizon/documentation/unity/unity-env-device-setup/)
* The following steps may repeat portions of the Meta guide
* Download the Meta Quest Developer Hub(ODH)[ **here**](https://developer.oculus.com/downloads/package/oculus-developer-hub-win).
  1. Next, install it by double clicking on it and running through the installation wizard.
* **Login** with your developer account
* **Connect** your Meta Quest headset to your computer via the[ **Link Cable or AirLink**](https://www.meta.com/help/quest/articles/headsets-and-accessories/oculus-link/connect-with-air-link/?srsltid=AfmBOop5IuBcpgHpW2NYOZQCFW1ZaMB1pn-0WIjeGY4bfoTKG5cas3wS)
* After setting your device to **Developer Mode**, you can open up the **Developer Hub** app to view your "connected" device under the **Device Manager** tab.

<figure><img src="/files/pjNNJly1DNLalogLjXYk" alt="" width="271"><figcaption><p>MQDH <strong>Device</strong> <strong>Manager</strong></p></figcaption></figure>

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXewQ543WUwuYy8ZOr-1AQBgLAhvrygie8C7at3rn14ZyTZ7uuBXWNK9LWoH5U4UnR8aMkeGlEtkASptSmEXGvHfFbM7BZOkdN569vYXizFV4-o50L_HuSGXC8WaAVWzGvPEnOef?key=94UzjZoz3rxYBFT-uST1_cPz" alt=""><figcaption></figcaption></figure>

* You should see your device connected under the **Devices** tab. If you do not see your device and it is connected via a USB-C cable, click "**Set Up New Device**" and follow the on screen instructions.

<figure><img src="/files/lv7A5HBzGdfNaVzcrwoS" alt="" width="249"><figcaption><p>MQDH <strong>Devices</strong></p></figcaption></figure>

<figure><img src="/files/S4nywN5gDe9d9X45blBb" alt=""><figcaption><p>MQDH Device <strong>added</strong> but not connected.</p></figcaption></figure>

<figure><img src="/files/TltRy02UhtlaoXZr2LuG" alt=""><figcaption><p>MQDH Device <strong>connected</strong>.</p></figcaption></figure>

* **Click** the “Add Build” button to select and install your APK to the headset.

<figure><img src="/files/HsB6tbR4w2FuN6hFZFvq" alt=""><figcaption><p>MQDH <strong>add a build (APK)</strong></p></figcaption></figure>

* Your apk will now **install** on your Meta Quest 3.
* To launch the app, see [#launching-apps](#launching-apps "mention")

***

</details>

**HTC Vive Devices**

<details>

<summary>Vive Focus 3</summary>

## Manually Install an APK on a Vive Focus Device

{% hint style="warning" %}
Installing apps on your Focus 3 requires a USB-C cable. Plug the cable into your computer and then into the device. You may need to 'authorize' the computer in the headset.
{% endhint %}

**On Your Computer**

Once your computer is **connected** to your Focus 3, you should see the device folder in your computer file explorer.
\
Drag the **downloaded** MOTAR 3D to the Focus 3 "Downloads" folder. <br>

**On Your Focus 3**

Put on your Focus 3 and navigate to "Storage/Downloads" Click on the MOTAR 3D file and choose "Install"<br>

</details>

**Most Android based XR Devices**

<details>

<summary>SideQuest</summary>

**SideQuest** is a 3rd party tool which allows installing software outside of the Meta Quest Store (ad hoc). SideQuest is community run and the developers work closely with Meta to allow developers a platform for showcasing their early work. Recently, Meta has allowed some integration with SideQuest via the Meta Quest Labs.

* Download the SideQuest application[ **here**](https://sidequestvr.com/setup-howto). Next, install it by double clicking on it and running through the installation wizard.
* Once installed, connect your headset to the computer via[ **Link Cable or AirLink**](https://www.meta.com/help/quest/articles/headsets-and-accessories/oculus-link/connect-with-air-link/?srsltid=AfmBOop5IuBcpgHpW2NYOZQCFW1ZaMB1pn-0WIjeGY4bfoTKG5cas3wS)
  * You should see your device in the upper left corner

<figure><img src="/files/IM0MPbiTYdNkpzBZKg1m" alt="" width="217"><figcaption><p>SideQuest with a Quest connected.</p></figcaption></figure>

* **Click** the “Install APK” button and select your APK

<figure><img src="/files/PkLmSgzXoXNIFkIrET9T" alt="" width="374"><figcaption><p>SideQuest <strong>Install APK</strong></p></figcaption></figure>

* The install status can be seen in the “Running Tasks” tab.

<figure><img src="/files/pUSNHrdTYHkr9lTJan34" alt="" width="374"><figcaption><p>SideQuest check <strong>running tasks.</strong></p></figcaption></figure>

<figure><img src="/files/CIttIVjq02THUSofkOHR" alt="" width="375"><figcaption><p>SideQuest current running <strong>task list.</strong></p></figcaption></figure>

</details>

<details>

<summary>Command Line ADB Install (Windows only)</summary>

### Command Line (via Link Cable)

#### Windows/PC Only

1. Install ADB Drivers from[ **here**](https://developer.oculus.com/downloads/package/oculus-adb-drivers/). ADB is the software that lets PCs transfer and installs apps onto Android-based devices like Oculus standalone headsets. When the download finishes, unzip the downloaded file folder. Now **right-click** on **android\_winusb.inf** and click **Install**. When prompted click open followed by yes to get a message that says, **"The operation completed successfully."**
2. Next, you need to download the SDK platform tools from[ **here**](https://developer.android.com/studio/releases/platform-tools). Extract the contents of the platform-tools folder to an easy-to-find folder on your PC, such as **C:\ADB\users\\"YourName"** by selecting **all** the contents of the folder and copying(CTRL+C) and pasting(CTRL+V) it into the new location.
3. Make sure your headset is connected to your PC via a link cable(or compatible USB cable).
4. Open the **Command Prompt.** Right-click on the Windows **Start** button at the bottom left of your screen and click **Command Prompt (Administrator)** or click on the windows icon and type "cmd" and press enter.
5. In the command prompt type "**adb**" and a string of text should pop up if you completed everything correctly, but this message will pop up if the ADB drivers and platform tools weren't installed properly: **'adb' is not recognized as an internal or external command, operable program or batch file**.
6. Type **"ADB devices"** to view **"List of devices attached"** with the device listed below(represented by a list of numbers and letters). It will most likely say "unauthorized" next to that so you will need to put on your headset and select **"Always allow from this computer"** or **"allow"** to allow your Oculus to connect to your PC. After this, in the command prompt, it should say **"device"** instead of unauthorized.
7. Install the app via command line by manually entering in the file path and app name or **copying the path**. To copy the path, hold shift, right-click on the APK file, and select "copy as path".
8. In the command prompt, type **adb install -r command** followed by the **full path** to the sideloaded app you want to install then press enter. It should say **"success"** in the command prompt if everything worked correctly. Example:

```
adb install -r C:\Users\YourName\Downloads\MyCoolNewApp.apk
```

</details>


# Hub

Permissions-based Digital Asset Management with Digital Thread

## MOTAR Hub Overview

MOTAR Hub is a content discovery service that includes applications, model, video, audio, image and document listings.

{% hint style="success" %}
MOTAR Hub is fully mobile-responsive and optimized for seamless use across all your devices, including desktop, tablet, smartphone, and compatible XR headsets!
{% endhint %}

<figure><img src="/files/j0KcvfMVAPPEMyxPhNfK" alt=""><figcaption></figcaption></figure>

## **Access**

MOTAR Hub is available to all users on the platform. The content within the Hub is available based on the permissions given to the assets uploaded by the Studio Organization. Users can use the preview of the permissions table on the hub card to determine if they have are able to interact with it.

### Accessing the Permissions Table

The permissions for each MOTAR Hub listing can be seen by hovering over the key icon on the card. A tooltip will display showing access as full, partial or none indicated by the circles.&#x20;

<figure><img src="/files/ZQZh78032DeXaAYE77Jj" alt=""><figcaption></figcaption></figure>

Clicking the key icon will open up a full permissions table.

<figure><img src="/files/4cxCBRb5085HTDR9NGdD" alt="" width="375"><figcaption></figcaption></figure>

### Full Access

A solid filled in circle on the tool tip means that user type has full access

<div><figure><img src="/files/Og9Axr1MXjaCmbpmO0BL" alt=""><figcaption></figcaption></figure> <figure><img src="/files/Q3DovPcgHP0TqCbZ9tv0" alt=""><figcaption></figcaption></figure></div>

### Limited Access

A half filled in circle on the tool tip means that user type has partial access and can open the listing to review the full table.

<div><figure><img src="/files/JhEyTqMr8jJlPu7KpqLM" alt=""><figcaption></figcaption></figure> <figure><img src="/files/2wWQy7iFcKGAGaSmJ4uO" alt=""><figcaption></figcaption></figure></div>

### No Access

An empty circle with a slash means that user group only has hub view access and they would not be able to click into the card to see any additional listing details.

&#x20;

<div><figure><img src="/files/VW6PoLmFfse7Uk8xUHFK" alt=""><figcaption></figcaption></figure> <figure><img src="/files/I00SKACwtQoSbjZ3Y7cr" alt=""><figcaption></figcaption></figure></div>

{% hint style="info" %}
Also listed on the Hub Card is the MIAB Compatibility denoted by the M icon which can be hovered over to learn more. The M icon means MIAB Compatible while the M icon with a slash through it means Not MIAB Compatible.
{% endhint %}

<figure><img src="/files/MNPTRjgKEJnpunO7RbX3" alt="" width="563"><figcaption><p>MIAB Compatible Icon</p></figcaption></figure>

## **How to Use MOTAR Hub**

<table data-card-size="large" data-view="cards"><thead><tr><th data-type="content-ref"></th><th></th></tr></thead><tbody><tr><td><a href="/pages/zPEMPjN5XKCbzvGzhnJd">/pages/zPEMPjN5XKCbzvGzhnJd</a></td><td>Instructions on how to discover listings in the Hub.</td></tr><tr><td><a href="/pages/MVQECf7LrwAFEfZ2XrZ2">/pages/MVQECf7LrwAFEfZ2XrZ2</a></td><td>Once a listing has been published or approved, it can be downloaded from the MOTAR Hub by users with the appropriate permissions.</td></tr><tr><td><a href="/pages/fq7LwhQkmy9LRfLcPQfr">/pages/fq7LwhQkmy9LRfLcPQfr</a></td><td>The DX Model Inspector allows MOTAR users with appropriate permissions to preview a 3D model directly embedded in the HUB Listing.</td></tr><tr><td><a href="/pages/YlICGoEASsBrxlH3EEVx">/pages/YlICGoEASsBrxlH3EEVx</a></td><td>Hub listings will be categorized as either MIAB compatible or incompatible. </td></tr></tbody></table>


# Discovering Listings

{% hint style="warning" %}
Listings are visible on hub when the studio group who owns that listing has made it discoverable when they created it. The users ability to interact with any particular listing is based on their role and the permissions of that listing.
{% endhint %}

### Filter Options

MOTAR Hub provides the user with three different filter options to discover listings on the platform:\
Assets Dropdown, Sidebar Filter, and Sort by Dropdown.  Additional information regarding each filter option can be found below on this page.

<figure><img src="/files/018FDoPo8R0RmNRF4yGG" alt=""><figcaption></figcaption></figure>

### Assets Dropdown Menu

The asset dropdown menu lists all assets (both available now and coming soon) for the MOTAR Hub. The dropdown will filter the content displayed to the user based on what is selected.

<figure><img src="/files/wHuT1aEsWVFgE6Cn3L4X" alt=""><figcaption></figcaption></figure>

For example, if the user selects Apps, only app listings will be shown.

### Sidebar Filter

Using the sidebar filter, the user can further refine results with a combination of filter options based on Listing Type and Organization.

<figure><img src="/files/q5CLtZGe5r0I11vvJQy4" alt=""><figcaption></figcaption></figure>

### Filter by Listing Type

The Listing Type dropdown menu lists all assets (both available now and coming soon) for the MOTAR Hub. When the user selects an asset type, additional filter types will be displayed.  Details regarding each asset filter type can be found in the tabs below.

<figure><img src="/files/rm7xsGkoER5pQpfiwBeg" alt=""><figcaption></figcaption></figure>

#### Filter by Authorized Asset

The Authorized Asset dropdown menu gives the user the ability to filter all available content by all authorized assets or only those created by their organization that have been published on MOTAR Hub. &#x20;

<figure><img src="/files/FzY2HpaqZdU7hTQFeu2Y" alt=""><figcaption></figcaption></figure>

#### Filter by Certified Asset

The Certified Asset dropdown menu gives the user the ability to filter all available content by all certified assets or only those created by their organization that have been published on MOTAR Hub.&#x20;

<figure><img src="/files/NHGdYmBDMai3IZCZ0FeC" alt=""><figcaption></figcaption></figure>

#### Filter by Organization

The Organization dropdown menu gives the user the ability to filter all available content by  organization(s) that published the asset on MOTAR Hub. &#x20;

<figure><img src="/files/kmEW5wIfzAKVuXcPaNFn" alt=""><figcaption></figcaption></figure>

### **Search by Tag**

To search by tag, type the word or tag name into the search bar. Any assets containing that term in their title, description, or tags will appear in the results.

<figure><img src="/files/QiF9lfPk2oFzHnw7USbC" alt="" width="375"><figcaption></figcaption></figure>

### **Filter by Tag(s)**

To filter by tag, open the side menu and select one or more tags. The Hub will automatically update to show only matching listings.

<figure><img src="/files/C1Mlir8L6rFvIfW66x9G" alt="" width="375"><figcaption></figcaption></figure>

### Sort By Dropdown Menu

The Sort By dropdown menu gives the user the ability to sort all available content by three criteria:  Published Date - Latest First, Published Date - Oldest First, Alphabetical A-Z,  Alphabetical Z-A &#x20;

<figure><img src="/files/onpNCm7C90LCneeDeEjv" alt=""><figcaption></figcaption></figure>

{% tabs %}
{% tab title="Published Date - Latest First " %}
The user will see a mix of MOTAR Hub content displayed by the most recent publish date first.
{% endtab %}

{% tab title="Published Date - Oldest First" %}
The user will see a mix of MOTAR Hub content displayed by the oldest publish date first.
{% endtab %}

{% tab title="Alphabetical A-Z" %}
The user will see content displayed in alphabetical order listed A-Z.
{% endtab %}

{% tab title="Alphabetical Z-A" %}
The user will see content displayed in alphabetical order listed Z-A.
{% endtab %}
{% endtabs %}


# Interacting with Listings

How to view skills badges associated with an asset on Hub.

### Hub Listing Anatomy

Each hub listing type follows the same structure which may include the following areas:

* Listing Previewer
  * Image
  * Model
  * Video
  * Audio
* About/Badges/Metrics Card
* Assets Used Card
* Download Card
  * Download options
  * Launch options
* Version Tree Card
* Permissions Card

<figure><img src="/files/GGPrc3a9iI4313qCIQne" alt=""><figcaption></figcaption></figure>


# Download/Launch

Understanding the download card on the Hub listings.

The Download card of a hub listing details page will be different depending on the listing type. You may see a download or a launch button.

{% hint style="info" %}
Listing types available for download from the MOTAR Hub include: Apps, Audio, Documents, Models, Images, and Videos.
{% endhint %}

### Download Listings

After the user has found a listing that they would like to download and have navigated to the Hub Listing page, CLICK the "Download" link.

<figure><img src="/files/mS7HPIwPNMqIyCy6Z0u6" alt=""><figcaption></figcaption></figure>

This will prompt a **DOWNLOAD ASSET** modal.&#x20;

<figure><img src="/files/NeAtRDQ0NJjIVb7KUs2O" alt=""><figcaption></figcaption></figure>

If the user does not wish to continue with the download, the "Cancel" or "X" buttons can be selected to close the modal.&#x20;

<figure><img src="/files/adDbxqo6cViunZ6WHalG" alt="" width="375"><figcaption></figcaption></figure>

If the user does want to proceed with the download, **Click** the "Download" button.

<figure><img src="/files/Pky2DiLrhY5MoVjlVUDY" alt="" width="375"><figcaption></figcaption></figure>

{% hint style="info" %}
Once the download has been completed, the file will be able to be accessed locally by the user.
{% endhint %}

## Launch Listings

Listing types available for launch from the MOTAR Hub include: URL and MOTAR 3D apps. These apps can be launched via the browser or through XR.

#### Web Based (URL) Apps

Launching URL based apps is as simple as clicking the Launch URL button.&#x20;

* Navigate to the app listing detail page from Hub
* **Click** the "Launch URL" button

<figure><img src="/files/8GEg8ODYTuP3r7SxGUkG" alt=""><figcaption></figcaption></figure>

* A popup will show you the URL, **click** "Proceed" to leave MOTAR and goto the URL

<figure><img src="/files/jmEwzt793AxBkVY90keo" alt=""><figcaption></figcaption></figure>

#### Immersive Apps (XR)

{% hint style="danger" %}
**WARNING** : **Before** launching an app on a **Meta Quest** device, ensure you have your Guardian activated and set to RoomScale. \
Due to Meta update **v74**, **inactive** Guardians and **Stationary** guardians may prevent apps from launching properly.
{% endhint %}

There are two ways to launch immersive apps hosted on MOTAR:

#### MOTAR 3D

Requirements:&#x20;

* [ ] MOTAR 3D is installed&#x20;
* [ ] The app is installed on the headset.
* [ ] You are permissioned to launch the app.

{% hint style="warning" %}
If you organization is using Meta Quest for Business, you will need to contact your app administrator for information on which apps are installed on your device.
{% endhint %}

To launch an immersive application using **MOTAR 3D**

* **Launch** MOTAR 3D (see [MOTAR 3D](/motar-core-services/intro-to-core-services/devices/motar-3d))
* Find the app you would like to launch
* **Click** 'Launch' on the app details page.

Launch directly from MOTAR Hub on the **web**.

* Navigate to Hub
* Locate the app you would like to launch
* **Click** 'Launch with MOTAR 3D'

<figure><img src="/files/357NQCjjx45PTsMeLUTd" alt=""><figcaption></figcaption></figure>

* **Click** "Continue on Headset"

<figure><img src="/files/CnfRhWgXvSHrqreMOCGD" alt=""><figcaption></figcaption></figure>

* Devices page will open

{% hint style="warning" %}
The devices page now has information about the app you want to launch. Do not navigate away from this page or your app may not launch properly!
{% endhint %}

<figure><img src="/files/idgr3pMg1QHavrR2z6cw" alt=""><figcaption></figcaption></figure>

* Put on your headset
* Launch **"**&#x4D;OTAR 3D"

{% hint style="danger" %}
To launch an app directly, you will need to re-enter the domain and get a new sync code.&#x20;

**Do not** use your **PIN** when launching an app from web.
{% endhint %}

* Grab the sync code from the MOTAR 3D sync screen.

<figure><img src="/files/MbAXwI17EJyMI4XrhJEw" alt=""><figcaption></figcaption></figure>

* **Enter** the MOTAR 3D sync code into the Devices page on web.

<figure><img src="/files/17qVyZwccf1HSVMaWUR5" alt=""><figcaption></figcaption></figure>

* **Click** 'Sync Device'
* Put your headset back on and enjoy the app!

If the application requirements have been met, your app will launch after entering the sync code. Otherwise, you will be brought to the MOTAR 3D main screen.


# Previewer

Instructions on using the MOTAR Model Inspector

### About

The Model Inspector allows MOTAR users with appropriate permissions to preview a 3D model directly embedded in the HUB Listing.

{% hint style="info" %}
Instructions explaining different permissions types can be found at the link below:

[Listing Permissions](/motar-core-services/intro-to-core-services/studio/listing-permissions)
{% endhint %}

### Previewer Types

What you see in the previewer will change depending on the listing.&#x20;

* Video Player
* Audio Player
* Image Viewer
* 3D Model Viewer

### Video and Audio Player

For these listing types, the previewer will have controls right on the screen.&#x20;

<figure><img src="/files/5bH4g21xKx88BFFppEBg" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/gTZ3MV06EzXWkpC1BIJc" alt=""><figcaption></figcaption></figure>

### Image Viewer

Images are static on the screen unless additional thumbnails were provided by the creator. In that case, a carousel is displayed where you can scroll through the different images.

<figure><img src="/files/b2imJIYWakOCEx10X175" alt=""><figcaption></figcaption></figure>

### 3D Model Viewer

3D Models can be interacted with right on the viewer page. See below for the controls available. You can also view any additional models in the viewer by clicking on the additional thumbnail below it. &#x20;

#### Final Render

When the "Final Render" option is selected, the model displayed in the viewer is the "Final Render" of the 3D model.

<figure><img src="/files/CiG1rzk2vdajzb0FdRZw" alt=""><figcaption></figcaption></figure>

#### Matcap

The Matcap displays a surface material and lighting environment simply by painting an object so that it shows proper texture, highlights, and lowlights.

<figure><img src="/files/oX2IFNg9NvfUor457iDX" alt=""><figcaption></figcaption></figure>

#### Wireframe

The wireframe option displays a visual representation of the underlying design structure of a 3D model.

<figure><img src="/files/hY1zPgT0bCQBORDdRiux" alt=""><figcaption></figcaption></figure>

#### Background Color

The background color option allows the user to change the background color of the 3D model Inspectors display area.

<figure><img src="/files/rL689wIi6WTvoVkno4Hu" alt=""><figcaption></figcaption></figure>

#### Play Animation

The play animation dropdown allows the user to select/run any animations included in the 3D model listing.

<figure><img src="/files/Vpzf8uEUQCHZz7Z2xZvM" alt=""><figcaption></figcaption></figure>


# Listing Version Tree

MOTAR supports versioning and remixing of assets with it's Digital Thread feature. A visual "tree" of an assets digital thread is created automatically. Learn more about Digital Thread below.

{% content-ref url="/pages/nZuFwq0fcqsiai4EKer2" %}
[Digital Thread](/motar-core-services/intro-to-core-services/studio/digital-thread)
{% endcontent-ref %}

## Version Tree Dropdown

A listing may have multiple versions shown on the Version Tree Dropdown from the Hub listing card.&#x20;

<figure><img src="/files/tOpNdsxoH2FHbbVBJ03U" alt=""><figcaption></figcaption></figure>

### Select Version

**Click** on the "Version Tree Dropdown" to expand / view the listing data. Search through the list and **Click** your desired version. The hub card will update allowing the user to then **Select** it to launch directly into the desired content.<br>

{% hint style="info" %}
If using the Hub Search Bar to find a specific listing by name the Version Tree Dropdown will be disabled on the Hub Listing Card.
{% endhint %}

<figure><img src="/files/yrMo5dB3MdfMPM5TLvXF" alt=""><figcaption></figcaption></figure>

## Version Tree

Once you have a listing open, the Hub Listing Detail page will display the Version Tree in a card on the right. From this view, the user is able to access different versions of the content if they have the required permissions and if the version's creator has allowed it to be visible on the Hub.

<figure><img src="/files/NlrbEkLeRdxSbKICCJcD" alt=""><figcaption></figcaption></figure>

### Select Version from Tree

**Click** on a version in the Version Tree. This will redirect the user to the Hub Listing Detail page for the version they selected.

<figure><img src="/files/VFBlDQI1g8tT78Q9gGuF" alt=""><figcaption></figcaption></figure>


# About Details Card

How to view skills badges associated with an asset on Hub.

### About/Version info

Details for the listing show up on the first tab as either an About section, or, if it's a version, the Version section.&#x20;

<figure><img src="/files/PnJCDgcDr0gEgKzuqcDg" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/WvxVf9kfTsC6HYrmnuCQ" alt=""><figcaption></figcaption></figure>

**Clicking** on an asset will tak you to that hub listing page if you have the proper permissions.&#x20;


# Skill Badges

How to view skills badges associated with an asset on Hub.

### Viewing Badges

Assets can earn you **Skill Badges** to track competencies across multiple asset types. This data is stored at the asset level and also in the user's digital learning record [Learner Record](/motar-core-services/intro-to-core-services/profile/learner-record).&#x20;

<figure><img src="/files/03XudihWyETAVtHH9R9x" alt=""><figcaption></figcaption></figure>

* **Click** on the "Badges" tab on any compatible asset listing to view the available Skill Badges for that asset.
* To add a Skill Badge to an asset, see [Add a Skill Badge](/motar-core-services/intro-to-core-services/studio/add-a-skill-badge)


# Metrics

How to view skills badges associated with an asset on Hub.

### Metrics tab

Metrics are captured on each listing and are located under this tab.

<figure><img src="/files/5Tib381oWJBuu4T98toU" alt=""><figcaption></figcaption></figure>

Here you will see the metrics for the original version and the version you're currently vieweing to compare. If you are viewing an original version page it will not have a comparison.&#x20;


# Assets Used

How to view skills badges associated with an asset on Hub.

### Assets Used Card

Remixed listings may include additional assets that were used to make the remix. Those are found on the assets used card.&#x20;

<figure><img src="/files/WvxVf9kfTsC6HYrmnuCQ" alt=""><figcaption></figcaption></figure>

**Clicking** on an asset will tak you to that hub listing page if you have the proper permissions.&#x20;


# Permissions Card

How to view skills badges associated with an asset on Hub.

### Permissions

The listing permissions that were set during creation are displayed here on the listing details page. This is the same [permissions](https://app.gitbook.com/o/-LVczVIRnIFIRo5llDYg/s/VJV84grXWXSLppsAzVKx/~/edit/~/changes/480/motar-core-services/intro-to-core-services/hub#accessing-the-permissions-table) that is located on the hub card in Hub.

<figure><img src="/files/fDshCry8saKVOcGkF5b2" alt=""><figcaption></figcaption></figure>


# Profile

This page allows users to see their account information, change their passwords, update their profile image, and access their Learning Record.

To navigate to the User Profile page, **select** "Profile" from the Nav menu:

<figure><img src="/files/YdxFTuc7b94Rxs9NcSb8" alt=""><figcaption></figcaption></figure>

The Profile Details page will open by default. From here, you can view and edit profile details.&#x20;

<figure><img src="/files/67XDwQzH9uCbpqGnc5yL" alt=""><figcaption></figcaption></figure>


# Account Details

This page allows users to see their account information, change their passwords, update their profile image, and access their Learning Record.

## Edit Profile Account Details

{% hint style="warning" %}
*Editing personal information is not available at this time.*
{% endhint %}

### Changing your password

* **Click** on the "Details > Password" section

<figure><img src="/files/UliVKSopppi9DDCAJ0ME" alt=""><figcaption></figcaption></figure>

* Enter your current password
* Enter a new password
* Confirm the new password

After entering the correct current password, new password, and confirming the new password, the "Change Password" button will activate.

* **Click** the "Change Password" button to save the new password.

<figure><img src="/files/Hk7DQL62B230pwFOiXWa" alt=""><figcaption></figcaption></figure>

***

### Updating your profile picture

* **Click** the "Replace" button at the bottom of the Details page

<figure><img src="/files/EH14kWjf4H7K8B9bgtPO" alt=""><figcaption></figcaption></figure>

* A file selection window will open, choose your image.&#x20;
* You can crop your image if needed,&#x20;
* **Click** "Upload"

<figure><img src="/files/2QzDVJ0N5GeWQhwFrSqp" alt="" width="375"><figcaption></figcaption></figure>

<figure><img src="/files/aO62drmaT7y7F9ZtiJt5" alt=""><figcaption></figcaption></figure>


# Learner Record

Motar gives learners and instructors detailed insights into how users interact with video content, helping track engagement, progress, and skill development. With **learner metrics**, users can understand their own behavior, while instructors gain actionable data to improve learning outcomes.

These metrics allow learners to **monitor their engagement, optimize their learning experience, and track skill acquisition**, while providing instructors with the data needed to create more effective, engaging content.

### Viewing your learner record (Insights):

* **Click** "Record" on the User Profile page

<figure><img src="/files/AzTDPmHDAIovrxp36b3b" alt=""><figcaption></figcaption></figure>

* In the list of Assets, **click** on the insights 'graph' icon to view details for that asset.

<figure><img src="/files/D3lOKkyQsIxG0gx6y8Yy" alt=""><figcaption></figcaption></figure>

* A modal will open with specific metrics collected for that asset.

<figure><img src="/files/bN0HG9nKBh5rprFCNJow" alt="" width="563"><figcaption></figcaption></figure>

### Interaction & Behavior

<table><thead><tr><th width="198">Name</th><th width="337">Description</th><th>Example</th></tr></thead><tbody><tr><td><strong>Times Played</strong></td><td>Number of times a learner has watched a video. </td><td><strong>4</strong> views.</td></tr><tr><td><strong>Percent Watched</strong></td><td>The total amount of the video watched.</td><td><strong>84%</strong> watched<strong>.</strong></td></tr><tr><td><strong>Times Paused</strong></td><td>Frequency of pausing .</td><td>Paused <strong>12</strong> times.</td></tr><tr><td><strong>Was Muted</strong></td><td>Was the audio muted?</td><td><strong>No</strong></td></tr><tr><td><strong>Max Volume</strong></td><td>The maximum the volume was set.</td><td><strong>95%</strong></td></tr><tr><td><strong>Was Completed</strong></td><td>The entire video was watched.</td><td><strong>Yes</strong></td></tr><tr><td><strong>Last Watched</strong></td><td>The last time the video was watched.</td><td>Sep 30, 2025, 4:28:30 PM</td></tr><tr><td><strong>Playback Speed</strong></td><td>The speed the video was watched.</td><td>1x</td></tr><tr><td><strong>Was Full Screen</strong></td><td>Was the video played at fullscreen.</td><td><strong>No</strong></td></tr></tbody></table>

### Download Certificate

If a **Skill Badge** is associated with the completed asset, a "download certificate" icon will appear.

* **Click** the "Download Certificate" icon to automatically generate and download a PDF certificate for that **badge.**

<figure><img src="/files/wRSn6ZU04DFgZXhDrIkz" alt=""><figcaption></figcaption></figure>

* The PDF is compatible with any [**MOTAR CertIQ**](/additioinal-features/motar-certiq) system.

<figure><img src="/files/w2dAv97m2bdcXdbuzXHT" alt="" width="563"><figcaption></figcaption></figure>

### Import a Certificate

Importing a certificate from another compatible MOTAR CertIQ system is a simple process.&#x20;

* **Click** the "Import Certificate" button

<figure><img src="/files/KUAGqLWcpXOkG34pgN55" alt=""><figcaption></figcaption></figure>

* A file dialog window will open, select your PDF certificate.

{% hint style="danger" %}
Currently, **Admins** can disable importing user certificates from other systems. If the Import Certificate button is not available, contact your admin.

For more information see [MOTAR CertIQ](/additioinal-features/motar-certiq).
{% endhint %}


# Studio

Create and Distribute Content (3D Models, Apps, etc.)

## MOTAR Studio Overview

MOTAR Studio allows creators, and platform users, to quickly create, link, and distribute their applications for outside platforms using low-code studio tools & multi-language SDKs.

<figure><img src="/files/nP9Y0PSqe9zEZMwSOxpf" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
From here the Users will be able view the listings created by their Studio Org. The View Sandbox Listings toggle will default **ON** allowing the Users to view both Sandbox and Production listings. When the toggle is set to **OFF** only Production listings will display.
{% endhint %}

## **Access**

MOTAR Studio is available to users added to at least one studio group. If you need access, please contact your platform manager. Once assigned to a studio group the user will automatically be assigned the [creator role.](https://app.gitbook.com/o/-LVczVIRnIFIRo5llDYg/s/VJV84grXWXSLppsAzVKx/~/edit/~/changes/480/motar-core-services/intro-to-core-services/admin/users#role-s) &#x20;

{% hint style="warning" %}
Studio includes tools and a complete sandbox environment to develop applications and training scenarios for the user without the need to have broader platform access.
{% endhint %}

## **How to Use MOTAR Studio**

<table data-card-size="large" data-view="cards"><thead><tr><th data-type="content-ref"></th><th></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td><a href="/pages/g0eUi6o3ILJ0EA3DlEjt">/pages/g0eUi6o3ILJ0EA3DlEjt</a></td><td>Learn how to create and manage your listings.</td><td><a href="/files/7mVrVGHCfQKw9WYe4stx">/files/7mVrVGHCfQKw9WYe4stx</a></td></tr><tr><td><a href="/pages/LRlGPYZbBEAJ8VyyNe8Z">/pages/LRlGPYZbBEAJ8VyyNe8Z</a></td><td>The MOTAR Sandbox is a MOTAR test environment.</td><td><a href="/files/ME4X9SrRm1ideXbsV6zl">/files/ME4X9SrRm1ideXbsV6zl</a></td></tr><tr><td><a href="/pages/w1QhZr1b8TwwfUsIBSmd">/pages/w1QhZr1b8TwwfUsIBSmd</a></td><td>Control who can access your listing with the Permission Wizard.</td><td><a href="/files/1EiWF7SK1uUikXf9jmje">/files/1EiWF7SK1uUikXf9jmje</a></td></tr><tr><td><a href="/pages/nZuFwq0fcqsiai4EKer2">/pages/nZuFwq0fcqsiai4EKer2</a></td><td>Add version control to your listings.</td><td><a href="/files/Pj2yLU39N2453kJXPDzZ">/files/Pj2yLU39N2453kJXPDzZ</a></td></tr></tbody></table>


# Manage Each Listing Type

Use Studio tools to link your apps to the MOTAR Platform and leverage the SDK features. Apps can use Sandbox environment when in test and or Production environment when ready for discovery and download from the [MOTAR Hub](https://hub.motar.com/).

<figure><img src="/files/Vpl1lS5NZhYQh1lVWVz5" alt=""><figcaption></figcaption></figure>

Additional information on how to manage each listing type can be found at these pages:

<table data-card-size="large" data-view="cards"><thead><tr><th data-type="content-ref"></th><th></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td><a href="/pages/lNVh0OsORVL2GOCoO5VU">/pages/lNVh0OsORVL2GOCoO5VU</a></td><td>External applications created by users to then be distributed through MOTAR.</td><td><a href="/files/C29kjRnRYoxZdWTU7gPV">/files/C29kjRnRYoxZdWTU7gPV</a></td></tr><tr><td><a href="/pages/Ghbw7FbWpPS3ZhYNisjo">/pages/Ghbw7FbWpPS3ZhYNisjo</a></td><td>Model listings allow users to share FBX, GLB, and GLTF file types.</td><td><a href="/files/zQOPQwsR4mKuCiMuM0ZR">/files/zQOPQwsR4mKuCiMuM0ZR</a></td></tr><tr><td><a href="/pages/V9rVvZ0Dm8O9FdSdZAq3">/pages/V9rVvZ0Dm8O9FdSdZAq3</a></td><td>Video listings allow users to upload Standard or 360 video files that can be managed by specified studio groups or solely for personal use.</td><td><a href="/files/x7TkUJufvwkekJNTz7QR">/files/x7TkUJufvwkekJNTz7QR</a></td></tr><tr><td><a href="/pages/yQlselzdCBCZQYMsg5OD">/pages/yQlselzdCBCZQYMsg5OD</a></td><td>Image listings allow users to upload and share image files.</td><td></td></tr><tr><td><a href="/pages/ZcyQflp6ldjpCuXlNF2x">/pages/ZcyQflp6ldjpCuXlNF2x</a></td><td>Audio listings allow users to upload and share audio files.</td><td><a href="/files/qODPHIjhwgDh1hrSJnwv">/files/qODPHIjhwgDh1hrSJnwv</a></td></tr><tr><td><a href="/pages/LdKvW602Oa3UcH542cDJ">/pages/LdKvW602Oa3UcH542cDJ</a></td><td>Document listings allow users to upload and share documents.</td><td><a href="/files/GdbLkMHLVQGs50EqcSuY">/files/GdbLkMHLVQGs50EqcSuY</a></td></tr></tbody></table>


# App

External applications created by users to then be distributed through MOTAR.

{% hint style="info" %}
Each listing type has required fields that must be completed before the listing can be either saved or promoted to Production. If any required fields are left blank a red i icon will be marked on the corresponding tab to remind the user what still needs to be filled out.
{% endhint %}

## New Hub Listing

### Create <a href="#create" id="create"></a>

To begin creating a new listing:

* Go to the "My Listings" page.
* **Click** on the "APP" icon.

This action starts the create listing process.

<figure><img src="/files/K8Ku7xJmfJrwqCcV0N2t" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/Tb4QcesSC6VQzi4o4UY0" alt="" width="563"><figcaption></figcaption></figure>

### Listing Type Modal

{% hint style="info" %}
For app listings, the user is currently only able to create remixes of their own app or apps that belong to their Studio Group.
{% endhint %}

Clicking on the App icon on the My Listings page will show this flow to the user. The "Listing Type" modal will open allowing the user to **Select** whether this will be a new listing, new version of existing listing, or remix of someone else’s listing.&#x20;

<figure><img src="/files/3DQTWe9AOx9nbO04peBG" alt=""><figcaption></figcaption></figure>

### Required Fields

The following required fields must be entered before an application listing can be created. Enter all fields and then **click** "Create" to create the initial application listing.

### Info

On the **Info** tab, users are required to fill in a **Listing Name, Listing Description,** **Upload** a thumbnail, and **Select** whether or not the app runs in a web browser. Optional fields include **3D Preview, Preview Images,** and **Preview Videos**.

{% hint style="info" %}
Progress on an app listing can be saved once the user has named the listing, filled out a listing description, and uploaded a thumbnail. This allows the user to fill out all additional fields for their app listing at a later time. It is important to note that an app listing **cannot** be promoted from Sandbox to Production until all of the app listing’s required fields have been filled out.
{% endhint %}

<figure><img src="/files/K0yPy1zcxECjur833PA4" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/naODEm1svHojR6CXDYNh" alt=""><figcaption></figcaption></figure>

### Settings

On the "Settings" tab, the user will be able to view the "permissions scopes" and the "Keys" associated with the app listing. These keys are used to connect your app to the MOTAR SDK for Unity.

<figure><img src="/files/HlJidLgAGQnN5Zdf8Shb" alt=""><figcaption></figcaption></figure>

### Distributions

On the **Distributions** tab, the user will be able to Add New Distributions, View Distributions, Delete Distributions, and Edit the Release Notes, System Requirements, and Installation Instructions of Distributions.

<figure><img src="/files/8x1tl8tjsMyJ0j1JeAFF" alt=""><figcaption></figcaption></figure>

**Click** the "+ Add Distribution" button to launch the "Add Distribution" modal.

Select **APK, EXE, or URL** depending on your application type.

#### APK

Accepted file type(s): \*.**apk**

<figure><img src="/files/KY79lOrq4A7vZDXq5Lj3" alt=""><figcaption></figcaption></figure>

* **Click** "Upload Build" and set **Package Name/Bundle Identifier**&#x20;

{% hint style="warning" %}

#### WARNING!

**Package Name** is required to launch an app via MOTAR 3D. Package Name must match EXACTLY what is compiled with your app.
{% endhint %}

<figure><img src="/files/tuy33EG8ixpCqdiJimo5" alt=""><figcaption></figcaption></figure>

* **Release Notes, and Supported Devices** depending on the app type being created.&#x20;
* The user is also able to denote any **Installation Instructions**&#x20;
* **Launch With MOTAR 3D** (enabled by default for standalone XR applications)
* **Recommended System Requirements** that are compatible with their App.

#### EXE

Accepted file type(s): \*.exe, \*.zip, \*.msi

<figure><img src="/files/Dz36NojDYiu3rEvA1Sfz" alt=""><figcaption></figcaption></figure>

#### URL

Accepted file type(s): **NONE**

Accepts secure "HTTPS" URL's only.

<figure><img src="/files/278L9d0hTqTMAPlQ8elL" alt=""><figcaption></figcaption></figure>

#### Supported Devices

<figure><img src="/files/tYVAekrsfxNenVlEIV8a" alt=""><figcaption></figcaption></figure>

* **Select** compatible devices for your application.
  * Example: a URL based XR application may select  Mobile Browser and Meta Quest 3

{% hint style="info" %}
Supported Devices can only be selected by one distribution at a time. If the user wishes to have a second distribution with the same Build or Supported Devices, a New Version or Remix of the app listing will need to be made.
{% endhint %}

***

**Edits** to Distribution informations after saving.

If the User wishes to change the Package Name/Bundle Identified, Release Notes, and Recommended System Requirements they can click on the pencil icon to edit.

<figure><img src="/files/lyg3pbKw1ct4uifbt7xa" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
Listings will be in **Sandbox** until they have been promoted and **approved** for **Production**.\
If the app listing is in the **Sandbox | Under Review** for Production or **Production | Published** status the user will be unable to make changes to or delete the distributions added to the app listing.
{% endhint %}

### SDKs

On the SDKS tab, the user will be able to view and access MOTARs prebuilt SDKs in order to assist with app development.

{% hint style="info" %}
To learn more about MOTAR SDK,[ click here.](broken://pages/yqZucIEU1WtO4Nu8Qxw0)
{% endhint %}

<figure><img src="/files/3U2ZACMPnlsWQMeM30cS" alt=""><figcaption></figcaption></figure>

### Permissions

On the "Permissions" Tab, **Click** the "Launch" button to run the Permissions Wizard. Full instructions can be found at the link below.

{% content-ref url="/pages/w1QhZr1b8TwwfUsIBSmd" %}
[Listing Permissions](/motar-core-services/intro-to-core-services/studio/listing-permissions)
{% endcontent-ref %}

{% hint style="info" %}
The Hub Visibility toggle is located on the top right of a listing's edit page after initial permissions are set. The default is **OFF** for public visibility on Sandbox listings. The default is **ON** for public visibility on Production listings.
{% endhint %}

<figure><img src="/files/xAA1eNKpLekps2KgapYR" alt=""><figcaption></figcaption></figure>

### Digital Thread

* The **current version** of the listing
* Any future **versions** or **remixes** created from it

The **Digital Thread** tab provides a centralized view of a listing’s **entire digital lifecycle**.\
It captures and displays:

When creating a **new listing**, this tab will initially show **only that listing**.\
As you or others create new versions or remixes, those will be added to this view automatically.

You can return to the **Digital Thread** tab at any time by **choosing** to "Edit" the listing from the "My Listings" page.

{% hint style="info" %}
From the Digital Thread tab, users can **set a listing as Authoritative or Certified**—but only **after it has been promoted to Production**.

For more guidance on how to authorize or certify a listing, click [here](/motar-core-services/intro-to-core-services/studio/digital-thread/authoritative-and-certified-listings).
{% endhint %}

<figure><img src="/files/FZaa3hrQ5ls4fTnV4IZB" alt=""><figcaption></figcaption></figure>

### Submit for Review

Once all the required information has been completed for an app listing and the listing is in the Sandbox|Testing on MOTAR Training status, the "Submit for Review" button will become available to the user.

<figure><img src="/files/mqIMHvye98RRMYQwlY49" alt=""><figcaption></figcaption></figure>

The Submit for Review button will launch the "Submit for Review" modal. **Selecting** "Continue" will prompt MOTAR Admins to review, approve, or reject the App Listing.

<figure><img src="/files/yECK2Km4OwIXb4AozNCb" alt=""><figcaption></figcaption></figure>

Status of an App Listing will update to **Sandbox|Under Review** for Production during this time.

<figure><img src="/files/3NIANSjx21GUzPup2MqI" alt=""><figcaption><p>Listing In Review</p></figcaption></figure>

During the review process, your listing will not be editable.

<figure><img src="/files/Q8UXx36q5VnYtOQNHX2q" alt=""><figcaption><p>Listing Details - Under Review</p></figcaption></figure>

{% hint style="info" %}
Once an app listing has been submitted for review the user will be unable to edit or change any of the information, distributions, or permissions that have been input up to this point until the App is either approved or rejected by a MOTAR Admin.
{% endhint %}

### Publish

Once an app listing has reached the Sandbox|Ready to Publish on Production status, the Publish button will become available to the user.&#x20;

Users will be able to **Publish** their listing which will promote the listing from the Sandbox to Production.&#x20;

<figure><img src="/files/mw03e6vXIbXRpQBQLXUY" alt=""><figcaption><p>App Approved | Unpublished</p></figcaption></figure>

<figure><img src="/files/pIbEX0UXvTQBluUkepZL" alt=""><figcaption></figcaption></figure>

Clicking Publish will open the **Permissions for Production** modal. From here the user will be able to choose to keep current or set new permissions.

<figure><img src="/files/v7nACOrkuf5F0lKKPwDv" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Setting new permissions will overwrite the existing permissions for the listing. Full instructions on how to run the Permissions Wizard can be found at the link below.
{% endhint %}

{% content-ref url="/pages/w1QhZr1b8TwwfUsIBSmd" %}
[Listing Permissions](/motar-core-services/intro-to-core-services/studio/listing-permissions)
{% endcontent-ref %}

The modal will close and the listing will be updated from Sandbox to Production.

## Edit

To edit a listing, **Click** the "Pencil" icon in the "Action" column in the "My Listings" table. The table can be accessed from the MOTAR Studio "My Listings" page.

Make any desired changes in the **Info, Settings, Distribution, Permissions,** and/or **Digital Thread** tabs. The user can navigate between tabs by either **Clicking** the "tab title" or **CLICKING** the "Next" button.

{% hint style="danger" %}
If the app listing is in the Sandbox|Under Review the user will be unable to make any changes to the app listing until it is either approved or rejected by a MOTAR Admin. If the app listing is in the Production|Ready status the user will be unable to delete the distributions added to the app listing.
{% endhint %}

<figure><img src="/files/xmFK7mTM87hyy6xWpFrb" alt=""><figcaption><p>Editing a Sandbox Listing (unreviewed/unpublished)</p></figcaption></figure>

<figure><img src="/files/9ORyerdYxaD3GsMU8uBg" alt=""><figcaption></figcaption></figure>

If the user desires to update permissions settings, **Click** the "Modify" button in the "Permissions" tab to run the Permissions Wizard. Full instructions can be found at the link below.

{% content-ref url="/pages/w1QhZr1b8TwwfUsIBSmd" %}
[Listing Permissions](/motar-core-services/intro-to-core-services/studio/listing-permissions)
{% endcontent-ref %}

Once desired edits have been made, **Click** the "Save" button to save all requested changes and update the App Listing.

## Delete

To delete a listing, **Click** the "Pencil" icon in the "Action" column in the My Listings table. Navigate to the "Digital Thread" tab, **Click** the "Trash Can" icon in the "Action" column of the **"**&#x44;igital Thread" tab. A Delete Listing modal will be displayed.

<figure><img src="/files/steVojBDSLeCXNuDsb1W" alt=""><figcaption></figcaption></figure>

To confirm deletion of the listing, **type** the word "Delete" in the text field. This will activate the "Delete" button which can then be **Clicked**.

<figure><img src="/files/6ub0vV4wFsMaHNHZpoLl" alt=""><figcaption><p>Deleting a Listing</p></figcaption></figure>

The user will be returned to the MOTAR Studio "My Listings" page. The listing has been deleted and will no longer be displayed in the My Listings table.


# Model

Model listings allow users to share FBX, GLB, and GLTF file types.

{% hint style="info" %}
Each listing type has required fields that must be completed before the listing can be either saved or promoted to Production. If any required fields are left blank a red i icon will be marked on the corresponding tab to remind the user what still needs to be filled out.
{% endhint %}

## New Hub Listing <a href="#new-hub-listing" id="new-hub-listing"></a>

### Create <a href="#create" id="create"></a>

To begin creating a new listing:

* Go to the **MY LISTINGS** page.
* Click on the **MODEL** icon.

This action starts the **create listing** process.

<figure><img src="/files/NxCSAfb0DXH4TggPLcLt" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/IyyGiQiFPmCT0a0gEBju" alt="" width="563"><figcaption></figcaption></figure>

### Listing Type Modal <a href="#listing-type-modal" id="listing-type-modal"></a>

{% hint style="info" %}
This flow covers **how to create a New Hub Listing**.\
For details on creating a **New Version** or a **Remix**, refer to the additional guides linked below.\
[New Version](/motar-core-services/intro-to-core-services/studio/digital-thread/new-version) or [Remix](/motar-core-services/intro-to-core-services/studio/digital-thread/remix).
{% endhint %}

After clicking the **Model** icon:

* The **LISTING TYPE** modal will appear.
* Choose the type of listing to create:
  * **New Hub Listing**
  * **New Version** of an existing listing
  * **Remix** of another user's listing

<figure><img src="/files/5h98UfgGwMxVFzYOnaIg" alt=""><figcaption></figcaption></figure>

To proceed:

1. **Select** the **NEW HUB LISTING** option.
2. Click the **NEXT** button to continue to the next step in the creation flow.

### Upload <a href="#upload" id="upload"></a>

To begin uploading:

* Click the **UPLOAD** button on the Upload tab.

#### Supported File Formats

You can upload files in any of the following formats:

* **FBX**
* **OBJ**
* **ZIP**
* **GLTF / GLB**
* **Most CAD formats**

Make sure your file meets the format requirements to avoid upload errors.

<figure><img src="/files/ItQBYcBd7Ifqqxozv1P2" alt=""><figcaption></figcaption></figure>

### Info

After uploading a file, you can begin filling in the "Info" tab.

{% hint style="info" %}
The **Listing Name** will auto-populate based on the file uploaded in the **UPLOAD** tab.\
However, you can **edit this name** to something more descriptive or user-friendly if desired.
{% endhint %}

<figure><img src="/files/SZiCVg1wwF8kpMfA7Rb7" alt=""><figcaption></figcaption></figure>

#### Required Fields

Fields marked with a <mark style="color:red;">**red**</mark> **asterisk \[**<mark style="color:red;">**\***</mark>**]** are **required** and must be completed before creating the listing:

* **Name**
* **Description**
* **Thumbnail**

Once these fields are filled out, you can **click** **"**&#x43;reat&#x65;**"** to finalize your asset listing.

{% hint style="warning" %}
To ensure **MOTAR 3D Holodeck compatibility**, you **must upload a 3D Preview**.

Accepted 3D preview formats:

* **GLB** (single file)
* **GLTF** (single file)\
  Textures and animations are supported.
  {% endhint %}

You can **save your progress** once you’ve:

* Uploaded a file
* Named the listing
* Added a description
* Uploaded a thumbnail

This allows you to return later and complete additional fields as needed.

{% hint style="danger" %}
A listing **cannot be promoted** from **Sandbox** to **Production** until **all required fields** have been completed.
{% endhint %}

### Settings

From the "Settings" tab, you can define important technical details about your model listing.

You’ll be able to:

* **Select Geometry Type**:\
  Choose between **Polygons** or **Triangles**
* **Enter Polycount**:\
  Specify the total polygon or triangle count for your model
* **Mark Asset Features**:\
  Indicate whether your model **includes Textures** and/or **Animations**

{% hint style="info" %}
**Textures** and **Animations** are **not required** for submitting a model listing, but including them may enhance listing compatibility and appeal.
{% endhint %}

<figure><img src="/files/AQT6xL2ZbahdmR4ODJ4w" alt=""><figcaption></figcaption></figure>

### Permissions

To configure access controls for your listing:

* **Navigate** to the "Permissions" tab.
* **Click** the "Launch" button to open the **Permissions Wizard**.

Need a step-by-step guide?

{% content-ref url="/pages/w1QhZr1b8TwwfUsIBSmd" %}
[Listing Permissions](/motar-core-services/intro-to-core-services/studio/listing-permissions)
{% endcontent-ref %}

After setting the appropriate permissions in the wizard:

* **Click** the "Save" button to apply your changes.
* This will also enable the option to adjust **Hub Visibility** for your listing.

{% hint style="info" %}
Once permissions are saved, the **Hub Visibility** toggle will appear in the **top right corner** of the listing’s edit page.

* **Sandbox Listings:** Visibility is **OFF** by default (not publicly visible).
* **Production Listings:** Visibility is **ON** by default (publicly visible).
  {% endhint %}

<figure><img src="/files/unNYJwZbrYAqKdSEElQe" alt=""><figcaption><p>Hub Visibility OFF</p></figcaption></figure>

<figure><img src="/files/HKOeiq1QddB7MIsMxIIt" alt=""><figcaption><p>Hub Visibility ON</p></figcaption></figure>

### Digital Thread

* The **current version** of the listing
* Any future **versions** or **remixes** created from it

The "Digital Thread" tab provides a centralized view of a listing’s **entire digital lifecycle**.\
It captures and displays:

When creating a **new listing**, this tab will initially show **only that listing**.\
As you or others create new versions or remixes, those will be added to this view automatically.

You can return to the **Digital Thread** tab at any time by **choosing** to "Edit" the listing from the "My Listings" page.

{% hint style="info" %}
From the Digital Thread tab, users can **set a listing as Authoritative or Certified**—but only **after it has been promoted to Production**.

For more guidance on how to authorize or certify a listing, click [here](/motar-core-services/intro-to-core-services/studio/digital-thread/authoritative-and-certified-listings).
{% endhint %}

<figure><img src="/files/tFpB5JzopfN68juGsHQZ" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
See the following links for more information on [Digital Thread](/motar-core-services/intro-to-core-services/studio/digital-thread/iconology) and the [Digital Thread Iconology](/motar-core-services/intro-to-core-services/studio/digital-thread/iconology).
{% endhint %}

{% hint style="warning" %}
All listings remain in **Sandbox** until they are **promoted and approved for Production**. This means their authoritative or certified status cannot be applied until that transition happens.
{% endhint %}

### Publish

Once all **required information** for a listing is complete and the listing has been **saved**, the "Publish" button becomes available.

Publishing a listing moves it from **Sandbox** to **Production**, making it officially available for wider access.

{% hint style="danger" %}
After publishing, users will **no longer be able to change files** on the "Upload" tab.\
However, you **can still update**:

* Description on the "Info" tab
* Listing **permissions**
  {% endhint %}

To publish:

* **Click** the "Publish" button.

<figure><img src="/files/ksoAh4RYVXe4u72iNmty" alt=""><figcaption></figcaption></figure>

* The **Permissions for Production** modal will open.
* Choose between:
  * Keep Current permissions
  * Set New permissions
* For this example, **select** "Keep Current" and then **click** "Next".

<figure><img src="/files/pqrD2JNtaxbGZC2IiP6U" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
Choosing **SET NEW** permissions will **overwrite the existing permissions** for the listing.

Need help setting new permissions?

Full instructions on how to run the Permissions Wizard can be found at the link below.
{% endhint %}

{% content-ref url="/pages/w1QhZr1b8TwwfUsIBSmd" %}
[Listing Permissions](/motar-core-services/intro-to-core-services/studio/listing-permissions)
{% endcontent-ref %}

The modal will close and the listing will be updated from Sandbox to Production.

<figure><img src="/files/zpRPOUZMrsTYmKZMKz2M" alt=""><figcaption></figcaption></figure>

***

### Edit

To begin editing a listing:

* Go to the **MOTAR Studio –** "My Listings" page.
* Find your listing in the table.
* **Click** the "Pencil" icon in the "Action" column.

<figure><img src="/files/KGH0iiHKvPgCPLSUHAmp" alt=""><figcaption></figcaption></figure>

#### Editing Options

You can make changes in any of the following tabs:

* **Upload**
* **Info**
* **Settings**
* **Permissions**
* **Digital Thread**

<figure><img src="/files/dB3wP78kvE1NxYWku0yZ" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
If the user desires to update permissions settings, **CLICK** the **MODIFY** button in the **PERMISSIONS** tab to run the Permissions Wizard. Full instructions can be found at the link below.
{% endhint %}

{% content-ref url="/pages/w1QhZr1b8TwwfUsIBSmd" %}
[Listing Permissions](/motar-core-services/intro-to-core-services/studio/listing-permissions)
{% endcontent-ref %}

Once all desired changes have been made, **click** the "Save" button.\
This will apply your edits and update the listing accordingly.

***

## Delete

To delete a listing:

* Go to the **MOTAR Studio –** "My Listings" page.
* **Click** the "Pencil" icon in the "Action" column to edit the listing.

<figure><img src="/files/KGH0iiHKvPgCPLSUHAmp" alt=""><figcaption></figcaption></figure>

* **Navigate** to the "Digital Thread" tab.
* **Click** the "Trash Can" icon in the "Action" column.

<figure><img src="/files/MPZH5iQr50lVubV7xPB7" alt=""><figcaption></figcaption></figure>

This will open the **Delete Listing** modal.

To confirm the deletion:

* **Type** the word `DELETE` into the confirmation text field.
* This will activate the "Delete" button.
* **Click** "Delete" to complete the action.

<figure><img src="/files/efXNv7ucOkNU3lCZDsav" alt=""><figcaption></figcaption></figure>

Once deleted:

* You’ll be returned to the "Digital Thread" tab.
* The listing will appear as archived both in the Digital Thread and on the My Listings page.

<figure><img src="/files/u2pQ5P7RGiXuiLk7l4Js" alt=""><figcaption></figcaption></figure>


# Video

Video listings allow users to upload Standard or 360 video files that can be managed by specified studio groups or solely for personal use.

## New Hub Listing

### Create <a href="#create" id="create"></a>

To begin creating a new listing:

* Go to the "My Listings" page.
* **Click** on the "Video" icon.

This action starts the **create listing** process.

<figure><img src="/files/2Dr2ieyyC9IeEIMvMX52" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/PEWa8kxVc6odBZCcAT8x" alt="" width="563"><figcaption></figcaption></figure>

### Listing Type Modal

{% hint style="info" %}
This page will be reviewing the creation flow of a New Hub Listing. These links can be used to learn more about how to create a [New Version](/motar-core-services/intro-to-core-services/studio/digital-thread/new-version) or [Remix](/motar-core-services/intro-to-core-services/studio/digital-thread/remix).
{% endhint %}

**Clicking** on the Video icon on the My Listings page will show this flow to the user. The "Listing Type" modal will open allowing the user to **Select** whether this will be a new listing, new version of existing listing, or remix of someone else’s listing. **Select** the "New Hub Listing" option and **Click** the **Next** button.

<figure><img src="/files/bQXAi3hpGhlOCO9VcSur" alt=""><figcaption></figcaption></figure>

### Upload

After a New Hub Listing type is chosen, the user will be brought to the "Upload" tab and is required to upload a supported video file type.

<figure><img src="/files/jtMEgJFqcSBLWdMG41Pc" alt=""><figcaption></figcaption></figure>

The File Upload and Scanning Tool will launch (see link below for additional instructions, if needed).  Once the scan is successfully completed, the modal can be closed and the document will be listed.

{% content-ref url="/pages/lbE42dn6cJmSUnh4APkS" %}
[Secure File Upload & Scanning](/motar-core-services/intro-to-core-services/studio/secure-file-upload-and-scanning)
{% endcontent-ref %}

### Info

{% hint style="info" %}
The Listing Name for the listing will be auto-populated to match the name of the file that was uploaded on the "Upload" tab but can be edited at this time to a preferred listing name.
{% endhint %}

<figure><img src="/files/wE2ejfajICA0ZFB08cSw" alt=""><figcaption></figcaption></figure>

On the "Info" tab, users are required to fill in a Listing Name, Listing Description, and Upload a thumbnail.

{% hint style="info" %}
Progress on a listing can be saved once the user has uploaded a file, named the listing, filled out a listing description, and uploaded a thumbnail. This allows the user to fill out all additional fields for their listing at a later time. It is important to note that a listing **cannot** be promoted from Sandbox to Production until all of a listing’s required fields have been filled out.
{% endhint %}

<figure><img src="/files/t6UfOQcsgcPYcVGXfNis" alt=""><figcaption></figcaption></figure>

### Settings

On the "Settings' tab, users will need to **select** if the video is a Standard or a 360 video file.

<figure><img src="/files/4FsVclV90t3i6Lqy65xf" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/liF3ay8J62kf0jbtq5Wn" alt=""><figcaption></figcaption></figure>

### Permissions

On the "Permissions" Tab, **Click** the **"Launch"** button to run the Permissions Wizard. Full instructions can be found at the link below.

{% content-ref url="/pages/w1QhZr1b8TwwfUsIBSmd" %}
[Listing Permissions](/motar-core-services/intro-to-core-services/studio/listing-permissions)
{% endcontent-ref %}

Once permissions have been set, **Click** the "Save" button to save all requested changes and allow the user to set the Hub Visibility of the listing.

{% hint style="info" %}
The Hub Visibility toggle is located on the top right of a listing's edit page after initial permissions are set. The default is **off** for public visibility on Sandbox listings. The default is **on** for public visibility on Production listings.
{% endhint %}

<figure><img src="/files/GMI2Kp9APhC7ki5vtoYD" alt=""><figcaption></figcaption></figure>

### Digital Thread

* The current version of the listing
* Any future versions or remixes created from it

The "Digital Thread" tab provides a centralized view of a listing’s **entire digital lifecycle**.\
It captures and displays:

When creating a new listing, this tab will initially show **only that listing**.\
As you or others create new versions or remixes, those will be added to this view automatically.

You can return to the "Digital Thread" tab at any time by **choosing** to "edit" the listing from the "My Listings" page.

{% hint style="info" %}
From the Digital Thread tab, users can **set a listing as Authoritative or Certified**—but only **after it has been promoted to Production**.

For more guidance on how to authorize or certify a listing, click [here](/motar-core-services/intro-to-core-services/studio/digital-thread/authoritative-and-certified-listings).
{% endhint %}

<figure><img src="/files/Yrldwj7rqtLimtUyPw6G" alt=""><figcaption><p>Unpublished Digital Thread Tab</p></figcaption></figure>

<figure><img src="/files/sOb6t9S5tCuwp3kJhtrz" alt=""><figcaption><p>Published Digital Thread tab with settings</p></figcaption></figure>

{% hint style="info" %}
See the following links for more information on [Digital Thread](/motar-core-services/intro-to-core-services/studio/digital-thread) and the [Digital Thread Iconology](/motar-core-services/intro-to-core-services/studio/digital-thread/iconology).
{% endhint %}

### Publish

Once all required information for a listing is complete and the listing has been **saved**, the "Publish" button becomes available.

Publishing a listing moves it from **Sandbox** to **Production**, making it officially available for wider access.

{% hint style="danger" %}
After publishing, users will **no longer be able to change files** on the "Upload" tab.\
However, you can still update:

* Description on the "Info" tab
* Listing permissions
  {% endhint %}

To publish:

* **Click** the "Publish" button.

<figure><img src="/files/ksoAh4RYVXe4u72iNmty" alt=""><figcaption></figcaption></figure>

* The "Permissions for Production" modal will open.
* Choose between:
  * Keep current permissions
  * Set new permissions
* For this example, **select** "Keep Current" and then **click** "Next" .

<figure><img src="/files/pqrD2JNtaxbGZC2IiP6U" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
Choosing **set new** permissions will **overwrite the existing permissions** for the listing.

Need help setting new permissions?

Full instructions on how to run the Permissions Wizard can be found at the link below.
{% endhint %}

{% content-ref url="/pages/w1QhZr1b8TwwfUsIBSmd" %}
[Listing Permissions](/motar-core-services/intro-to-core-services/studio/listing-permissions)
{% endcontent-ref %}

The modal will close and the listing will be updated from Sandbox to Production.

<figure><img src="/files/QmikrJPUFIjXzFZ401CL" alt=""><figcaption></figcaption></figure>

***

## Edit

To edit a listing, **Click** the "✏️" icon in the action column in the "My Listings" table. The table can be accessed from the MOTAR Studio "My Listings" page.

{% hint style="warning" %}
Only **Unpublished** listings are fully editable. **Limited** changes are allowed on **Published** listings.
{% endhint %}

<figure><img src="/files/YxVnaMcX8w3Ifq2KcBQQ" alt=""><figcaption></figcaption></figure>

Make any desired changes in the "Upload", "Info", "Settings", "Permissions" and/or "Digital Thread" tabs. The user can navigate between tabs by either **Clicking** the tab title or **Clicking** the "Next" button.

<figure><img src="/files/uviT1AucXPwCXKXzJPPN" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
If the user desires to update permissions settings, **Click** the "Modify" button in the "Permissions" tab to run the Permissions Wizard. Full instructions can be found at the link below.
{% endhint %}

{% content-ref url="/pages/w1QhZr1b8TwwfUsIBSmd" %}
[Listing Permissions](/motar-core-services/intro-to-core-services/studio/listing-permissions)
{% endcontent-ref %}

Once desired edits have been made, **Click** the "Save" button to save all requested changes and update the Video Listing.

***

## Delete

To delete a listing, **Click** the "✏️" icon in the "Action" column in the My Listings Table.&#x20;

<figure><img src="/files/YxVnaMcX8w3Ifq2KcBQQ" alt=""><figcaption></figcaption></figure>

**Navigate** to the "Digital Thread" tab,&#x20;

**Click** the " 🗑️ " icon in the action column of the "Digital Thread" tab.&#x20;

A Delete Listing modal will be displayed.

<figure><img src="/files/J148qEbt5ACi1eafTY3g" alt=""><figcaption></figcaption></figure>

To confirm deletion of the listing, **Type** the word "Delete" in the text field. This will activate the "Delete" button which can then be **Clicked**.

<figure><img src="/files/nyO1LmdK2dKazDPAWYxA" alt=""><figcaption></figcaption></figure>

The user will be returned to the "Digital Thread" tab. The newly deleted listing will display as archived in the "Digital Thread" tab.

<figure><img src="/files/cLuKRsvR8A9NOlzZPiSt" alt=""><figcaption></figcaption></figure>

## Metrics

### [Listing Performance Metrics](/motar-core-services/intro-to-core-services/studio/listing-performance-metrics)

### [Learner Record](/motar-core-services/intro-to-core-services/profile/learner-record)


# Audio

Audio listings allow users to upload and share audio files.

## New Hub Listing

### Create

Audio listings allow users to upload and share audio files.

To start the creation process:

* Go to the "My Listings" page.
* **Click** on the Audio icon to begin.

<figure><img src="/files/gg3ghvEcK6Vflkbrdyjf" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/zHMFPtBmx4DiXl5iTBGP" alt="" width="563"><figcaption></figcaption></figure>

### Listing Type Modal

After clicking the "Audio" icon, the "Listing Type" modal will appear.\
In this modal, you can choose from the following options:

* New Hub Listing
* New Version of an existing listing
* Remix of another user's listing

<figure><img src="/files/5h98UfgGwMxVFzYOnaIg" alt=""><figcaption></figcaption></figure>

To create a new listing, **select** "New Hub Listing" and **click** "Next" to proceed.

{% hint style="info" %}
This guide focuses on creating a **New Hub Listing**. For details on creating a **New Version** or a **Remix**, check the additional resources linked below.\
[New Version](/motar-core-services/intro-to-core-services/studio/digital-thread/new-version) or [Remix](/motar-core-services/intro-to-core-services/studio/digital-thread/remix).
{% endhint %}

### Upload

After selecting the New Hub Listing option, you will be directed to the "Upload" tab.\
Here, you are required to upload a supported audio file.

<figure><img src="/files/XOluWVtWY2pbReOGJWti" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
The **File Upload and Scanning Tool** will launch to help with this process (see the link below for detailed instructions).
{% endhint %}

{% content-ref url="/pages/lbE42dn6cJmSUnh4APkS" %}
[Secure File Upload & Scanning](/motar-core-services/intro-to-core-services/studio/secure-file-upload-and-scanning)
{% endcontent-ref %}

Once the scan is completed successfully, you can **close** the modal, and the audio file will be listed.

### Info

After the file is uploaded, the "Info" tab will allow you to complete the following:

* The Listing Name will auto-populate to match the name of the file that was uploaded. *You can edit this name at this point to your preferred listing name.*
* Listing Description: Provide a brief description of the listing.

<figure><img src="/files/AdQNn9a69Zc7VYfzd3au" alt=""><figcaption></figcaption></figure>

You can **save** your progress after uploading the file, naming the listing, and filling in the description.\
This allows you to come back and complete any remaining fields later.

{% hint style="warning" %}
&#x20;A listing cannot be promoted from Sandbox to Production until all required fields have been completed.
{% endhint %}

### Permissions

To set permissions for your listing:

* **Navigate** to the "Permissions" tab.
* **Click** the "Launch" button to run the Permissions Wizard.

<figure><img src="/files/9SE831qVAP8qKvQNgvfA" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/kGxQ6RjAJqptd7COKddS" alt="" width="563"><figcaption></figcaption></figure>

Full instructions on how to use the wizard can be found below:

{% content-ref url="/pages/w1QhZr1b8TwwfUsIBSmd" %}
[Listing Permissions](/motar-core-services/intro-to-core-services/studio/listing-permissions)
{% endcontent-ref %}

Once you've configured the permissions:

* **Click** the "Save" button to apply all requested changes.
* This will enable the option to adjust the Hub Visibility for your listing.

{% hint style="info" %}
After saving permissions, you’ll see the **Hub Visibility** toggle in the **top right corner** of the listing’s edit page.

* **Sandbox Listings:** Hub visibility is **OFF** by default (not publicly visible).
* **Production Listings:** Hub visibility is **ON** by default (publicly visible).
  {% endhint %}

### Digital Thread

* The current version of the listing
* Any future versions or remixes created from it

The "Digital Thread" tab provides a centralized view of a listing’s **entire digital lifecycle**.\
It captures and displays:

When creating a new listing, this tab will initially show only that listing.\
As you or others create new versions or remixes, those will be added to this view automatically.

You can return to the "Digital Thread" tab at any time by **choosing** to "Edit" the listing from the "My Listings" page.

{% hint style="info" %}
From the Digital Thread tab, users can **set a listing as Authoritative or Certified**—but only **after it has been promoted to Production**.

For more guidance on how to authorize or certify a listing, click [here](/motar-core-services/intro-to-core-services/studio/digital-thread/authoritative-and-certified-listings).
{% endhint %}

<figure><img src="/files/uBwJz3KqOu3kloZyynm9" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
See the following links for more information on [Digital Thread](/motar-core-services/intro-to-core-services/studio/digital-thread/iconology) and the [Digital Thread Iconology](/motar-core-services/intro-to-core-services/studio/digital-thread/iconology).
{% endhint %}

{% hint style="warning" %}
All listings remain in **Sandbox** until they are **promoted and approved for Production**. This means their authoritative or certified status cannot be applied until that transition happens.
{% endhint %}

### Publish

Once all required information for a listing is complete and the listing has been **saved**, the "Publish" button becomes available.

Publishing a listing moves it from **Sandbox** to **Production**, making it officially available for wider access.

{% hint style="danger" %}
After publishing, users will **no longer be able to change files** on the "Upload" tab.\
However, you **can still update**:

* Description on the "Info" tab
* Listing permissions
  {% endhint %}

To publish:

* **Click** the "Publish" button.

<figure><img src="/files/ksoAh4RYVXe4u72iNmty" alt=""><figcaption></figcaption></figure>

* The "Permissions for Production" modal will open.
* Choose between:
  * Keep Current permissions
  * Set New permissions
* For this example, **select** "Keep Current" and then **click** "Next".

<figure><img src="/files/pqrD2JNtaxbGZC2IiP6U" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
**Choosing** "Set New" permissions will **overwrite the existing permissions** for the listing.

Need help setting new permissions?

Full instructions on how to run the Permissions Wizard can be found at the link below.
{% endhint %}

{% content-ref url="/pages/w1QhZr1b8TwwfUsIBSmd" %}
[Listing Permissions](/motar-core-services/intro-to-core-services/studio/listing-permissions)
{% endcontent-ref %}

The modal will close and the listing will be updated from Sandbox to Production.

<figure><img src="/files/SQFGFTNy4GeaASwFMog2" alt=""><figcaption></figcaption></figure>

***

## Edit

To edit an existing listing:

* Go to the "MOTAR Studio **–** My Listings" page.
* **Click** the " ✏️ " icon in the action column of the listing you want to edit.

<figure><img src="/files/kyYEWDUh6IjNXQ47pyBK" alt=""><figcaption></figcaption></figure>

You can make changes in the following tabs:

* Upload
* Info
* Permissions
* Digital Thread

Navigate between tabs by either:

* **Clicking** the tab title
* **Clicking** the "Next" button to move through the sections

{% hint style="info" %}
If you need to **update permissions**:

1. Go to the "Permissions" tab.
2. **Click** the "Modify" button to launch the Permissions Wizard modal.

Full instructions on using the wizard can be found below.
{% endhint %}

{% content-ref url="/pages/w1QhZr1b8TwwfUsIBSmd" %}
[Listing Permissions](/motar-core-services/intro-to-core-services/studio/listing-permissions)
{% endcontent-ref %}

After making your desired edits:

* **Click** the "Save" button to apply all changes and update the listing.

***

## Delete

To delete a listing:

* Go to the "My Listings" page in MOTAR Studio.
* **Click** the " ✏️ " icon in the action column for the listing you want to delete.
* **Navigate** to the "Digital Thread" tab.
* **Click** the " 🗑️ **"** CAN icon in the action column.

<figure><img src="/files/AnxtnkAGkHz9xbN56GqD" alt=""><figcaption></figcaption></figure>

A "Delete Listing" modal will appear.

To confirm:

* **Type** the word `DELETE` in the text field.
* This will activate the "Delete" button.
* **Click** the "Delete" button to confirm the deletion.

<figure><img src="/files/aB6C3DNbf6ntD5p0XoMr" alt=""><figcaption></figcaption></figure>

Once deleted:

* You’ll be returned to the "Digital Thread" tab.
* The listing will now display as archived in:
  * The "Digital Thread" tab
  * The "My Listings" page

<figure><img src="/files/UgUDRXhV1WKJi6Iu36TB" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
Mobile Users: Control volume while viewing an Audio listing using the physical buttons on the device.&#x20;
{% endhint %}


# Image

### Create

To start the creation process:

* Go to the "My Listings" page.
* **Click** the "Image" icon to begin creating a new image listing.

<figure><img src="/files/HZ83dCtKb3NeuaabhFoY" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/kLEO67BUloVuEogS1cWm" alt="" width="563"><figcaption></figcaption></figure>

### Listing Type Modal

{% hint style="info" %}
This page will be reviewing the creation flow of a New Hub Listing. These links can be used to learn more about how to create a [New Version](/motar-core-services/intro-to-core-services/studio/digital-thread/new-version) or [Remix](/motar-core-services/intro-to-core-services/studio/digital-thread/remix).
{% endhint %}

* The "Listing Type" modal will appear.

In this modal, you can choose from the following options:

* New Hub Listing
* New Version of an existing listing
* Remix of another user's listing

<figure><img src="/files/5h98UfgGwMxVFzYOnaIg" alt=""><figcaption></figcaption></figure>

To create a new listing, **select** New Hub Listing and **click** "Next" to proceed.

### Upload

* After selecting your listing type, you’ll be taken to the "Upload" tab.
* Upload a supported image file (e.g., JPG, PNG, TIF, GIF, SVG,).

<figure><img src="/files/Xqr2DlRrsatklQY8yKSu" alt=""><figcaption></figcaption></figure>

* The File Upload and Scanning Tool will launch automatically.
* Once scanning is complete, close the modal. Your image file will now be listed.

{% hint style="info" %}
For more help, refer to the scanning tool instructions linked below
{% endhint %}

{% content-ref url="/pages/lbE42dn6cJmSUnh4APkS" %}
[Secure File Upload & Scanning](/motar-core-services/intro-to-core-services/studio/secure-file-upload-and-scanning)
{% endcontent-ref %}

### Info

* The "Info" tab will be activated.
* The Listing Name is auto-filled based on your uploaded file’s name but can be edited.

#### Required Fields:

* Listing Name
* Description

{% hint style="info" %}
Once the required fields are completed, you can save your progress and return later to finish optional fields.

⚠️ *Note:* The listing **cannot be promoted to Production** until all required fields are completed.
{% endhint %}

<figure><img src="/files/Q3V1KkeT12Ae7CSy8V56" alt=""><figcaption></figcaption></figure>

{% content-ref url="/pages/w1QhZr1b8TwwfUsIBSmd" %}
[Listing Permissions](/motar-core-services/intro-to-core-services/studio/listing-permissions)
{% endcontent-ref %}

### Settings

On the "settings" tab, users will need to select the image type and set the Width & Height.

{% hint style="info" %}
Settings for images are optional.
{% endhint %}

<figure><img src="/files/eeISSOaKk4h65IpBXMoL" alt=""><figcaption></figcaption></figure>

### Permissions

On the "Permissions" Tab, **Click** the "Launch" button to run the Permissions Wizard. Full instructions can be found at the link below.

{% content-ref url="/pages/w1QhZr1b8TwwfUsIBSmd" %}
[Listing Permissions](/motar-core-services/intro-to-core-services/studio/listing-permissions)
{% endcontent-ref %}

Once permissions have been set, **Click** the "Save" button to save all requested changes and allow the user to set the Hub Visibility of the listing.

{% hint style="info" %}
The Hub Visibility toggle is located on the top right of a listing's edit page after initial permissions are set. The default is **OFF** for public visibility on Sandbox listings. The default is **ON** for public visibility on Production listings.
{% endhint %}

<figure><img src="/files/GMI2Kp9APhC7ki5vtoYD" alt=""><figcaption></figcaption></figure>

### Digital Thread

* The current version of the listing
* Any future versions or remixes created from it

The "Digital Thread" tab provides a centralized view of a listing’s entire digital lifecycle.\
It captures and displays:

When creating a new listing, this tab will initially show only that listing.\
As you or others create new versions or remixes, those will be added to this view automatically.

You can return to the "Digital Thread" tab at any time by choosing to "Edit" the listing from the "My Listings" page.

{% hint style="info" %}
From the Digital Thread tab, users can **set a listing as Authoritative or Certified**—but only **after it has been promoted to Production**.

For more guidance on how to authorize or certify a listing, click [here](/motar-core-services/intro-to-core-services/studio/digital-thread/authoritative-and-certified-listings).
{% endhint %}

<figure><img src="/files/Au3oJ0VjSaETcopVDSVV" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/KykWSPC59AH4eH0iuMln" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
See the following links for more information on [Digital Thread](/motar-core-services/intro-to-core-services/studio/digital-thread) and the [Digital Thread Iconology](/motar-core-services/intro-to-core-services/studio/digital-thread/iconology).
{% endhint %}

### Publish

Once all required information for a listing is complete and the listing has been **Saved**, the "Publish" button becomes available.

Publishing a listing moves it from Sandbox to Production, making it officially available for wider access.

{% hint style="danger" %}
After publishing, users will **no longer be able to change files** on the "Upload" tab.\
However, you **can still update**:

* Description on the "Info" tab
* Listing permissions
  {% endhint %}

To publish:

* **Click** the "Publish" button.

<figure><img src="/files/ksoAh4RYVXe4u72iNmty" alt=""><figcaption></figcaption></figure>

* The "Permissions for Production" modal will open.
* Choose between:
  * Keep Current permissions
  * Set New permissions
* For this example, **select** "Keep Current" and then **click** "Next".

<figure><img src="/files/pqrD2JNtaxbGZC2IiP6U" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
Choosing **set new** permissions will overwrite the existing permissions for the listing.

Need help setting new permissions?

Full instructions on how to run the Permissions Wizard can be found at the link below.
{% endhint %}

The modal will close and the listing will be updated from Sandbox to Production.

<figure><img src="/files/2mTZpreVhxOH2KzSZ2wm" alt=""><figcaption></figcaption></figure>

***

## Edit

{% hint style="danger" %}
Only edits to the description are allowed once an image is **Published.**
{% endhint %}

To make changes:

1. Go to "My Listings"
2. Click the " ✏️ " icon in the *Action* column.
3. Modify content in:
   * Upload
   * Info
   * Permissions
   * Digital Thread

<figure><img src="/files/jNND54liJD7tLXD9hvLV" alt=""><figcaption></figcaption></figure>

To modify permissions:

* **Open** the "Permissions" tab
* **Click** "Modify" to rerun the Permissions Wizard

{% hint style="info" %}
Full instructions can be found at the link below.
{% endhint %}

{% content-ref url="/pages/w1QhZr1b8TwwfUsIBSmd" %}
[Listing Permissions](/motar-core-services/intro-to-core-services/studio/listing-permissions)
{% endcontent-ref %}

After making changes, **click** "Save".

***

## Delete

To delete a listing:

* Go to "My Listings"
* **Click** the " ✏️ " icon
* Go to the "Digital Thread" tab
* Click the " 🗑️ " can in the *Action* column

<figure><img src="/files/DJy3UC2H2t56mhIRa5fy" alt=""><figcaption></figcaption></figure>

* Type `DELETE` in the confirmation text field.
* This activates the "Delete" button. **Click** it.

<figure><img src="/files/ptkqPIyfAuEtv7i3HrdQ" alt=""><figcaption></figcaption></figure>

You’ll be returned to the "Digital Thread" tab.\
The listing will now appear as **archived** in:

* The Digital Thread
* The My Listings page

<figure><img src="/files/74yIOjlyul1ljW4D1ton" alt=""><figcaption></figcaption></figure>


# 360 Images

### 🌐 1. Where to Find Free 360° Images

Free resources are great for prototyping and personal projects. Most of these use Creative Commons licensing, but always double-check if attribution is required.

| **Source**                                                                                       | **Best For**                                           | **License Type**    |
| ------------------------------------------------------------------------------------------------ | ------------------------------------------------------ | ------------------- |
| [Poly Haven](https://polyhaven.com/hdris)                                                        | High-quality outdoor/indoor environments (HDRIs).      | CC0 (Public Domain) |
| [Flickr (360 Group)](https://www.google.com/search?q=https://www.flickr.com/groups/360-degrees/) | Diverse, user-generated content from around the world. | Varies (Check CC)   |
| [Unsplash](https://unsplash.com/s/photos/360-panorama)                                           | Modern, aesthetic 360° panoramas.                      | Unsplash License    |
| [Pixabay](https://www.google.com/search?q=https://pixabay.com/images/search/360%2520panorama/)   | General purpose landscapes and cityscapes.             | Pixabay License     |

> 💡 Pro Tip: Search for "Equirectangular" or "360 Panorama" instead of just "360" to avoid getting standard wide-angle photos.

***

### 💰 2. Where to Find Paid / Premium 360° Images

For commercial applications where you need legal protection and unique, high-resolution content, these professional stock sites are the industry standard.

* [Adobe Stock](https://stock.adobe.com/): Excellent integration if your team already uses Creative Cloud. Search for "360 degree panorama."
* [Shutterstock](https://www.shutterstock.com/): One of the largest libraries available. They offer 360° images specifically formatted for VR and web viewers.
* [Getty Images](https://www.gettyimages.com/): The "Gold Standard" for editorial and high-end commercial 360° content.
* [Kuula.co](https://kuula.co/explore): A dedicated 360° platform. While primarily for hosting, many professional photographers sell or license their work directly through the community.

***

### 🤖 3. Generating 360° Images with AI

In 2026, AI is one of the fastest ways to get a custom, royalty-free 360° environment without picking up a camera.

* [Blockade Labs (Skybox AI)](https://www.blockadelabs.com/): The current leader in 360° generation. You can type a prompt (e.g., *"Cyberpunk city at night, 8k, highly detailed"*) and it generates a seamless equirectangular image in seconds.
* Adobe Firefly: Now supports generating panoramic expansions that can be stitched into 360° environments.

***

### 📸 4. Creating Your Own (DIY)

If you need a specific location (like your office or a project site), creating your own is often the best route.

#### Option A: Smartphone Apps (Free/Cheap)

* Google Street View App (Legacy/Replacement): Many modern camera apps (iPhone/Android) have a "360" or "Panorama" mode that handles stitching automatically.
* Panorama 360 & Virtual Tours: A popular third-party app for capturing and stitching 360° photos on the fly.

#### Option B: Dedicated Hardware (Best Quality)

* Insta360 X4 / RS: Consumer-friendly cameras that capture 360° in one click.
* Ricoh Theta Z1: The professional choice for real estate and virtual tours due to its superior image sensors.

***

### 🛠 5. Technical Requirement

To ensure your images look correct, follow these specs:

* Projection: Must be Equirectangular (looks like a distorted world map).
* Aspect Ratio: Always 2:1 (e.g., 4000x2000 pixels).
* File Format: `.jpg` or `.png` is standard.


# Document

Document listings allow users to upload and share documents, as well as create Journal listings which are a document listing subcategory.

## New Hub Listing

### Create

To start the creation process:

* Go to the "My Listings" page.
* **Click** the "Document" icon to begin creating a new image listing.

<figure><img src="/files/0eHkV9bjtXBPR8LaK0BJ" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/15zWWrqrTGfUVel9KNkI" alt="" width="563"><figcaption></figcaption></figure>

### Listing Type Modal

{% hint style="info" %}
This page will be reviewing the creation flow of a New Hub Listing. These links can be used to learn more about how to create a [New Version](/motar-core-services/intro-to-core-services/studio/digital-thread/new-version) or [Remix](/motar-core-services/intro-to-core-services/studio/digital-thread/remix).
{% endhint %}

Clicking on the Document icon on the My Listings page will show this flow to the user. The Listing Type modal will open allowing the user to **Select** whether this will be a new listing, new version of existing listing, or remix of someone else’s listing. **Select** the "New Hub Listing" option and **Click** the "Next" button.

<figure><img src="/files/5h98UfgGwMxVFzYOnaIg" alt=""><figcaption></figcaption></figure>

### Upload

After a New Hub Listing type is chosen, the user will be brought to the "Upload" tab and is required to upload a supported file type.

<figure><img src="/files/5yc7tnbyhn3TEPQaGZEZ" alt=""><figcaption></figcaption></figure>

#### Supported Files Types:

* **WORD**: *.doc .docm .docx .dot .dotx .rtf .txt*
* **EXCEL**: *.xls .xlsm .xlsx .csv*
* **POWERPOINT**: *.ppt .pptm .pptx*
* **ACROBAT PDF**: *.pdf*

After selecting the "Upload" button, the File Upload and Scanning Tool will launch (see link below for additional instructions, if needed). &#x20;

After the secure scanning is complete, **Click** the "Close" on the file upload modal.

{% content-ref url="/pages/lbE42dn6cJmSUnh4APkS" %}
[Secure File Upload & Scanning](/motar-core-services/intro-to-core-services/studio/secure-file-upload-and-scanning)
{% endcontent-ref %}

### Info

{% hint style="info" %}
The Listing Name for the listing will be auto-populated to match the name of the file that was uploaded on the "Upload" tab but can be edited at this time to a preferred listing name.
{% endhint %}

On the "Info" tab, users are required to fill in a Listing Name and Listing Description.

{% hint style="info" %}
Progress on a listing can be saved once the user has uploaded a file, named the listing, and filled out a listing description. This allows the user to fill out all additional fields for their listing at a later time. It is important to note that a listing **cannot** be promoted from Sandbox to Production until all of a listing’s required fields have been filled out.
{% endhint %}

<figure><img src="/files/CI4TutLNElyPT1algrGU" alt=""><figcaption></figcaption></figure>

### Permissions

On the "Permissions" Tab, **Click** the "Launch" button to run the Permissions Wizard. Full instructions can be found at the link below.

{% content-ref url="/pages/w1QhZr1b8TwwfUsIBSmd" %}
[Listing Permissions](/motar-core-services/intro-to-core-services/studio/listing-permissions)
{% endcontent-ref %}

Once permissions have been set, **Click** the "Save" button to save all requested changes and allow the user to set the Hub Visibility of the listing.

{% hint style="info" %}
The Hub Visibility toggle is located on the top right of a listing's edit page after initial permissions are set. The default is **OFF** for public visibility on Sandbox listings. The default is **ON** for public visibility on Production listings.
{% endhint %}

<figure><img src="/files/9SE831qVAP8qKvQNgvfA" alt=""><figcaption></figcaption></figure>

### Digital Thread

* The current version of the listing
* Any future versions or remixes created from it

The "Digital Thread" tab provides a centralized view of a listing’s **entire digital lifecycle.**\
It captures and displays:

When creating a new listing, this tab will initially show only that listing.\
As you or others create new versions or remixes, those will be added to this view automatically.

You can return to the "Digital Thread" tab at any time by choosing to **Edit** the listing from the "My Listings" page.

{% hint style="info" %}
From the Digital Thread tab, users can **set a listing as Authoritative or Certified**—but only **after it has been promoted to Production**.

For more guidance on how to authorize or certify a listing, click [here](/motar-core-services/intro-to-core-services/studio/digital-thread/authoritative-and-certified-listings).
{% endhint %}

<figure><img src="/files/qOBM7QSoUCa5QJ9CToPt" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
See the following links for more information on [Digital Thread](/motar-core-services/intro-to-core-services/studio/digital-thread) and the [Digital Thread Iconology](/motar-core-services/intro-to-core-services/studio/digital-thread/iconology).
{% endhint %}

### Publish

Once all required information for a listing is complete and the listing has been **Saved**, the "Publish" button becomes available.

Publishing a listing moves it from **Sandbox** to **Production**, making it officially available for wider access.

{% hint style="danger" %}
After publishing, users will **no longer be able to change files** on the **UPLOAD** tab.\
However, you **can still update**:

* Description on the **INFO** tab
* Listing **permissions**
  {% endhint %}

To publish:

* **Click** the "Publish" button.

<figure><img src="/files/ksoAh4RYVXe4u72iNmty" alt=""><figcaption></figcaption></figure>

* The "Permissions for Production" modal will open.
* Choose between:
  * Keep Current permissions
  * Set New permissions
* For this example, **select** "Keep Current" and then **click** "Next".

<figure><img src="/files/pqrD2JNtaxbGZC2IiP6U" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
Choosing **SET NEW** permissions will **overwrite the existing permissions** for the listing.

Need help setting new permissions?

Full instructions on how to run the Permissions Wizard can be found at the link below.
{% endhint %}

The modal will close and the listing will be updated from Sandbox to Production.

<figure><img src="/files/fUIPweKB8b2HEX0LL1JY" alt=""><figcaption></figcaption></figure>

***

## Edit

To edit a listing, **Click** the " ✏️ " icon in the *Action* column in the "My Listings" table. The table can be accessed from the MOTAR Studio My Listings page.

<figure><img src="/files/wLfdt4oTRId22jk17H1p" alt=""><figcaption></figcaption></figure>

Make any desired changes in the Upload, Info, Permissions, and/or Digital Thread tabs. The user can navigate between tabs by either **Clicking** the tab title or **Clicking** the "Next" button.

{% hint style="info" %}
If the user desires to update permissions settings, **CLICK** the **MODIFY** button in the **PERMISSIONS** tab to run the Permissions Wizard. Full instructions can be found at the link below.
{% endhint %}

{% content-ref url="/pages/w1QhZr1b8TwwfUsIBSmd" %}
[Listing Permissions](/motar-core-services/intro-to-core-services/studio/listing-permissions)
{% endcontent-ref %}

Once desired edits have been made, **Click** the "Save" button to save all requested changes and update the Document Listing.

***

## Delete

To delete a listing:

* Go to "My Listings"
* Click the " ✏️ " icon
* Go to the "Digital Thread" tab
* **Click** the " 🗑️ " icon in the "*Action*" column

<figure><img src="/files/AsQ4wXUkjaNRKzWPb96P" alt=""><figcaption></figcaption></figure>

* Type `DELETE` in the confirmation text field.
* This activates the "Delete" button. Click it.

<figure><img src="/files/CdqF3s4cwPjmUiQn7ZGl" alt=""><figcaption></figcaption></figure>

You’ll be returned to the "Digital Thread" tab.\
The listing will now appear as **archived** in:

* The Digital Thread
* The My listings page

<figure><img src="/files/IglxOIfJSLJVaebDRR26" alt=""><figcaption></figcaption></figure>


# Patch

The Patch listing type is a new asset category in MOTAR Studio designed for software distribution files — things like installers, updates, packages, and archives.

***

**Creating a Patch Listing**

To create a Patch listing, open Studio and select **Patch** as your listing type. The creation flow mirrors the Document listing type with a few key differences.

**Supported file types:** iso, zip, msi, dmg, pkg, tar, exe, gz, csv, xml

<figure><img src="/files/L7h1lQUhvgJtmHIBHNd8" alt=""><figcaption></figcaption></figure>

***

**Tabs & Fields**

**Info Tab**&#x20;

Fill in your listing details here. Note that the Info tab does not support preview images or video uploads for Patch listings.

**Settings Tab**&#x20;

The Settings tab includes a **Platform Types** field where you can specify the target platform(s) for the patch.

**Permissions Tab** Works the same as other listing types. Set access controls as needed.

**Digital Thread Tab** Available and functions identically to Document listings.

**Badges Tab** Not available for Patch listings.

***

**Hub Discovery**

Patch listings appear on the Hub with a default icon when no thumbnail has been uploaded. A **Patch** filter option has been added to the main Hub filter panel, allowing users to browse and search specifically for Patch assets alongside other listing types.

***

**Tags**

Like all listing types, Patch assets support tagging. Tags are managed in the **Info tab** and can be used to filter results in Hub or queried through the MOTAR AI assistant.


# Listing Permissions

A guide to set listing permissions on assets.

As a creator, you control how other users access your listings by running the Permission Wizard listed on the permission settings. Here, you can set who can "Discover, Download, Use, Distribute, and Modify" your uploaded content.

<figure><img src="/files/Ycqr3vLjEGoVIuUfuDlQ" alt=""><figcaption></figcaption></figure>

## Permissions

### Discover

Discover permission allow you to view the listing cards on the Hub.

{% hint style="warning" %}
If you do not see a hub card listed on the Hub discover page, it is most likely because you do not have discover permission to that listing.
{% endhint %}

### Download

Download permissions allows you to download a listing.

### Use

Use permission gives rights to 'use, display, and include' the listing.

### Distribute

Distribute permission allows you to 'use, display and include' the listing in other published listings in MOTAR, created by the downloader account.

### Modify

Modify permissions allows rights to make derivatives, modifications, and alterations on this listing and furthermore 'use, display, and include' this altered version in other listings published in MOTAR. The original creators account must be credited in the listing page.

### Group Definitions

**Public**: All users with an account on the platform\
**Owning** **Company**: All members of the Owning Company\
**Partners**: All users associated with a Partner Company\
**Custom**: Specify groups like a Department, Partner Company, or Studio Group

## Manage Permissions&#x20;

Set permissions by clicking the ![](https://studio.test.dynepic.net/dxp/assets/images/plus-circle.svg) symbols for the groups in the table below.

Permissions are cumulative as you go down the table. (e.g.) **Selecting** “Download” for a group will subsequently also check “Discover”. Permissions can be modified from Studio once they’ve been set.

<figure><img src="/files/4LvheWc0dl6930osgg0W" alt=""><figcaption></figcaption></figure>


# State Manager

A guide for understanding the Studio listing State Manager

The MOTAR State Manager keeps track of what stage of Sandbox or Production an asset is in during the creation process.

## State Manager

The MOTAR State Manager denotes what status the a listing is currently in for each step of the creation process. All listings will start in Sandbox status until requirements have been met allowing the user to promote it to Production status.

{% hint style="info" %}
Requirements for publishing can be found at the following links: [Listing Publishing](/motar-core-services/intro-to-core-services/studio/manage-each-listing-type)&#x20;
{% endhint %}

## State Manager Overview

All courses and listings will start in Sandbox status until requirements have been met allowing the user to promote the course or listing to Production status. The charts below break down each state in the flow for asset creation and how the user can progress to the next state.

### State Manager - Non-App Listings&#x20;

<table><thead><tr><th width="326" align="center">State Indicator</th><th>Description</th></tr></thead><tbody><tr><td align="center"><img src="/files/8esFAKWopygc2XUsxoNk" alt="" data-size="original"></td><td><p><strong>Sandbox - Create Listing</strong></p><p>When a new listing is created and has not been saved yet. If the user exits the listing creation before moving past this state the listing will not appear on the user's studio listings.</p></td></tr><tr><td align="center"><img src="/files/3vmbCKqNOgIXbZMycWXM" alt="" data-size="original"></td><td><p><strong>Sandbox - Incomplete Listing</strong></p><p>All required fields on the Info tab have been entered, and data has been saved, but not all the required information in all required tabs has been entered. The listing will appear on the user's studio listing page.</p></td></tr><tr><td align="center"><img src="/files/9V6JSI6dE4CJAQoh2o6t" alt="" data-size="original"></td><td><p><strong>Sandbox - Ready to Publish on MOTAR</strong></p><p>All required fields in all required tabs have been completed and the listing has been saved. The listing is ready to be viewed on Hub, tested using a Sandbox Course, or to be published to Production.</p></td></tr><tr><td align="center"><img src="/files/GSN1BQOmzMCWlJePkLwA" alt="" data-size="original"></td><td><p><strong>Production - Published</strong></p><p>When a user has promoted a listing by selecting the publish button and has chosen to either Keep Permissions or Set New Permissions. The listing is promoted to Production. </p></td></tr></tbody></table>

### State Manager - App Listings

<table><thead><tr><th width="326" align="center">State Indicator</th><th>Description</th></tr></thead><tbody><tr><td align="center"><img src="/files/e2MkWf75KUNyPOUGYwGB" alt="" data-size="original"></td><td><p><strong>Sandbox - Create Listing</strong></p><p>When a new app listing is created and has not been saved yet. If the user exits the app creation before moving past this state the app will not appear on the user's studio listings.</p></td></tr><tr><td align="center"><img src="/files/CuWtaa088jUFmO9oFvwN" alt="" data-size="original"></td><td><p><strong>Sandbox - Local Test Only</strong></p><p>All required fields on the Info tab have been entered, and data has been saved, but not all the required information in all required tabs has been entered. The app will appear on the user's studio listing page.</p></td></tr><tr><td align="center"><img src="/files/PQI71uYf1epGFWjs2Xt2" alt="" data-size="original"></td><td><p><strong>Sandbox - Under Review for Production</strong></p><p>After a user submits the app for review, the state manager updates to under review. The user will be unable to make any changes to the app during this time.</p></td></tr><tr><td align="center"><img src="/files/D01LqVvBwC2d3FSpa2WS" alt="" data-size="original"></td><td><p><strong>Sandbox - Ready to Publish to Production</strong></p><p>All required fields in all tabs have been completed, the app has been approved, and the app has been saved. The app is ready to be viewed on Hub, tested using a Sandbox Course, or to be published to Production.</p></td></tr><tr><td align="center"><img src="/files/m31cDteCKijgbyCYBR9D" alt="" data-size="original"></td><td><p><strong>Production - Published</strong></p><p>When a user has promoted an app by selecting the publish button and has chosen to either Keep Permissions or Set New Permissions. The app is promoted to Production. </p></td></tr><tr><td align="center"><img src="/files/LkrmgVAaaeXVuNcK0Awu" alt="" data-size="original"></td><td><p><strong>Production - Listing Edits Under Review</strong></p><p>When a user has a Production App and wishes to make changes to it, they must resubmit it for review. The previously approved version of the application is still available on Hub during this Production Review. </p></td></tr></tbody></table>


# Digital Thread

## Overview

Users will be able to organize each asset listing as a parent or child version and contribute assets across organizations where they have proper permissions. Additionally, users can remix assets they have “Modify” permissions on. This allows users to easily track version control and choose the correct version.

Some key features of an asset’s “Digital Thread” include:&#x20;

<figure><img src="/files/HIj8HBRhHvV7NxwPLOEe" alt=""><figcaption></figcaption></figure>

### Version Control

Version control involves assigning unique versions to each iteration of a listing within a digital thread. The versioning can then be used to show a history of changes to an original listing which can include new versions and remixes created collaboratively by other users that have the access to do so.

<figure><img src="/files/ZmHZQae7FqEAR8UyHRBX" alt=""><figcaption></figcaption></figure>

### Version Tree

Version Tree shows the entire digital thread for a listing including the hierarchy of all new versions and remixes that have been made in relation to the listing. The Version Tree can be found in Studio by **selecting** the dropdown next to a listing to view more information or in Hub on the Hub Listing Page for a listing.

<div data-full-width="true"><figure><img src="/files/bcBPIB31sxlwcjcpXfSR" alt=""><figcaption></figcaption></figure></div>

### Remix

Remixes consist of listings that are made up of assets combined to create an entirely new asset. The user will need to pick an original version of a listing to make a remix of, then they will have the ability to select all attributing listings to include in the new remix. Remixes can be made of existing listings owned by the user and their Studio Org(s) or listings owned by other users, as long as the user has permission to access them.&#x20;

<figure><img src="/files/5NnagBUD4u3T0E1a5lD2" alt=""><figcaption></figcaption></figure>

### Ownership and Permissions

Users can assign Authoritative and Certified classifications to the listings that they or their Studio Org(s) own. Only one listing in a listing's version tree can be marked as Authoritative at a time. This signifies to other users that a version of a listing has been defined as the "source of truth" for that entire tree by the Studio Admin. Multiple listings in a digital thread can be marked as Certified, this signifies to other users that the listings are certified for training content.&#x20;

<figure><img src="/files/4pAHI1BY59v15RGixQ4C" alt=""><figcaption></figcaption></figure>

### Digital Twin

*Coming soon!*

***

## Digital Thread Features

<table data-card-size="large" data-view="cards" data-full-width="false"><thead><tr><th data-type="content-ref"></th><th></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td><a href="/pages/H4YE9NDlKceeXVRBToPi">/pages/H4YE9NDlKceeXVRBToPi</a></td><td>Explanation of the Digital Thread icon legend found in Hub and Studio.</td><td></td></tr><tr><td><a href="/pages/Liz8gObZA2izs9kZJcf1">/pages/Liz8gObZA2izs9kZJcf1</a></td><td>New Versions can be made of existing listings owned by the user or their Studio Org.</td><td></td></tr><tr><td><a href="/pages/DPfCDO0Hecfz2190sl91">/pages/DPfCDO0Hecfz2190sl91</a></td><td>Remixes can be made of existing listings owned by the user and their Studio Org or listings owned by other users as long as the user has the permissions to access them.</td><td></td></tr><tr><td><a href="/pages/gn3P6TypGKTzLkDtlvqM">/pages/gn3P6TypGKTzLkDtlvqM</a></td><td>Users can assign Authoritative and Certified classifications to the listings that they or their Studio Org(s) own.</td><td></td></tr></tbody></table>


# Iconology

## How to Access the Icon Legend

{% hint style="info" %}
The Icon Legend can be accessed from the Info icon above the Version Tree in Hub or in Studio or above the Listing Name on the Digital Thread tab when editing a listing.
{% endhint %}

**Click** the "Info" icon then **Click** on the "Icon Legend" link. This will open the Icon Legend modal. From here the user will be able to **Click** the "Documentation" link to be directed to a more detailed description of the Digital Thread icons in the MOTAR Public Documents.

<figure><img src="/files/U2NCPMIcdBzABrY40aPo" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
The icon legend pop-up can be moved around and stay on the screen until closed.
{% endhint %}

The user can close the Icon Legend modal by **Clicking** the "X" button located at the top right of the modal.

Icon Types

<table><thead><tr><th width="107" align="center">Icon</th><th>Description</th><th data-hidden></th></tr></thead><tbody><tr><td align="center"><img src="/files/YkXXmahFD2KQwtOm7i6P" alt="" data-size="original"></td><td><p><strong>Authorized -</strong></p><p>A listing that has been marked as the Authoritative Version.</p></td><td></td></tr><tr><td align="center"><img src="/files/Y3TniOcsgyBxbpPhCTZ3" alt="" data-size="original"></td><td><p><strong>Certified -</strong></p><p>A listing that has been marked as Certified to be used as a part of training content.</p></td><td></td></tr><tr><td align="center"><img src="/files/DWEsg99cZlbmZVSuxjn8" alt="" data-size="original"></td><td><p><strong>Not Certified -</strong></p><p>A listing that has not yet been marked as Certified to be used as a part of training content.</p></td><td></td></tr><tr><td align="center"><img src="/files/9n247ChYh5THT0dD55zp" alt="" data-size="original"></td><td><p><strong>Remix -</strong> </p><p>A listing that is made up of assets from different parts of the Version Tree, combined to create an entirely new asset. </p></td><td></td></tr><tr><td align="center"><img src="/files/i090iTD3qlgTK9IfGae3" alt="" data-size="original"></td><td><strong>My Org Listing -</strong> <br>A listing that was created in the Studio Org(s) the user belongs to.</td><td></td></tr></tbody></table>

### Status Types

<table><thead><tr><th width="100" align="center">Icon</th><th>Description</th><th data-hidden></th></tr></thead><tbody><tr><td align="center"><div><figure><img src="/files/HKksmT4n2xjoAop07dKU" alt=""><figcaption></figcaption></figure></div></td><td><strong>Production -</strong> <br>A listing that has been promoted from Sandbox mode to Production.</td><td></td></tr><tr><td align="center"><div><figure><img src="/files/yxkieIJayNSfvPfiinqW" alt=""><figcaption></figcaption></figure></div></td><td><strong>Sandbox -</strong><br>A listing that exists only in Sandbox mode. </td><td></td></tr><tr><td align="center"><div><figure><img src="/files/loGDbDUscvB1Wj9pcG0i" alt=""><figcaption></figcaption></figure></div></td><td><strong>Archived -</strong><br>A listing that has been archived.</td><td></td></tr><tr><td align="center"><div><figure><img src="/files/RZmt9j2k3wo15NRs0p2v" alt=""><figcaption></figcaption></figure></div></td><td><strong>Locked -</strong><br>The current user does not have permissions to view the listing.</td><td></td></tr><tr><td align="center"><div><figure><img src="/files/HJxcJVDn2C52GjrYdKT9" alt=""><figcaption></figcaption></figure></div></td><td><em><strong>Moderation -</strong></em><br><em>A listing that is under moderation. (coming soon)</em></td><td></td></tr></tbody></table>


# New Version

{% hint style="danger" %}
All listings will be in Sandbox until they have been promoted and approved for Production.
{% endhint %}

{% hint style="info" %}
Each listing type has required fields that must be completed before the listing can be either saved or promoted to Production. If any required fields are left blank a red i icon will be marked on the corresponding tab to remind the user what still needs to be filled out.
{% endhint %}

## New Version of Hub Listing

### Create

{% hint style="info" %}
For the following steps on how to make a New Version of a listing, the Document listing type will be used. The steps are the same for all listing types though there may be additional required tabs to fill out depending on the listing type.
{% endhint %}

**Click** on the "Document" icon to begin the create listing process.

<figure><img src="/files/wPK4AJxdtgOSWYCnmBDb" alt=""><figcaption></figcaption></figure>

### Listing Type Modal

{% hint style="info" %}
This page will be reviewing the creation flow of a New Version. These links can be used to learn more about how to create a [New Hub Listing](/motar-core-services/intro-to-core-services/studio/manage-each-listing-type) or [Remix](/motar-core-services/intro-to-core-services/studio/digital-thread/remix).
{% endhint %}

**Clicking** on the Document icon on the My Listings page will show this flow to the user. The "Listing Type" modal will open allowing the user to **Select** whether this will be a new listing, new version of existing listing, or remix of someone else’s listing. **Select** the "Add a new version to my own listing" option and **Click** the "Next" button.

<figure><img src="/files/X7lH4Q0kyiRD0WQY3K1b" alt="" width="375"><figcaption></figcaption></figure>

On the next page of the modal users will be able to select either a remix version or standard version of the listing to add. **Select** the "Add a Standard Version" option and **Click** the "Next" button

{% hint style="info" %}
More information on remixing a listing can be found [here](/motar-core-services/intro-to-core-services/studio/digital-thread/remix).
{% endhint %}

<figure><img src="/files/4pnONaN3d9kMC4FDHbEf" alt="" width="375"><figcaption></figcaption></figure>

### Select Listing Modal

All Document listings created by either the user or the Studio Organization they belong to will display. The user will be able to choose a listing to make a New Version of from the documents that they have access to being displayed on this modal. **Select** one of the listings and **Click** the "Next" button.

<figure><img src="/files/EAwAVcrguKgQexa3yYNb" alt=""><figcaption></figcaption></figure>

### Version Tree Modal

The current Version Tree for the original listing will display. The user will be able to choose whether to make their New Version a new Child or Parent Version of the original listing.

<figure><img src="/files/NekAXzK3h7vB8hP6tjj3" alt="" width="375"><figcaption></figcaption></figure>

Once one of the options is chosen the user will be able to "Input" a name for the New Version. **Click** the "Next" button.

<figure><img src="/files/kAGO1NJAvN4bFbpFxxt3" alt="" width="375"><figcaption></figcaption></figure>

### Upload

After all the New Version modals are completed, the user will be brought to the Create Document Listing page. The user will be on the "Upload" tab and is required to upload a supported file type.

<figure><img src="/files/aMyR5dlKuvQ7dPfn6Vn2" alt=""><figcaption></figcaption></figure>

### Info

On the "Info" tab, users are required to fill in a *Version Name* and *Version Description*.

{% hint style="info" %}
Progress on a listing can be saved once the user has uploaded a file, named the listing and filled out a listing description. This allows the user to fill out all additional fields for their listing at a later time. It is important to note that a listing cannot be promoted from Sandbox to Production until all of a listing’s required fields have been filled out.
{% endhint %}

<figure><img src="/files/OZoJu3JkSYuFB37OewZx" alt=""><figcaption></figcaption></figure>

### Permissions

On the "Permissions" Tab, **Click** the "Launch" button to run the Permissions Wizard. Full instructions can be found at the link below.

{% content-ref url="/pages/w1QhZr1b8TwwfUsIBSmd" %}
[Listing Permissions](/motar-core-services/intro-to-core-services/studio/listing-permissions)
{% endcontent-ref %}

<figure><img src="/files/mhE5wrUSlf8e4tB7AYtJ" alt=""><figcaption></figcaption></figure>

### Digital Thread

The "Digital Thread" tab will display all current information for a listings digital thread. The digital thread for a New Version should display the original listing and then the new version of the listing beneath it in the tree. If additional versions or remixes of the listing are made they will display too and the tab can be accessed again if the user chooses to **Edit** the listing.

{% hint style="info" %}
The user will be able to set Authorized or Certified on listings in the tree from this tab. Only if the listing has been promoted to Production. More information on how to authorize or certify a listing can be found [here](/motar-core-services/intro-to-core-services/studio/digital-thread/authoritative-and-certified-listings).
{% endhint %}

<figure><img src="/files/1G7QnunFcLpLdPE16gYP" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
See the following links for more information on [Digital Thread](/motar-core-services/intro-to-core-services/studio/digital-thread) and the [Digital Thread Iconology](/motar-core-services/intro-to-core-services/studio/digital-thread/iconology).
{% endhint %}

### Publish

Once all the required information has been completed for a listing and the listing has been saved, the Publish button will become available to the user. Users will be able to "Publish" their listing which will promote the listing from the Sandbox to Production.

{% hint style="danger" %}
Once a listing is published, the user will be unable to change the files on the "Upload" tab but will still be able to update information on the "Info" tab and modify permissions.
{% endhint %}

**Click** on the "Publish" button.

<figure><img src="/files/kB0jnuFOUpSefx16E2MC" alt=""><figcaption></figcaption></figure>

This will open the "Permissions for Production" modal. From here the user will be able to choose to keep current or set new permissions. For the purposes of this example, **Select** the "Keep Current" option and **Click** the "Next" button.

{% hint style="info" %}
Setting new permissions will overwrite the existing permissions for the listing. Full instructions on how to run the Permissions Wizard can be found at the link below.
{% endhint %}

{% content-ref url="/pages/w1QhZr1b8TwwfUsIBSmd" %}
[Listing Permissions](/motar-core-services/intro-to-core-services/studio/listing-permissions)
{% endcontent-ref %}

<figure><img src="/files/Giw1TOUXu1aHjkHUi2CQ" alt=""><figcaption></figcaption></figure>

The modal will close and the listing will be updated from Sandbox to Production.

<figure><img src="/files/01plL7VdA14IBAjUrZN1" alt=""><figcaption></figcaption></figure>

***

## Edit

To edit a listing, **Click** the " ✏️ " icon in the *"Action"* column in the My Listings table. The table can be accessed from the MOTAR Studio My Listings page.

<figure><img src="/files/mLGdjiJsfg8igNrmQJlZ" alt=""><figcaption></figcaption></figure>

Make any desired changes in the Upload, Info, Permissions, and/or Digital Thread tabs. The user can navigate between tabs by either **Clicking** the tab title or **clicking** the "Next" button.

If the user desires to update permissions settings, **Click** the "Modify" button in the "Permissions" tab to run the Permissions Wizard. Full instructions can be found at the link below.

{% content-ref url="/pages/w1QhZr1b8TwwfUsIBSmd" %}
[Listing Permissions](/motar-core-services/intro-to-core-services/studio/listing-permissions)
{% endcontent-ref %}

Once desired edits have been made, **Click** the "Save" button to save all requested changes and update the Document Listing.

***

## Delete

To delete a listing, **Click** the " ✏️ " icon in the *"Action"* column in the My Listings table. Navigate to the "Digital Thread" tab, **Click** the " 🗑️ " can icon in the *"Action"* column of the "Digital Thread" tab. A Delete Listing modal will be displayed.

<figure><img src="/files/mHltZulJNjn2t8S2aOry" alt=""><figcaption></figcaption></figure>

To confirm deletion of the listing, **Type** the word *"Delete"* in the text field. This will activate the "delete" button which can then be **Clicked**.

<figure><img src="/files/jiq5IVwgjin3wAUuuxza" alt="" width="563"><figcaption></figcaption></figure>

The user will be returned to the **"**&#x44;igital Thread" tab. The listing that has been selected for deletion and will display as archived in the "Digital Thread" tab and also on the "My Listings" page.

<figure><img src="/files/SojMbIi10Pqf7I9Bc8kP" alt=""><figcaption></figcaption></figure>


# Remix

{% hint style="danger" %}
All listings will be in Sandbox until they have been promoted and approved for Production.
{% endhint %}

{% hint style="info" %}
Each listing type has required fields that must be completed before the listing can be either saved or promoted to Production. If any required fields are left blank a red i icon will be marked on the corresponding tab to remind the user what still needs to be filled out.
{% endhint %}

## Remix of Hub Listing

### Create

{% hint style="info" %}
For the following steps on how to make a Remix of a listing, the Document listing type will be used. The steps are the same for all listing types though there may be additional required tabs to fill out depending on the listing type.
{% endhint %}

**CLICK** on the **DOCUMENT** icon to begin the create listing process.

<figure><img src="/files/OUyACROrMRRjAlhZ7EqJ" alt=""><figcaption></figcaption></figure>

### Listing Type Modal

{% hint style="info" %}
This page will be reviewing the creation flow of a New Version. These links can be used to learn more about how to create a [New Hub Listing](/motar-core-services/intro-to-core-services/studio/digital-thread/new-version#new-version-of-hub-listing) or [New Version](/motar-core-services/intro-to-core-services/studio/digital-thread/new-version).
{% endhint %}

Clicking on the Document icon on the My Listings page will show this flow to the user. The **LISTING TYPE** modal will open allowing the user to **SELECT** whether this will be a new listing, new version of existing listing, or remix of someone else’s listing. **SELECT** the **ADD A REMIX TO SOMEONE ELSE’S LISTING** option and **CLICK** the **NEXT** button.

<figure><img src="/files/u8AqWcEywQKZ3ftfcBGD" alt="" width="375"><figcaption></figcaption></figure>

### Select Listing Modal

All Document listings created by other users that have been downloaded will display. The user will be able to choose a listing to make a Remix of from the documents that they have access to being displayed on this modal. **SELECT** one of the listings and **CLICK** the **NEXT** button.

<figure><img src="/files/lepBdmAofIV1mJsNY90M" alt=""><figcaption></figcaption></figure>

### Version Tree Modal

The current Version Tree for the original listing will display. The user will be able to choose whether to make their Remix either a new Child or Parent Version of the original listing.

<figure><img src="/files/8OUqXH2TBRHFZwnXO4dc" alt="" width="375"><figcaption></figcaption></figure>

Once one of the options is chosen the user will be able to **INPUT** a name for the Remix. **CLICK** the **NEXT** button.

<figure><img src="/files/pT6PTK6vsHKYabLM7glM" alt="" width="375"><figcaption></figcaption></figure>

### Upload

After all the Remix modals are completed, the user will be brought to the Create Document Listing page. The user will be on the **UPLOAD** tab and is required to upload a supported file type.

<figure><img src="/files/tDns8lIYHdDvvL6EPmg6" alt=""><figcaption></figcaption></figure>

### Info

On the **INFO** tab, users are required to fill in a **VERSION NAME** and **VERSION DESCRIPTION**.

{% hint style="info" %}
Progress on a listing can be saved once the user has uploaded a file, named the listing and filled out a listing description. This allows the user to fill out all additional fields for their listing at a later time. It is important to note that a listing **cannot** be promoted from Sandbox to Production until all of a listing’s required fields have been filled out.
{% endhint %}

<figure><img src="/files/e90su2pf6oFCVcdUfEgC" alt=""><figcaption></figcaption></figure>

### Permissions

On the **PERMISSIONS** Tab, **CLICK** the **LAUNCH** button to run the Permissions Wizard. Full instructions can be found at the link below.

{% content-ref url="/pages/w1QhZr1b8TwwfUsIBSmd" %}
[Listing Permissions](/motar-core-services/intro-to-core-services/studio/listing-permissions)
{% endcontent-ref %}

<figure><img src="/files/z3NLMO4TcIo8oLIvCEBF" alt=""><figcaption></figcaption></figure>

### Digital Thread

The **DIGITAL THREAD** tab will display all current information for a listings digital thread. The digital thread for a Remix should display the original listing and then the remix of the listing beneath it in the tree. If additional versions or remixes of the listing are made they will display too and the tab can be accessed again if the user chooses to **EDIT** the listing.

{% hint style="info" %}
The user will be able to set Authoritative or Certified on listings in the tree from this tab. Only if the listing has been promoted to Production. More information on how to authorize or certify a listing can be found [here](/motar-core-services/intro-to-core-services/studio/digital-thread/authoritative-and-certified-listings).
{% endhint %}

<figure><img src="/files/Y30qHh66JECrXEdzFqfp" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
See the following links for more information on [Digital Thread](/motar-core-services/intro-to-core-services/studio/digital-thread) and the [Digital Thread Iconology](/motar-core-services/intro-to-core-services/studio/digital-thread/iconology).
{% endhint %}

### Assets Used

The **ASSETS USED** tab will display all the published listings the current user has permissions to access and modify from their Studio Org and any listing that they have downloaded. Next to each listing is a checkbox that the user can **SELECT** to signify that the selected listing was used as part of the remixed listing being created.

<figure><img src="/files/LboSNUmEyxqGeOnCa4sw" alt=""><figcaption></figcaption></figure>

### Publish

Once all the required information has been completed for a listing and the listing has been saved, the Publish button will become available to the user. Users will be able to **PUBLISH** their listing which will promote the listing from the Sandbox to Production.

{% hint style="danger" %}
Once a listing is published, the user will be unable to change the files on the **UPLOAD** tab but will still be able to update information on the **INFO** tab and modify permissions.
{% endhint %}

**CLICK** on the **PUBLISH** button.

<figure><img src="/files/YV0GHQz88mZEz0tw3XDA" alt=""><figcaption></figcaption></figure>

This will open the **PERMISSIONS FOR PRODUCTION** modal. From here the user will be able to choose to **KEEP CURRENT** or **SET NEW PERMISSIONS**. For the purposes of this example, **SELECT** the **KEEP CURRENT** option and **CLICK** the **NEXT** button.

{% hint style="info" %}
Setting new permissions will overwrite the existing permissions for the listing. Full instructions on how to run the Permissions Wizard can be found at the link below.
{% endhint %}

{% content-ref url="/pages/w1QhZr1b8TwwfUsIBSmd" %}
[Listing Permissions](/motar-core-services/intro-to-core-services/studio/listing-permissions)
{% endcontent-ref %}

<figure><img src="/files/NsmWHDVb6QMhxxy3zDli" alt=""><figcaption></figcaption></figure>

The modal will close and the listing will be updated from Sandbox to Production.

<figure><img src="/files/0ItuMFFowIkupYFHxXTk" alt=""><figcaption></figcaption></figure>

***

## Edit

To edit a listing, **CLICK** the **PENCIL** icon in the **ACTION** column in the **MY LISTINGS** table. The table can be accessed from the MOTAR Studio **MY LISTINGS** page.

<figure><img src="/files/Typ27R4jZf7U0BWuh88s" alt=""><figcaption></figcaption></figure>

Make any desired changes in the **UPLOAD, INFO, PERMISSIONS**, and/or **DIGITAL THREAD** tabs. The user can navigate between tabs by either **CLICKING** the **TAB TITLE** or **CLICKING** the **NEXT** button.

If the user desires to update permissions settings, **CLICK** the **MODIFY** button in the **PERMISSIONS** tab to run the Permissions Wizard. Full instructions can be found at the link below.

{% content-ref url="/pages/w1QhZr1b8TwwfUsIBSmd" %}
[Listing Permissions](/motar-core-services/intro-to-core-services/studio/listing-permissions)
{% endcontent-ref %}

Once desired edits have been made, **CLICK** the **SAVE** button to save all requested changes and update the Document Listing.

***

## Delete

To delete a listing, **CLICK** the **PENCIL** icon in the **ACTION** column in the **MY LISTINGS** table. Navigate to the **DIGITAL THREAD** tab, **CLICK** the **TRASH CAN** icon in the **ACTION** column of the **DIGITAL THREAD** tab. A Delete Listing modal will be displayed.

<figure><img src="/files/fxeARYkEwdsRRiQITZsb" alt=""><figcaption></figcaption></figure>

To confirm deletion of the listing, **TYPE** the word **DELETE** in the text field. This will activate the **DELETE** button which can then be **CLICKED**.

<figure><img src="/files/SN6qjK2mc6WtkPkMJcOL" alt="" width="563"><figcaption></figcaption></figure>

The user will be returned to the **DIGITAL THREAD** tab. The listing that has been selected for deletion and will display as archived in the **DIGITAL THREAD** tab and also on the **MY LISTINGS** page.

<figure><img src="/files/rG572uLNtxVAiFaomlaT" alt=""><figcaption></figcaption></figure>


# Authoritative and Certified Listings

Users can assign Authoritative and Certified classifications to the listings that they or their Studio Org(s) own.

## Authoritative Listing

{% hint style="info" %}
Users will first need to promote their listing from Sandbox to Production for the Authoritative Listing Toggle to be accessible. For more information on Publishing a listing see the corresponding links here: [Apps](/motar-core-services/intro-to-core-services/studio/manage-each-listing-type/app), [Audio](/motar-core-services/intro-to-core-services/studio/manage-each-listing-type/audio), [Document](/motar-core-services/intro-to-core-services/studio/manage-each-listing-type/document), [3D Model](/motar-core-services/intro-to-core-services/studio/manage-each-listing-type/model), [Image](/motar-core-services/intro-to-core-services/studio/manage-each-listing-type/image), or [Video](/motar-core-services/intro-to-core-services/studio/manage-each-listing-type/video).
{% endhint %}

The Authoritative Listing Toggle can be found on the Digital Thread tab of Production Listings.&#x20;

<figure><img src="/files/LTqwPCWfWm1Py2kup5Vk" alt=""><figcaption></figcaption></figure>

**CLICK** the **AUTHORITATIVE LISTING** to set it **ON**. This will update the listing to Authoritative and change the icons on the Digital Thread to match. This signifies to other users that this version of a listing has been defined as the "source of truth" for that entire tree by a Studio Admin.

<figure><img src="/files/dm5a0VWMrrACqN4QM9zv" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
Only one listing in a listing's version tree can be marked as Authoritative at a time.&#x20;
{% endhint %}

Setting a new listing to be the Authoritative will remove the identifier from the previous listing selected and set it to the new listing.

<figure><img src="/files/I46dwoCGEBzlFwO133Sj" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
If the Authoritative Listing identifier is being swapped, the owner of the listing that was previously marked as Authoritative will be notified of the change.
{% endhint %}

<figure><img src="/files/DRaFO3Mfm3o7Z5dYdK7c" alt=""><figcaption></figcaption></figure>

## Certified Listing

{% hint style="warning" %}
Users will first need to promote their listing from Sandbox to Production for the Authoritative Listing Toggle to be accessible. For more information on Publishing a listing see the corresponding links here: [Apps](/motar-core-services/intro-to-core-services/studio/manage-each-listing-type/app), [Audio](/motar-core-services/intro-to-core-services/studio/manage-each-listing-type/audio), [Document](/motar-core-services/intro-to-core-services/studio/manage-each-listing-type/document), [3D Model](/motar-core-services/intro-to-core-services/studio/manage-each-listing-type/model), or [Video](/motar-core-services/intro-to-core-services/studio/manage-each-listing-type/video).
{% endhint %}

The Certified Listing Toggle can be found on the Digital Thread tab of Production Listings.

<figure><img src="/files/oqSV1eHflmtwKxZXzO4W" alt=""><figcaption></figcaption></figure>

**CLICK** the **CERTIFIED LISTING** to set it **ON**. This will update the listing to Certified and change the icons on the Digital Thread to match. This signifies to other users that this version of a listing passes a particular set of standards for training as determined by a Studio Admin.

<figure><img src="/files/Df7yaX0UXNbY97VBfyzQ" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Multiple listings in a digital thread can be marked as Certified, this signifies to other users that the listings are certified for training content.
{% endhint %}

Setting a new listing to be Certified will add the Certified icon to each additional listing in a tree that is marked as such without removing the certification from previously selected listings.

<figure><img src="/files/T5HLy52JEcG0bZRUZRQl" alt=""><figcaption></figcaption></figure>


# Secure File Upload & Scanning

The Secure File Upload & Scanning tool launches every time content is uploaded across the platform, ensuring the MOTAR environment remains secure.

## Overview

Security is paramount within MOTAR!  All content uploaded to the platform will be scanned to ensure the MOTAR environment remains free from vulnerabilities.

## How to Use the File Upload & Scanning Tool

Once a file is selected for upload on the MOTAR platform, the **FILE SCREENING** modal will launch. The first **STATUS** will be: **UPLOADING FILE**. If desired, **CLICK** the **CANCEL** button to cancel the upload.

<figure><img src="/files/LZDxx33mWTOepTOCrGln" alt=""><figcaption></figcaption></figure>

Once uploaded, the status will change to: **SCANNING...PLEASE WAIT**.

<figure><img src="/files/cIRBS3BB08ypxCidtlqh" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
If desired, the user can close the modal following the instructions [here](#close-the-file-upload-modal-while-scan-in-progress).
{% endhint %}

Once the file upload and screening is complete, the **STATUS** will change to: **UPLOAD COMPLETE**! **CLICK** the **CLOSE** link or the **X** icon to close the modal.

<figure><img src="/files/gEgvweEFXH6GDCgF25so" alt=""><figcaption></figcaption></figure>

**CLICK** the **CLOSE** link or the **X** icon to close the modal.

After the upload completes, you will be brought to the Info tab automatically.

### Close the File Upload Modal While Scan in Progress

To close the **FILE SCREENING** modal, **CLICK** the **X** icon on the top right of the modal. A warning message will launch.

<figure><img src="/files/mz9yvY1pF7vtSJQDTT75" alt=""><figcaption></figcaption></figure>

**CLICK** the **CANCEL** button to return to the **FILE SCREENING** modal or **CLICK** the **I UNDERSTAND** button to return to the main MOTAR screen. The file progress will be displayed as **IN PROGRESS** next to the file upload status.

<figure><img src="/files/qrk7JWAJjXnNsjhMEmRS" alt=""><figcaption></figcaption></figure>

{% hint style="danger" %}
If the user chooses to close the modal while the file screening is still in progress, they can **NOT** leave or refresh the MOTAR page until the file upload is complete. Doing so will result in the loss of all content that has not yet been successfully uploaded and scanned.
{% endhint %}

### Check File Upload Status

If the **FILE SCREENING** modal was closed, **CLICK** the **IN PROGRESS** link to reopen the modal and check the status.

<figure><img src="/files/LZDxx33mWTOepTOCrGln" alt=""><figcaption></figcaption></figure>


# Add a Skill Badge

Adding **Skill Badges**  to an asset in Studio can only be done during the initial asset creation.&#x20;

After uploading the asset (audio file shown) the new "Badges" tab will appear on supported asset types\*

{% hint style="info" %}
Currently, only video and audio assets support badging.
{% endhint %}

* **Click** on the **Badges** tab to select or **add** a new skill.

### Selecting an existing Skill

<figure><img src="/files/VqwPWaLMH9Z4GkKtUWiw" alt=""><figcaption></figcaption></figure>

* Available skills will show up in the dropdown, or you can type the skill name.
* Selecting that skill and clicking the + button will add the skill to the asset

### Adding a New Skill

* Click "Add New Skill" if none are found.
* A model will appear, enter the Skill Badge Name and Description

<figure><img src="/files/GFiDgHAs0T8dWK1NLN7O" alt="" width="563"><figcaption></figcaption></figure>

{% hint style="warning" %}
Skill Badge Names must be unique. If the name is taken the system will alert you.
{% endhint %}

* After entering the name and description, **Click** "Add Skill"

<figure><img src="/files/aiTFayRbHDO4Ms4uxpfR" alt="" width="563"><figcaption></figcaption></figure>

* The skill will **automatically** be added to the asset.

<figure><img src="/files/kdQSTAsL5fRwRqsOv1Tu" alt=""><figcaption></figcaption></figure>

* Added Skill Badges can be found on the Listing Details Page, once the listing is published.

<figure><img src="/files/03XudihWyETAVtHH9R9x" alt=""><figcaption></figcaption></figure>


# Setting Assets Used

## Assets Used

Items that are remixed may contain additional assets Mark them here to be shown on the Hub card.

<figure><img src="/files/XYCJ4yAxabwc9ZLkOBG6" alt=""><figcaption></figcaption></figure>

**Click** the checkbox next to the asset that was used.


# Spatially Aware Content

We are excited to introduce Spatial Awareness in MOTAR Studio. This update allows you to anchor your digital content to physical coordinates, bridging the gap between virtual assets and the real world.

Currently, you can enable spatial awareness for all asset types supported in Studio under Settings, including:

* 3D Models
* Applications
* Images & Videos
* Audio Files
* Documents

#### Why Spatially Aware Content?

While we are just beginning to unlock the potential of geospatial data within the MOTAR ecosystem, defining the spatial context of your assets now ensures they are ready for future immersive capabilities.

Current Use Cases:

* Contextual Accuracy: If you are uploading a 3D model of a specific facility, adding its latitude and longitude provides a definitive reference for where that object exists in the physical world.
* On-Site Training: Link instructional videos or manuals to the exact equipment location on a base or campus, creating a "digital twin" experience for site-specific content.
* Environmental Relevance: Tag 360-degree photos or audio recordings to the specific terrain where they were captured to maintain situational context.

#### How it Works

When creating or editing an asset in Studio, you will find new fields to input spatial coordinates.

* Precision: Enter coordinates in decimal format (e.g., `38.8977, -77.0365`) to pin your asset to a precise spot on the globe.
* Dynamic Updates: You can update or remove these coordinates at any time as your asset requirements evolve.

#### The Road Ahead: Why Start Now?

By making your content spatially aware today, you are future-proofing your library. Our development roadmap includes powerful tools that will transform how you interact with content:

* Map-Based Discovery: Visualize your entire asset library on a global map to see where your content is concentrated.
* Spatial Search: Search for assets based on their proximity to a specific location (e.g., *"Show me all videos within 5 miles of this coordinate"*).
* Proximity Triggers: Future integrations may allow for content to be automatically served to users based on their physical proximity to a tagged location.

> Pro Tip: Start tagging your assets today to build a more intelligent, spatially aware content library that scales with the future of MOTAR.


# Capturing Geolocation

### Guide: Understanding & Capturing Geolocation

To get the most out of the new geospatial features in Studio, it helps to understand how coordinates work and the quickest way to find them for your assets.

***

#### Part 1: Geolocation 101 - What & How

Think of geolocation as a digital "X marks the spot" for the entire planet. Every point on Earth can be defined by the intersection of two imaginary lines:

* Latitude (North/South): These lines run horizontally like the rungs of a ladder. The Equator is 0°. Anything North is a positive number (up to +90°), and anything South is a negative number (down to -90°).
* Longitude (East/West): These lines run vertically from pole to pole. The Prime Meridian (running through England) is 0°. Everything East is positive (up to +180°) and everything West is negative (down to -180°).

Why we use Decimal Degrees: While you might see coordinates written with degrees, minutes, and seconds (e.g., *38° 53' 52" N*), Studio uses Decimal Degrees (e.g., *38.8977*). This format is the industry standard for software because it’s easier for computers to process, search, and map accurately.

***

#### Part 2: How to Get Coordinates (The Easy Way)

The fastest way to find precise coordinates for an asset is by using a map tool you likely already have.

**Using Google Maps (Desktop)**

1. Navigate to [Google Maps](https://www.google.com/maps).
2. Find the exact spot on the map where your asset belongs (e.g., the building your 3D model represents).
3. Right-click on that spot.
4. A pop-up menu will appear with the Latitude and Longitude listed at the very top.
   1\.

   ```
   <figure><img src="/files/Q3H6AjoHdPBjlzPP9BWB" alt=""><figcaption></figcaption></figure>
   ```
5. Click the coordinates to automatically copy them to your clipboard.

**Using Google Maps (Mobile)**

1. Open the Google Maps app.
2. Long-press (touch and hold) on the map until a red pin drops.
3. On Android: Look at the search bar at the top; the coordinates are displayed there.
4. On iOS (iPhone): Tap the "Dropped Pin" label at the bottom. Scroll down slightly to find the coordinates next to the map icon.
5. Tap and hold the coordinates to copy them.

***

#### Part 3: Best Practices for Studio

* Order Matters: In most systems (including Studio), the format is Latitude first, then Longitude (Lat, Long).
* Don't forget the negative sign: If you are in the Western Hemisphere (like the U.S.) or the Southern Hemisphere (like Australia), your coordinates will likely start with a - (minus sign). Skipping this will place your asset on the opposite side of the world!
* Be as Precise as You Want: You can include several numbers after the decimal point. Four decimal places (e.g., `45.1234`) is usually enough to pin a specific building, while six decimal places can pin a specific corner of a room.


# Listing Performance Metrics

## Video

MOTAR gives creators and instructors insight into how their video assets are performing through CMI5 & xAPI standardized **metrics**. These analytics make it easy to measure learning impact, optimize content, and track skill development.

By combining these metrics, instructors can **gauge learner engagement, identify areas of improvement, and validate skill acquisition** directly within the MOTAR platform. This data helps ensure content is not just delivered, but learned, retained, and applied.

To view metrics on a video asset, navigate to the asset details page

* Click the **Metrics** tab

<figure><img src="/files/yhh45xUQ2YnPWPEIKm41" alt=""><figcaption></figcaption></figure>

### Playback & Engagement Metrics

<table><thead><tr><th width="198">Name</th><th width="337">Description</th><th>Example</th></tr></thead><tbody><tr><td><strong>Launches</strong></td><td>How many times launched</td><td>Launched <strong>159</strong> times.</td></tr><tr><td><strong>Downloads</strong></td><td>Number of times the video has been downloaded</td><td>Downloaded <strong>53</strong> times.</td></tr><tr><td><strong>Completion Rate</strong></td><td>% of viewers who reach 100 %</td><td><strong>92.3%</strong> completion rate.</td></tr></tbody></table>

***

## Audio

To view metrics on an audio asset, navigate to the asset details page

* Click the **Metrics** tab

<figure><img src="/files/W4YT0crT8JcnPXaEgdRd" alt=""><figcaption></figcaption></figure>

### Playback & Engagement Metrics

<table><thead><tr><th width="198">Name</th><th width="337">Description</th><th>Example</th></tr></thead><tbody><tr><td><strong>Launches</strong></td><td>How many times launched</td><td>Launched <strong>159</strong> times.</td></tr><tr><td><strong>Downloads</strong></td><td>Number of times the audio has been downloaded</td><td>Downloaded <strong>53</strong> times.</td></tr><tr><td><strong>Completion Rate</strong></td><td>% of listeners who reach 100 %</td><td><strong>92.3%</strong> completion rate.</td></tr></tbody></table>


# Deleting and Archiving Listings

To remove a listing, open the **Studio Listing** page and click the **trashcan icon** next to the edit button.&#x20;

<figure><img src="/files/1jp1Ups1qUnIVbqPLJOf" alt=""><figcaption></figcaption></figure>

A confirmation dialog will appear:

> *Are you sure you want to delete this listing?*

<figure><img src="/files/OxTUkNj7IYm4hKssdyy0" alt=""><figcaption></figcaption></figure>

#### Behavior of Deleted Listings

Deleted listings will:

* Be marked as **Archived** and set to *view only* in the listing tree.
* Remain available in any trainings where they are already in use.

#### Digital Thread Listings

If the listing is part of a **Digital Thread**, deletion from the Studio page is not allowed.&#x20;

Instead, you will be redirected to the Digital Thread section of the listing, where you can archive it by clicking the **trashcan icon**.

<figure><img src="/files/hDwBIlCllneSGZCoRVs2" alt=""><figcaption></figcaption></figure>


# Tagging

A brief guide on adding tags to your assets.

**Adding and Removing Tags**

Tags improve the searchability of your assets and can be used in the Hub to filter and find content quickly. You can add or remove tags from inside any created asset.

**To add a tag:**

* Select the asset from the Studio listings.

<figure><img src="/files/cFJx5FEnnYS26p41n8UU" alt=""><figcaption></figcaption></figure>

* Open the listing menu to view the asset's permissions, details, and tags.
* Click **+ Add a Tag**.

<figure><img src="/files/Bq7GxaktWSpxLcfFTutF" alt=""><figcaption></figcaption></figure>

* Type your desired tag — autocomplete will suggest any existing tags.

<figure><img src="/files/ktxEwLdEpXmP8uUBFkh3" alt=""><figcaption></figcaption></figure>

* Select an existing tag from the list, or press **Enter** to create and save a new one.

Your tags are now active and searchable in the Hub.

<figure><img src="/files/XZ65kfc354ZsZ7wcK7AO" alt=""><figcaption></figcaption></figure>


# MOTAR 3D

MOTAR 3D is your companion app for navigating immersive assets on MOTAR.

<figure><img src="/files/x53N4CuDvtC5cD31BXCe" alt=""><figcaption><p>MOTAR 3D Hub</p></figcaption></figure>

MOTAR 3D is available for download in the **Configure Platform** menu of the Admin service.

<figure><img src="/files/HmuUM0ISqyNRl8JHreyT" alt=""><figcaption></figcaption></figure>

There are two builds: **Meta Quest** and **Vive**. Each is customized for your platform during creation and includes your domain for device syncing.

Depending on organizational procedures, applications can be obtained in one of two ways:

* **Download Link** – Direct download from the platform. Can be installed to sideload to XR headsets.
* **Download URL** – A shareable link that can be integrated with third-party MDM solutions or provided to users for direct headset installation.

{% hint style="warning" %}
The download URL is publicly accessible.
{% endhint %}

## Installing MOTAR 3D

Follow the guide [Installing Applications on an XR Device](/motar-core-services/intro-to-core-services/devices/installing-applications-on-an-xr-device) to install MOTAR 3D to your XR device.


# MOTAR AI Engine

The MOTAR AI Engine with Zero Trust Orchestration Layer (beta) is a new feature that learns from content on your instance and allows users to query that content, based on the MOTAR Permissions.

{% hint style="warning" %}
**MOTAR AI Engine** with zero trust orchestration layer (beta)  is in early development and may produce incorrect or incomplete information.
{% endhint %}

**MOTAR AI Engine** with zero trust orchestration layer (beta) is now packaged with every MOTAR Instance!\
It automatically **learns** from your uploaded assets to provide contextual answers and insights, while continuing to **respect** all asset **permissions**.\*

<figure><img src="/files/ccYlh9dUogzZXTaginw5" alt=""><figcaption></figcaption></figure>

*To install* **MOTAR AI Engine** with zero trust orchestration layer *(beta) on your instance, follow the guide:* [Advanced Deployment Guide](/welcome/getting-started/production-installation/advanced-deployment-guide#ai-beta-installation)

*\*Currently AI compatible assets do not include 3D models or Apps.*

#### Searching for Assets by Tag

The MOTAR AI chat supports natural language tag queries. Use any of the following patterns to find assets:

**Find assets with a specific tag:**

* `Show me assets`` `**`tagged`**` ``with training`
* `Find items with the`` `**`tag`**` ``safety`
* `What assets have a`` `**`tag`**` ``of onboarding?`
* `Do I have anything`` `**`tagged`**` ``maintenance?`

**Browse or audit your tags:**

* `Do I have any`` `**`tagged`**` ``items?`
* `What`` `**`tags`**` ``are on my assets?`
* `How many`` `**`tagged`**` ``items do I have?`
* `Show me items with`` `**`tags`**

**Tips:**

* Tag names are **not** case-sensitive — `Safety` and `safety` work the same.
* Tags with hyphens or dots are supported — e.g., `tagged with safety-vest` or `tag of v1.2`.
* Quotes around the tag name are optional — `tag "onboarding"` and `tag onboarding` both work.
* The query just needs to include a recognizable tag phrase followed by your tag name — phrasing doesn't have to be exact.

**What won't work:**

* Very short or ambiguous phrasing like `find safety` (no tag keyword) — include words like *tagged*, *tag*, or *items with tag* to trigger tag search.


# MOTAR CertIQ

Downloaded MOTAR CertIQ certificates can be imported to any enabled MOTAR CertIQ compatible system.

<figure><img src="/files/ShmQVmgN5bGEEpjajRBh" alt="" width="563"><figcaption></figcaption></figure>

<figure><img src="/files/w2dAv97m2bdcXdbuzXHT" alt="" width="563"><figcaption></figcaption></figure>

### Importing a Certificate

* In the Admin service, **click** Users / Edit User / Learner Record
* **Click** "Import Certificate"

<figure><img src="/files/HlTO6nlQlqFh2viIucMn" alt=""><figcaption></figcaption></figure>

* An import window will open, select the **MOTAR CertIQ PDF**&#x20;
* Compatible certificates will import the Skill Badge into the system.

### Downloding a Certificate

#### As a User

If a **Skill Badge** is associated with the completed asset, a "download certificate" icon will appear.

* **Navigate** to the User / Record section under the [Profile ](/motar-core-services/intro-to-core-services/profile)Service
* **Click** the "Download Certificate" icon to automatically generate and download a PDF certificate for that **badge.**

<figure><img src="/files/fhLeb6RPVCAqqYhcXcQq" alt=""><figcaption></figcaption></figure>

* The PDF is compatible with any [**MOTAR CertIQ**](/additioinal-features/motar-certiq) system.

<figure><img src="/files/w2dAv97m2bdcXdbuzXHT" alt="" width="563"><figcaption></figcaption></figure>

### CMI5 Learner Data Integration

Our platform issues "smart" digital certificates that do more than just prove completion, they carry a comprehensive payload of verifiable performance data. By embedding cmi5 data directly into our certification records, we bridge the gap between simple achievement and granular learning analytics.

#### Why cmi5?

While traditional SCORM provides basic "Pass/Fail" data, cmi5 (the contemporary profile for xAPI) allows our certificates to store a rich history of how the learner interacted with the content. This ensures that every credential is backed by a verifiable, high-fidelity audit trail.

#### Technical Structure

Our certificates output a JSON-based schema that is easily consumable by external Learning Record Stores (LRS) or HRIS systems.

*Example fields*

| **Key Field**      | **Description**                                                          | **Example Value**                |
| ------------------ | ------------------------------------------------------------------------ | -------------------------------- |
| `skillName`        | The specific competency earned.                                          | "Novice Level Drone Maintenance" |
| `awardedToEmail`   | Unique identifier for the learner.                                       | `elena.vasquez@spaceforce.demo`  |
| `wasCompleted`     | Boolean confirmation of requirement fulfillment.                         | `true`                           |
| `skillsAwardedRaw` | A serialized string of the raw cmi5/xAPI statement for deep integration. | See image logs                   |

#### Portability and Verification

Because the data is embedded using the cmi5 profile, these certificates are highly portable. They can be moved between compatible platforms without losing the underlying "proof of work" data, making them an ideal solution for high-stakes industries where precise maintenance of training records is a regulatory requirement.

<figure><img src="/files/mCAbJIMgkpyYPOMLUpe3" alt=""><figcaption></figcaption></figure>




---

[Next Page](/llms-full.txt/1)