> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/classic-alarms/readme.md).

# Classic Alarms

Detect and respond to intruders using our software, devices, and services

{% hint style="success" %}
Verkada announced the global End of Sale (August 1, 2026) and End of Life (August 1, 2027) for Classic Alarms. Eligible customers can upgrade to New Alarms at no charge through January 31, 2027. Visit [Verkada.com/alarms/upgrade](https://www.verkada.com/alarms/upgrade) to get started.
{% endhint %}

**Overview**\
Verkada Classic Alarms is a cloud-managed intrusion detection system designed to secure your facilities with a combination of sensors, door contacts, and sirens. It provides real-time alerts and centralized management, allowing you to monitor alarm activity and respond quickly from a single interface.

This collection provides detailed guidance on installing and configuring Classic Alarms, managing notifications and events, and maintaining reliable operation. It helps you deploy alarms efficiently and ensure your security monitoring remains consistent and effective.

Check out these links to get started:

<table data-view="cards"><thead><tr><th></th><th data-type="content-ref"></th></tr></thead><tbody><tr><td></td><td><a href="/classic-alarms/getting-started/get-started-with-verkada-classic-alarms.md">Get Started with Verkada Classic Alarms</a></td></tr><tr><td></td><td><a href="/classic-alarms/getting-started/quick-reference-guide-for-verkada-alarms.md">Quick Reference Guide for Verkada Alarms</a></td></tr><tr><td></td><td><a href="/classic-alarms/getting-started/classic-alarms-network-settings.md">Classic Alarms Network Settings</a></td></tr></tbody></table>


---

# 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.verkada.com/classic-alarms/readme.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.