> 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/br33-panic-button-configuration.md).

# BR33 Panic Button Configuration

Correctly setup New Alarms for your BR33 panic buttons

Panic buttons are discrete ways to raise an alarm in an emergency. You need to configure a response level and arm the partition containing panic buttons before they can trigger an alarm.

***

## Configuration

{% hint style="danger" %}
Configuring a panic button consists of three steps. You must configure all three steps to ensure your panic buttons always raise an alarm when pressed. Failure to configure all three steps correctly can result in panic buttons not raising alarms as expected.
{% endhint %}

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

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

{% step %}
**In the left navigation, click Devices.**
{% endstep %}

{% step %}
**Click your sensor to view the Device Settings.**
{% endstep %}

{% step %}
**Here, you can configure the following settings:**

* **Panic Gestures:** Choose the button press pattern that triggers a panic signal and alarm. Options include Single, Double, Triple, or Long Press.
* **Mute Device:** When enabled, the device will not trigger alarms but will continue to record signals.
* **Nearby Camera:** Select the camera to pair with the panic button for visual context.
  {% endstep %}
  {% endstepper %}

{% hint style="danger" %}
Panic buttons are not video-verified. Paired camera footage is provided for context only.
{% endhint %}

### Configure a response

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

{% step %}
**Select the Alarm site that you want to configure.**
{% endstep %}

{% step %}
**On the left navigation, select Response >.**
{% endstep %}

{% step %}
**Select one of the following responses:**

* Notification only
* Standard
* Immediate Dispatch
  {% endstep %}

{% step %}
**Add a contact**
{% endstep %}

{% step %}
**Click Save.**

<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-70d5e39487624a2147ccb9b7aa0b76cc8d21a9f5%2F5b82575ea9a25aa36fd675f55ed3f0e4f5c3eeea.png?alt=media" alt="" width="375"></div>
{% endstep %}
{% endstepper %}

### Configure an Always Armed partition

{% stepper %}
{% step %}
[**Create a new partition**](/new-alarms/configuration/alarm-sites/configure-partitions.md) **and assign an alarm response.**
{% endstep %}

{% step %}
**Add all panic buttons to the partition.**
{% endstep %}

{% step %}
**From the Arm Method dropdown, select Always Armed.**

<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-a3eb4b14caa98dd9a84e549bfafa9d3bfdb8fb24%2Ff018476b7f4b92c8a0e6f2484a4d09832b6cf38b.png?alt=media" alt="" width="563"></div>
{% endstep %}
{% endstepper %}

{% hint style="warning" %}

* Always Armed is enabled at a Partition level.
* If an alarm is triggered from an Always Armed partition, resolving it will not disarm that partition.
  {% 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/configuration/br33-panic-button-configuration.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.