> For the complete documentation index, see [llms.txt](https://documentation.nomos-system.com/nomos-system/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.nomos-system.com/nomos-system/integrator-en/zones.md).
# Zones
The "**Zones**" function in the nomos system Controller allows you to group rooms into logical units such as floors, wings, or other larger sections. This is particularly useful in large buildings or complex facilities to ensure a clearer structure and organization.
**What Are Zones?**
* Zones represent larger logical units within a building or system. Examples of zones could include:
* **Floors** (e.g., Ground Floor, 1st Floor, 2nd Floor)
* **Building wings** (e.g., West Wing, East Wing)
* **Building sections** (e.g., Administration Area, Production Area)
* Multiple rooms can be organized and managed within each zone.
**Screen Overview**
* **Create New Zone:**
* At the top right of the screen, you'll find the "**New Zone**" button.
* **Add Rooms to a Zone:**
* Once a zone has been created, you can assign rooms to this zone to further refine the structure.
* This facilitates the management of automations, scenes, and device states, as you can control an entire zone (e.g., a floor) collectively.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://documentation.nomos-system.com/nomos-system/integrator-en/zones.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.