> For the complete documentation index, see [llms.txt](https://move-solutions.gitbook.io/untitled/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://move-solutions.gitbook.io/untitled/getting-started/how-do-i-configure-alarm-notification.md).
# How do I configure alarm notification?
This guide explains how to add and manage contacts who will receive alarm emails triggered by threshold exceedances from sensors in your project.
***
### **Step 1 – Navigate to the Notifications Section**
1. From the left-hand menu, go to Settings.
2. Select the Notifications tab.
***
### **Step 2 – Add a New Contact**
1. Click the “Add Contact” button in the top-right corner.
2. Fill in the required fields:
* Contact Name: Enter the full name of the recipient.
* Contact Email: Enter a valid email address where alarm notifications will be sent.
3. Choose the sensor types for which the contact should receive alarm notifications. You can enable or disable:
* Dynamic Displacement Sensor
* Accelerometer
* Vibrometer
* Tiltmeter
* Communication Node
4. Click “Save” to add the contact to the list.
Add / Edit Contact modal - Notifications settings
{% hint style="info" %}
Ensure the contact is set to Active to start receiving emails. To temporarily disable notifications, change the status to Paused.
{% endhint %}
***
### **Step 3 – Edit or Delete Contacts (Optional)**
* To edit a contact’s name, email, or preferences, click the pencil icon.
* To remove a contact entirely, click the trash icon.
***
This setup ensures that selected recipients are notified in real time when sensors report critical, warning, or alert-level threshold violations.
---
# 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://move-solutions.gitbook.io/untitled/getting-started/how-do-i-configure-alarm-notification.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.
