> 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/turning-on-spatial-data-permission.md).
# Turning on spatial data permission
To use mixed reality on a Meta Quest headset, you must allow the ENGAGE application to access spatial data stored on the device. If this permission is not requested when you install ENGAGE, you initially deny permission, or you turn it off, then you must turn it on manually.
To manually turn on permission to access spatial data, complete the following steps:
1. Press the Meta or Oculus button on your right Touch controller to open the universal menu.
2. Select the clock to open the **Quick settings** panel.
3. Select **Settings**, and then select **Privacy and safety**.
4. Select **App permissions**, and then select **Spatial data**.
5. Turn on the spatial data permission for ENGAGE.
Permission to access spatial data on a Meta Quest 3 headset
---
# 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/turning-on-spatial-data-permission.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.
