> For the complete documentation index, see [llms.txt](https://docs.engagevr.io/engage/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.engagevr.io/engage/getting-started/creating-an-account.md).

# Creating an account

You can create your account either in the web manager or in the ENGAGE app.

* To use the web manager, go to <https://app.engagevr.io/register>.
* To use the ENGAGE app, open ENGAGE, and then select **Sign up** on the menu screen.

{% hint style="info" %}
If you intend to join an Enterprise group that has single sign-on (SSO) turned on, see [Single sign-on (SSO)](/engage/getting-started/creating-an-account/single-sign-on-sso.md).
{% endhint %}

<figure><img src="https://3460182399-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwVx6bvwqEE7tD0TYOcfj%2Fuploads%2Fgit-blob-faa1ce03818efa1ba7d5bbbe127c4e4e5eb78995%2Fapp_new_acc_wt_sso.jpg?alt=media" alt=""><figcaption><p>Sign up link on the main menu of the ENGAGE app</p></figcaption></figure>

The ENGAGE app is the fastest option, because you can enter all of the required information, and then immediately start to use the app. However, you may find it easier to enter information in the web manager, particularly if you want to use ENGAGE on a VR headset and don't have much experience with virtual reality.


---

# 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.engagevr.io/engage/getting-started/creating-an-account.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.