> 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/sessions/joining-a-session/joining-a-listed-session.md).
# Joining a listed Session
1. On the menu screen, select **Join Session**.
2. On the **Join Session** page, select **Live**.
3. The default list is the **Public** list. If you are a member of an Enterprise group, the group name, or list of group names, is displayed next to the **Public** tab. To view Sessions that are restricted to a group, select the group name.
4. To join a Session, select it.
5. On the Session details page, select **Join**.
{% hint style="warning" %}
On both the Join Session and Session details pages, the numbers next to the attendees icon .png?alt=media)
indicate current and maximum capacity. If a Session is full, you can't join.
{% endhint %}
6. If the Session requires a password, enter the password, and then select **Continue**.
7. If you need to download the location, wait for the download to complete, and then select **Go now**.
{% hint style="info" %}
An Enterprise group may choose to remove access to the public list for their members. If they do, the Join Session page initially shows a list of the group's Sessions. If there are any persistent Sessions associated with the group, these appear first in the list.
{% 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/sessions/joining-a-session/joining-a-listed-session.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.