> For the complete documentation index, see [llms.txt](https://help.solink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.solink.com/docs/protect-your-locations-with-alarms/use-and-configure-alarms/manage-open-alarms.md).
# Manage Open Alarms
Whenever an alarm is triggered, an **open alarm event** is created with video footage and associated data. Open alarms are alarms that are currently in progress and recording footage.
You can review open alarms from the **Alarms** page > **Recent Alarm Events**:
In the mobile app, locations with an open alarm appear under **Open Alarms** on the **Alarms** page. See the **Mobile** tab in [Close an Open Alarm](#close-an-open-alarm).
You can also view past open alarm events from the **Events** page. Select the **Alarms** tab on the Events page (as shown in the image below) to display only alarm events. This is a useful feature if you want to create reports using alarm events:
**Note:** Only users with an Alarm Administrator role (configured by a Solink representative) can see alarm events displayed on the **Events** page.
To view your **Open** alarms:
1. Select a specific location or **All locations** from the left sidebar:
2. Select **Open** near the top-right of the page:
3. Any **Open** alarm for the selected location (or all locations if you have selected All locations from the sidebar) is displayed on the page, as shown in the example below:
***
### Close an Open Alarm
{% tabs %}
{% tab title="Web" %}
You can close an open alarm from the **Recent Alarm Events** section; this can be especially useful to dismiss false alarms and ready the alarm system to detect future alarms. You can also temporarily disarm the alarm system from this location.
To close an open alarm:
1. From the **Recent Alarm Events** section, select a location.
2. If there is an open alarm, you will see the **Close** option (if you are using [VerifEye](/docs/protect-your-locations-with-alarms/alarms-with-ai-detection/verifeye-alarm-verification.md), you instead see a "Verify" option and must review the alarm event through the VerifEye console. You can still close the event this way.).
3. A message appears to confirm the alarm has been successfully closed.
**Note:** To disarm the alarm temporarily for this location, select **Disarm** instead, then choose for how long you would like to disarm the alarm system (15 minutes, 30 minutes or 60 minutes. Or until the next scheduled arm period based on your alarm schedule).
{% endtab %}
{% tab title="Mobile" %}
When an alarm is active:
* The location appears under **Open Alarms** on the **Alarms** page.
* An active-alarm notice may appear on the location detail screen.
* Open alarm cameras or event video to investigate.
* From the video player, use **Close Alarm** when the situation is resolved.
{% endtab %}
{% endtabs %}
***
### Temporarily Disarm an Open Alarm
You can temporarily disarm an open alarm for a set period of time (similar to a "snooze" button on an alarm clock).
To disarm an open alarm:
1. From the Recent Alarm Events tab, choose an open alarm you want to temporarily disarm. Select **Disarm...**.
2. Choose the amount of time you wish to disarm the alarm for (or choose to disarm until the next scheduled alarm period):
3. Select **Confirm**.
---
# 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://help.solink.com/docs/protect-your-locations-with-alarms/use-and-configure-alarms/manage-open-alarms.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.