> 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/building/levels/daylight-grids.md).
# Daylight Grids
Daylight Grids are used to analyse daylight performance and are added per level in your model. Each level can have multiple grids, and these can be combined with automatically generated daylight grids for more detailed analysis.
## Add a Daylight Grid
To add a Daylight Grid, start by selecting Levels on the left, then choose a level and click ‘Add Daylight Grid’. Turn on the Layers for the relevant zone, click the ‘Add Grids’ icon, and draw your grid in the drawing space. To add a single line for analysis, use ‘Add lines’ and draw a Daylight Grid line.
## Mode
By default, grids are drawn in the ‘Include Grid in this Area’ mode. If you need to exclude part of the area, switch to ‘Exclude Grid from this Area’ before drawing.
### Delete a Daylight Grid
To delete a Daylight Grid, go back to the Levels panel, find the Daylight Grid icon and click ‘Delete Daylight Grid’, then confirm. Alternatively, you can delete it directly within the drawing space.
---
# 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/building/levels/daylight-grids.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.
