> 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/configuration/configure-doors-as-alarm-triggers.md).
# Configure Doors as Alarm Triggers
Configure and manage access control doors as triggers in New Alarms
To use access control doors as triggers, they must be in the same site as the alarm system and equipped with door position indicators (DPIs).\
\
The Access controller and the BP52 alarms panel will communicate locally if used in conjunction with each other. See [Cross-Device Local Connections for Access Control](/access-control/integrations-and-alerts/create-a-person-of-interest-from-an-access-user/cross-device-local-connections-for-access-control.md) for more information.
***
## Add doors to an alarm site
{% stepper %}
{% step %}
**In Verkada Command, go to All Products > New Alarms.**
{% endstep %}
{% step %}
**Select the alarm site that you want to configure.**
{% endstep %}
{% step %}
**In the left navigation, select Devices.**
{% endstep %}
{% step %}
**In the top right, click Configure > Configure access control doors.**
a. Select the door(s) to add and click **Continue.**\
b. Select the events that will raise an alarm and click **Continue.**\
c. Select the partition for the doors and click **Continue.**
{% endstep %}
{% endstepper %}
{% hint style="warning" %}
Doors without DPIs or doors already added to the site will automatically be hidden.
{% endhint %}
***
## Manage doors on an alarm site
{% stepper %}
{% step %}
**In Verkada Command, go to All Products > New Alarms.**
{% endstep %}
{% step %}
**Select your alarm site.**
{% endstep %}
{% step %}
**In the left navigation, select Devices > your door.**
1. Under **Device Details:**
* Click the checkbox next to the door events you want to trigger the alarm. You can select **Door Forced Open, Door Opened,** and **Door Held Open.**
{% hint style="danger" %}
The DHO (Door Held Open) threshold for an access door must be configured on the access controller's door settings page.
{% endhint %}
* Under **Nearby Camera,** click **Pair Nearby Camera** to add a camera as a context camera.
* Toggle on **Video verification.**
* Under **Device Muting**, select **Mute device for**, then choose the duration.
{% hint style="warning" %}
While muted, this device will not trigger any alarms, but its signals will still be recorded.
{% endhint %}
2. Under **Activity,** you can view the door event history.
{% endstep %}
{% endstepper %}
---
# 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/configuration/configure-doors-as-alarm-triggers.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.
