> For the complete documentation index, see [llms.txt](https://docs.betterbuilding.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.betterbuilding.io/user-guide/2d-building/drawing/set-a-zone-height.md). # Set a Zone Height Zones represent thermal spaces within your model, whether they’re air-conditioned or not. All zones on the same drawing share the same height and are drawn to their required dimensions. Zones should be set up right after creating the first one. ## Set Single Zone Height Go to the admin area in the drawing space and click on the default ‘Storey Height’. Enter the new height for your zones (in mm), then click ‘Update’ and ‘Save’.
Important: Set the zone height before adding any windows. Changing it afterwards may cause window-wall clashes, which will result in the windows being removed automatically ## Setting Multiple Zone Heights If your design requires different heights, you can combine zones into single volumes by applying air-floors, allowing you to model multi-height spaces accurately. --- # 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.betterbuilding.io/user-guide/2d-building/drawing/set-a-zone-height.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.