> 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/new-alarms/alarm-specifications/verkada-new-alarms-monitoring-certificate.md).

# Verkada New Alarms Monitoring Certificate

Obtain a certificate that your New Alarm site is monitored

{% hint style="success" %}
This article is a guide for New Alarms. Refer to this [article](broken://pages/cjWSjS6etKtCnsdOkwNn) if you have classic Alarms. See [New Alarms vs Classic Alarms](/new-alarms/getting-started/new-alarms-vs-classic-alarms.md) if you are unsure which version of Alarms you have.
{% endhint %}

An Alarm Monitoring Certificate confirms that Verkada professionally monitors your alarm system and serves as proof for your insurance provider.

***

## Obtain the certificate

{% stepper %}
{% step %}
**In Verkada Command, go to All Products > New Alarms.**
{% endstep %}

{% step %}
[**Create an Alarm site**](/new-alarms/configuration/alarm-sites.md) **or select the alarm site that you want to configure.**
{% endstep %}

{% step %}
**In the left navigation, select Settings.**
{% endstep %}

{% step %}
**Under Site Address and Dispatch info, click Alarm Certificate.**

<div align="left" data-with-frame="true"><img src="https://2259276529-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNU1He6Uj2tgInV2VdCLQ%2Fuploads%2Fgit-blob-522c79dc21415d61a52c95085127213ef3c3ecc8%2F46f1c504b77dea48026d70f91e2cd30592c7903f.png?alt=media" alt="" width="1309"></div>
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
The certificate will include the business name, site address, date of download, and a license number based on the site’s address.
{% endhint %}


---

# 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/new-alarms/alarm-specifications/verkada-new-alarms-monitoring-certificate.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.