> For the complete documentation index, see [llms.txt](https://docs.gmetri.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gmetri.com/metaverse/publishing/authentication.md).

# Authentication

Control who accesses your deployment

You can control who accesses your deployments by changing it's Authentication.

<figure><img src="https://2186043722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Mgll1jjQMRTVj7p6n7g%2Fuploads%2FJ0jlYgeCdQ4zjJI7G9T4%2FGMetri%203.png?alt=media&amp;token=bb3466d0-87c1-4093-8737-1543c523c87a" alt=""><figcaption><p>Authentication Options</p></figcaption></figure>

## Public

This option allows anyone to access your deployment

## Social

The viewer can login using their social credentials like Google or Facebook/Instagram account to access your experience

## Load from another experience

This allows you to link multiple deployments. Selecting this option makes this deployment visible in the “Open Deployment” rule while you build another experience.

{% content-ref url="/pages/3F6RRfdb409MbufJt75H" %}
[Load from another Experience](/metaverse/publishing/authentication/load-from-another-experience.md)
{% endcontent-ref %}

## Public with history

This option allows anyone to access your experience, but GMetri assigns a viewer id to track history. So when the same person accesses the experience again from the same device and browser, their variables or progress would remain intact.

## Advanced Authentication Mechanisms

There are a lot more authentication mechanisms you can use:

### SCORM

{% content-ref url="/pages/-Mgse-VB5YtYtymg\_J8c" %}
[Export as SCORM package](/metaverse/publishing/gmetri-experience-as-scorm-package.md)
{% endcontent-ref %}

{% hint style="info" %}
The authentication options below are available only for the enterprise tier
{% endhint %}

### SSO/SAML

{% content-ref url="/pages/WpUQRZpFORy8IwgqV7Bi" %}
[SSO](/metaverse/publishing/authentication/sso.md)
{% endcontent-ref %}

### Custom List

{% content-ref url="/pages/XIi6sHUe36nQdkWpFWI3" %}
[Custom List](/metaverse/publishing/authentication/custom-list.md)
{% endcontent-ref %}

### Token

{% content-ref url="/pages/4C1TxidwXw5QnWOM2T0x" %}
[Token](/metaverse/publishing/authentication/token.md)
{% endcontent-ref %}

### Password With Expiry

{% content-ref url="/pages/XwtcAFzyxwD7Izx0JKlQ" %}
[Password With Expiry](/metaverse/publishing/authentication/password-with-expiry.md)
{% endcontent-ref %}

### Email with OTP

{% content-ref url="/pages/cLrMECOA8lcPWOyjPLlB" %}
[Email with OTP](/metaverse/publishing/authentication/email-with-otp.md)
{% endcontent-ref %}

## Viewer Groups

Many of the above authentication mechanisms can be setup from the Viewer Group section.

<figure><img src="https://2186043722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Mgll1jjQMRTVj7p6n7g%2Fuploads%2F1rCGwlkmler6EWpFvbFe%2Fviewer%20group.png?alt=media&amp;token=ce645faf-d1df-4edd-8a43-a9d5a79099a0" alt=""><figcaption><p>Opening the Viewers Group page from the portal menu</p></figcaption></figure>

<figure><img src="https://2186043722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Mgll1jjQMRTVj7p6n7g%2Fuploads%2FMkDmNHi2rYyDr1khp2S5%2Fviewer%20group%202.png?alt=media&amp;token=ff221f25-19eb-4e47-9857-729af9e1f18c" alt=""><figcaption><p>Viewer Groups</p></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.gmetri.com/metaverse/publishing/authentication.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.