> 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/creating-an-account-in-the-web-manager.md).

# Creating an account in the web manager

1. Go to <https://app.engagevr.io/register>.
2. Complete the account creation form, review and accept the *Terms of Service and Privacy Policy*, and then select **SIGN UP**.
3. On the **EDIT PROFILE DETAILS** page of the web manager, update your other profile information. The value that you enter for **Height** is applied to your avatar. To ensure accurate tracking if you use a VR headset, enter a **Height** value that closely matches your real height.
4. You will receive an email that explains how you can verify your email address. You must complete this process within 72 hours.

You can now open the ENGAGE app, log in, and then create your avatar. For more information, see [Creating your avatar](/engage/getting-started/creating-your-avatar.md).

{% hint style="info" %}
You can log in and use the ENGAGE app before you verify your email address. If you do, you will see a reminder to verify your email, but you can select **Continue** to start to use ENGAGE.
{% endhint %}


---

# 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/creating-an-account-in-the-web-manager.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.