> For the complete documentation index, see [llms.txt](https://faq.growsensor.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://faq.growsensor.co/the-grow-app/how-do-i-use-the-grow-dashboard/what-are-grows.md).

# What are grows?

Currently, each grow can contain one Grow Sensor, but in the future, you’ll be able to add multiple sensors to track different zones within the same grow.

### How grows work:

* A grow starts when you plant a seed and ends at harvest.
* Once a grow is complete, you can archive it and start a new one, allowing you to review past data and improve your next grow.
* In future updates, you’ll be able to:
  * Add tags (e.g., “Started flowering on \[date]”)
  * Leave notes for reference
  * Analyse specific weeks of your grow for crop registration and better plant optimisation.

**The key takeaway here is that a grow is one full plant cycle. When you’re done, review, analyse, archive, and start fresh - using past insights to grow even better next time!**

<br>


---

# 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://faq.growsensor.co/the-grow-app/how-do-i-use-the-grow-dashboard/what-are-grows.md?ask=<question>&goal=<endgoal>
```

`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.