> 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-46-15-47-ai-vehicle-drive-off-detection.md). # Release 15.46/15.47: AI Vehicle Drive-Off Detection April 29, 2026 Updates to the Solink platform in these releases include: *** ### New Features * [**AI Vehicle Drive-Off Detection**](/docs/understand-your-business/ai-features/vision-analytics/drive-off-detection.md): Added the ability to track when drive-offs occur at your locations via AI Zone Tracking (Vision Analytics). * Added new [user permission](/docs/manage-users-locations-and-your-account/users-page.md): * A new "**Live View Only**" user permission has been added that allows you to grant users access to view live camera feeds, but without access to recorded footage (such as clips, events, etc.). * When this permission is enabled for a user or role: * The user can access the **Video** page and watch live camera streams. * The date/time picker and archive toggle are disabled. * The timeline is non-interactive — selecting or dragging to seek is blocked. * All non-**Video** pages are hidden from navigation. * The session always starts (and stays) in live mode. *** ### Bug Fixes * Fixed an issue where users who did not have [alarm snooze](/docs/protect-your-locations-with-alarms/use-and-configure-alarms/snooze-alarms.md) permission could temporarily disarm locations without a threat present. --- # 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-46-15-47-ai-vehicle-drive-off-detection.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.