> 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/2025/release-15-23-verifeye-update.md).

# Release 15.23 - VerifEye Update

See the following updates to the Solink platform between Feb 19 - March 13, 2025:

***

## Enhancements

* [**VerifEye**](/docs/protect-your-locations-with-alarms/alarms-with-ai-detection/verifeye-alarm-verification.md) **update**: Added additional options when reviewing alarm footage after selecting "No Threat". Select either of these new options to disarm the system for a set period of time:
  * **Contractor**: Select this optionif it is clear a contractor onsite triggered the alarm\*\*.\*\*
  * **Delivery**: Select this optionif it is clear a delivery person onsite triggered the alarm\*\*.\*\*

***

## Bug Fixes

* Fixed an issue with [360 cameras](/docs/watch-and-find-video/manage-cameras/360-cameras-in-solink.md) displaying a black screen.
* Fixed an issue with [Dashboard tabs](/docs/understand-your-business/widget-configuration/dashboard-pages.md) (for example, the Alarms or Health tabs) not displaying upon logging into the Solink platform.
* Fixed an issue that prevented non-Admin Solink users from using [Zone Tracking Search](/docs/understand-your-business/ai-features/vision-analytics/zone-tracking-search.md) and [Zone Tracking Events](/docs/understand-your-business/ai-features/vision-analytics/zone-tracking-events.md).


---

# 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/2025/release-15-23-verifeye-update.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.