> 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-56-investigations.md).

# Release 15.56: Investigations

September 2, 2026

Updates in this release include:

***

## New Features

* [**Investigations**](/docs/review-events-and-save-evidence/investigations.md): Organize events and saved video clips into one collection so you can review and focus on important footage:

***

## Enhancements

* **Vision Analytics**: Changed the indicator that displays the total number of AI cameras configured at the location. Previously, there were dots that showed the number of cameras currently configured for AI/Vision Analytics (in addition to the total number of cameras you could configure for AI at this location). Now a number is displayed to prepare for future increases to the number of AI cameras supported per location:

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

***

## Additional Notes

* [**Guest Access**](/docs/protect-your-locations-with-alarms/alarm-setup/alarm-guest-access-legacy-feature.md): The Alarms Guest Access feature is being transitioned to legacy status. Users with existing Guest Access contacts can still edit and delete these contacts. Users who did not use the Guest Access feature will no longer see the option to use it.


---

# 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-56-investigations.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.