> 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/advanced-features/mixed-reality/room-setup.md).
# Room setup
Headsets that support mixed reality include tools to create a digital model of your physical space. This may include an automatic scan of your environment, manually adding features such as walls and furniture, or a combination of the two.
When you access mixed reality in ENGAGE, if you haven't already created a model of your physical space, the application will open your headset's tools so that you can do so.
{% hint style="warning" %}
If the application prompts you to set up your room space but you have already done so, you may need to manually turn on the required permission. For more information, see [Turning on spatial data permission](/engage/advanced-features/mixed-reality/turning-on-spatial-data-permission.md).
{% endhint %}
To access your headset's room setup tools at any time, complete the following step:
* On the menu screen, in the upper-right corner, select settings 
, select **Mixed Reality**, and then select **Room Setup**.
---
# 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/advanced-features/mixed-reality/room-setup.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.