> 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/web-manager.md).

# Web manager

You can access the web manager through a web browser, and use it to perform tasks that support your use of the ENGAGE app.

Many of the ENGAGE platform's features are available in both the web manager and the ENGAGE app. Changes that you make in one are synchronized with the other. For example, you can prepare web and video links in the web manager, and then access them in the ENGAGE app. Similarly, you can create notes in a Session in the ENGAGE app, and then access them in the web manager.

You can also use the web manager to perform tasks that aren't available in the ENGAGE app, such as manage a plus account subscription.

* To access the web manager, go to [https://app.engagevr.io/](https://app.engagevr.io), and then log in. You use use the same account details for both the web manager and the ENGAGE app.

For more information about the features that are available in the web manager, see the following sections.


---

# 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/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.