> 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/release-notes/web/2026/release-15-40-snooze-alarms.md).

# Release 15.40: Snooze Alarms

January 22, 2026

Updates to the Solink platform in this release include:

***

## New Features

* **Snooze Alarms:** Added the ability to "snooze" an alarm, either across an entire location or via specific cameras. This allows users to temporarily disarm the system for a set period of time, then automatically re-arm after the snooze time has passed.

```
* Snooze is helpful if you know an employee or contractor will be on site for a short period of time and you do not want them to trigger the alarm, for example.
* Snooze is accessible from the Alarms page in the Solink platform and in the VerifEye console when responding to an event. 


<img src="../../.gitbook/assets/faae21c4ad6a40fe.png" width="360" alt="">

* An admin user must enable the Snooze permission for a user in the Solink platform via the [Users](../../../manage-users-locations-and-account/users-page.md) page in **Settings**. 


<img src="../../.gitbook/assets/c65039cb7375a0cc.png" width="640" alt="">
```

***

## Enhancements

* Updated UI for [Location Selector](/docs/manage-users-locations-and-your-account/location-management-location-tags.md).

| **Before** | **After** |
| ---------- | --------- |
|            |           |

## Bug Fixes

* Fixed an issue where some users were able to test an alarm for non-alarm cameras.


---

# 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/release-notes/web/2026/release-15-40-snooze-alarms.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.