> For the complete documentation index, see [llms.txt](https://docs.gmetri.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gmetri.com/metaverse/build/scenes/3d-scene/zones.md). # Zones Zones are *interactive areas* that can be used for a variety of purposes.

When you add a new 3D Scene, there's always a default Zone that gets added - which is the spawn zone. A Spawn Zone controls where viewers will spawn when they enter the 3D Scene. ### How can I set the spawn zone? To include a 'Zone' in your experience, navigate to the 3D elements section and click the '+' icon. Then, select the 'Zone' element and add it to your experience.

To manage the 'Spawn Zone', access the properties panel by selecting the appropriate scene from the right panel. From there, navigate to the 'Spawn Zone' section and choose the desired zone to set as the Spawn zone.

### How can I detect when a viewer enters a zone? You can add a "Then Rule" to detect when the viewer enters a zone.

### How can I teleport to a zone? By incorporating rules, you have the ability to teleport your viewer to a different zone or scene.

## Also Read {% content-ref url="/pages/mJPqUjlr5B6jUW6h6LBY" %} [Rules](/metaverse/build/rules.md) {% endcontent-ref %} --- # 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.gmetri.com/metaverse/build/scenes/3d-scene/zones.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.