> 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/how-to-use-dashboard-trends.md).

# How to use dashboard trends?

If you’ve [<mark style="background-color:red;">set limits</mark>](https://docs.google.com/document/d/1aPP2hTh4Qcg-TKOk6RpB5yBrL8dzmOhgo8bTjV2PRg4/edit?tab=t.0#heading=h.ttenbgrkcwqk) for your grow, they’ll be displayed in a bar graph below each sensor value on your dashboard.

These bars visually represent your defined limits and show exactly where your current readings fall within your chosen range.

Each bar also includes a trend indicator, helping you quickly assess whether conditions are improving, worsening, or staying stable:

* **Left or right arrow** – The issue is shifting in the given direction (either worsening or improving).
* **White line** – The value is stable and not changing significantly.

This at-a-glance view makes it easy to understand your grow's overall health.&#x20;

With just a quick look, you’ll know whether you need to take action or if everything is running smoothly, and you can relax, knowing your grow is in control.

Need help? Contact us at <support@growsensor.co> we’re happy to help!

<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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://faq.growsensor.co/the-grow-app/how-do-i-use-the-grow-dashboard/how-to-use-dashboard-trends.md?ask=<question>&goal=<user_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.