> 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-set-limits-and-alerts-for-graphs/how-do-i-set-high-low-and-dangerously-high-low-limits.md).

# How do I set high/low and dangerously high/low limits?

Setting limits helps you stay in control of your growing environment by providing alerts and visual cues when conditions shift outside your ideal range.

### **How to set limits:**

{% stepper %}
{% step %}
Click on your grow in the dashboard.
{% endstep %}

{% step %}
Tap the cog icon in the top right corner.
{% endstep %}

{% step %}
Select "Limits and Alerts."
{% endstep %}

{% step %}
You’ll see a collapsed list of all available limits. If you've enabled night and day photoperiods, you’ll have two sets of limits - one for day and one for night.
{% endstep %}

{% step %}
Click on a limit to expand the settings.
{% endstep %}
{% endstepper %}

### **What you can adjust:**

For each parameter, you can set:

* **High limit & low limit** – Triggers an early warning when values rise above or below your set threshold.
* **Dangerously high and dangerously low limit** – Signals urgent action is needed.
* **"Alert Me" toggle** – Enable this to receive push notifications when a limit is breached.

### **Customising limits to your grow style**

How you use limits is entirely up to you; every grower is different. 

Some prefer tight limits for early warnings, while others only want notifications for dangerously high or low readings, using standard limits as a visual guide.

Experiment and find what works best for your setup!

Need help? Contact us at <support@growsensor.co>.&#x20;

<mark style="background-color:red;">Add video</mark><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-set-limits-and-alerts-for-graphs/how-do-i-set-high-low-and-dangerously-high-low-limits.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.