> 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/persistent-sessions/setting-the-location-for-a-persistent-session.md).
# Setting the location for a persistent or commercial Session
When you create a persistent or commercial Session, its location is automatically set to the *Hub Space*. To set a different location, a user with host permissions must join the Session, and then use the in-Session menu to change the location.
* For instructions on how to change the location of a Session, see [Changing location](/engage/advanced-features/changing-locations.md).
The Session will use the new location until you or someone else with host permissions chooses a different location.
{% hint style="info" %}
If the first user to join an empty persistent or commercial Session encounters an error, and that error is attributed to the location, the persistent Session will reset to use the Hub Space.
{% endhint %}
The Hub Space location
---
# 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/persistent-sessions/setting-the-location-for-a-persistent-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.
