> 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/alarm-admin-contact-requirement.md).

# Alarm Admin Contact Requirement

Each alarm site must designate an Alarm Admin Contact. This ensures Verkada has a single, accountable point of contact for maintaining alarm-site configuration and system health. This does not change the functionality of the alarm system.

Verkada may occasionally detect misconfigurations or settings that need attention to keep an alarm system functioning correctly. Having a designated Admin Contact ensures Verkada knows exactly who to contact to resolve issues quickly.

***

## Configuration

### Existing alarm site

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

{% step %}
**Select your Alarm site.**
{% endstep %}

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

{% step %}
**Under Site Address and Dispatch Info > Alarm Admin Contact, enter the user's name and select it from the list.**

{% hint style="warning" %}
You can select a user with any permission level as the Alarm Admin Contact, but we strongly recommend choosing a **Site Admin** to ensure they have full access to alarm configuration when contacted about an issue.\
\
See [Roles and Permissions for New Alarms](/new-alarms/getting-started/roles-and-permissions-for-new-alarms.md) for more information.
{% endhint %}
{% endstep %}
{% endstepper %}

### New alarm site

For new Alarms sites, you need to configure an Alarm Admin Contact during the alarm site creation flow.

{% hint style="warning" %}
See [Alarm Sites](/new-alarms/configuration/alarm-sites.md) for more information.
{% 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.verkada.com/new-alarms/alarm-specifications/alarm-admin-contact-requirement.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.