> 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/essential-features/accessing-engage-content.md).
# Accessing ENGAGE Experiences
The ENGAGE application includes a curated collection of immersive experiences and 360° videos.
If you want to share an Experience with other people, we recommend that you start the Experience in a Session. An Experience begins to play as soon as it downloads, and you may not be able control the playback. If you invite people to a Session before you start the Experience, you ensure that everyone views the Experience from the start.
## In a Session
1. Open ENGAGE, and then log in.
2. Start a Session and invite everyone you want to share the Experience with. For more information, see [Creating a Session](/engage/sessions/creating-a-session.md) and [Inviting others to your Session](/engage/sessions/inviting-others-to-your-session.md).
3. Open your menu or tablet, and then select **Experiences** 
.
4. Select an Experience from the library.
5. On the Experience information page, select **START**.
6. In the **Load Experience** prompt, select **Confirm**.
## From the menu screen
1. Open ENGAGE, and then log in.
2. On the menu screen, select **Experiences** .
3. Select an Experience from the library.
4. On the Experience information page, select **START**.
5. On the **Start Session** page, choose **Just Me** to view the Experience by yourself. You can choose **With Others**, but some people may miss the start of the Experience.
---
# 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/essential-features/accessing-engage-content.md?ask=&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.