# Alarm rules
Users with **Administrator** or **Manager** permissions can configure alarm rules by selecting **Rules and Notifications** from the settings menu.
In Efento Cloud, **alarm rules** determine which events trigger notifications or alarms. Each rule consists of three main components:
1. **Stimulus** – The monitored value or condition, such as a sensor measurement (e.g., temperature).
2. **Condition** – The threshold or criteria that must be met to trigger the alarm (e.g., rises above 10°C).
3. **Action** – The response to the alarm, such as sending an SMS, email, or simply logging the event.
Alarm rules are fully **customizable**. For example, you can configure different recipients to receive notifications depending on the severity of the threshold breach, or set rules to only log events without sending notifications. Users can create multiple alarm rules and assign them to specific sensors or gateways as needed.
There are **two types of rules** in Efento Cloud:
* **Sensor rules** – Monitor sensor measurements and trigger alarms based on defined thresholds.
* **Gateway rules** – Monitor the status and health of gateways, such as connectivity or operational issues.
To learn how to configure each rule type, please refer to the sections below.
{% content-ref url="/pages/xhGWHP1uGcKDMTrvXJjY" %}
[Sensor rules](/efento-cloud/advanced/markdown/sensor-rules.md)
{% endcontent-ref %}
{% content-ref url="/pages/eVzX2r91W50axGrM4pLC" %}
[Gateway rules](/efento-cloud/advanced/markdown/gateway-rules.md)
{% endcontent-ref %}
## Managing Alarm rules
Once alarm rules are created, Efento Cloud provides several tools to help you efficiently organize, review, and maintain them. All configured rules are displayed in a structured list that includes key information such as the rule name, threshold type and value, assigned recipients, and the sensors or locations covered by the rule. This overview allows administrators and managers to quickly verify how each rule is set up and ensure that the monitoring system operates as intended.
In the **Actions** column on the right side of the rules table, you will find several management options:
* **Edit (pencil icon)** – Opens the full configuration panel where you can modify any part of the rule, including thresholds, notification recipients, schedules, and assigned sensors.
* **Delete (trash can icon)** – Permanently removes the selected rule from the platform. Deleted rules cannot be recovered, so use this option with caution.
* **Clone** – Creates an exact copy of the selected rule, including its conditions, assigned devices, notifications, and schedules. This feature is especially useful when setting up multiple similar rules, as it saves time and ensures configuration consistency.
On the **left side of the Rules view**, a location tree is available. This tool helps you organize and filter alarm rules based on the structure of your organization. When you select a location, the platform displays only the rules associated with sensors assigned to that location and its sub-locations. All other rules remain hidden, which is particularly helpful in large, multi-site deployments where dozens or even hundreds of rules may exist.
Using the location-based filtering system, administrators and managers can:
* Quickly review rules relevant to a specific facility or area
* Reduce clutter by hiding unrelated rules
* Simplify maintenance in complex monitoring environments
## **Exporting the Rules List**
To export all alarm rules, click the **Export rules list** button. A PDF file containing the complete list of configured rules will be generated and sent to the email address associated with your Efento Cloud account.
---
# Agent Instructions: 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:
```
GET https://docs.efento.io/efento-cloud/advanced/markdown.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.