# Emergency Scenarios
Emergency scenarios are pre-configured emergency responses that admins can activate from Verkada Command, the Verkada Pass App, or a physical input. Each scenario defines which doors lock, which doors unlock, and who is notified, so when something happens, the right actions take effect immediately.
Verkada's five scenario types, **Lockdown, Hold, Secure, Evacuate, and Shelter**, are based on the [Standard Response Protocol](https://iloveuguys.org/The-Standard-Response-Protocol.html) developed by the I Love U Guys Foundation, a common framework used by schools, workplaces, and public buildings to standardize emergency response.
{% hint style="danger" %}
You must be an [Access Site Admin](/access-control/getting-started/roles-and-permissions-for-access-control.md) to create a scenario for a site.
{% endhint %}
***
## Create a scenario
{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Access.**
{% endstep %}
{% step %}
**Select a site from the All Sites menu.**
{% endstep %}
{% step %}
**Click Scenarios, then on the right, click** :plus:.
{% endstep %}
{% step %}
**Under General, select a scenario type.**
The scenario type you choose determines the icon and color used to identify the scenario across Command and alerts. It has no bearing on the configuration options available in the next steps. All types share the same configuration options.
{% endstep %}
{% step %}
**Provide a name for the scenario and, optionally, an emergency message.**
{% endstep %}
{% step %}
**Under Sites and Doors, select doors from the site(s) that will lock and/or unlock when the scenario is activated.**
Scenarios can be configured with no doors at all. This is useful when you want to use Command to trigger an emergency to generate alerts and notify admins without changing the state of any doors.
{% endstep %}
{% step %}
**Under Permissions, specify who can activate the scenario, release the scenario, or unlock doors during the scenario.**
The "Can Unlock Doors" permission only appears if at least one door in the scenario is configured to lock.
{% endstep %}
{% endstepper %}
{% hint style="warning" %}
If multiple sites are assigned to a lockdown scenario:
* If a user is not an [Access Site Admin](/access-control/getting-started/roles-and-permissions-for-access-control.md) for all the sites in the scenario, they can only add or remove doors from the sites where they have admin permissions.
* If an [AUX input](/access-control/configuration/configure-the-ax11-io-controller/configure-an-aux-output-on-an-access-controller.md) is configured to trigger the lockdown scenario, a user must be an [Access Site Admin](/access-control/getting-started/roles-and-permissions-for-access-control.md) for **all** assigned sites to edit or delete the AUX input configuration.
{% endhint %}
***
## Clone a scenario
{% stepper %}
{% step %}
**In Command, go to All Products > Access.**
{% endstep %}
{% step %}
**Select a site from the All Sites menu.**
{% endstep %}
{% step %}
**Click Scenarios, then select a scenario.**
{% endstep %}
{% step %}
**At the top right, click** > **Clone.**
{% endstep %}
{% step %}
**Select a site to clone to and click Next.**
{% endstep %}
{% step %}
**Follow the configuration window to configure the scenario and make changes.**
{% endstep %}
{% endstepper %}
***
## Activate a scenario
Once a scenario has been created, you will see a new **emergency** 
icon at the bottom-left of your navigation bar.
{% stepper %}
{% step %}
**On the Command homepage, left navigation, click** **Active Scenario.**
{% endstep %}
{% step %}
**Select the scenario to initiate.**
{% endstep %}
{% step %}
**Click Activate to start the scenario.**
{% endstep %}
{% endstepper %}
{% hint style="danger" %}
More than one scenario can be active at the same site at any given time, regardless of scenario type. When multiple scenarios are active and a door is configured across more than one of them, **the** **lock state takes precedence on a per-door basis**. If one active scenario tells a door to lock and another tells the same door to unlock, the door will lock. When the scenario locking the door is released, the door will switch to unlocked, provided the other scenario is still active.
{% endhint %}
{% hint style="info" %}
Scenarios can also be activated from the [Verkada Pass App](/access-control/users-and-credentials/verkada-pass-app.md), the Command mobile app, an AUX input, or the [Scenarios API](/access-control/integrations-and-alerts/manage-doors-via-api/manage-lockdowns-and-scenarios-via-api.md).
{% endhint %}
***
## Configure an AUX input to initiate a scenario locally
Once a scenario has been created, you can configure an AUX input on an access controller to trigger the scenario when the AUX input is activated.
{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Access.**
{% endstep %}
{% step %}
**Under Controllers, select the access controller where you want to set up an AUX input.**
{% endstep %}
{% step %}
**From the access controller’s details page, click Add and select AUX Input.**
{% endstep %}
{% step %}
**Under Settings:**
a. Enter a unique name.\
b. Select the desired name, port, and connection type.\
c. Click **Next**.
{% endstep %}
{% step %}
**Under Actions:**
a. Select **Scenario Trigger** as the **Input Type**.\
b. Select the **Scenario** that you want to trigger when the AUX input is activated.
{% endstep %}
{% step %}
**Click Done.**
{% endstep %}
{% endstepper %}
{% hint style="warning" %}
If an AUX input is configured to trigger a scenario that includes doors on other access controllers, the AUX input’s access controller will establish a local connection with the other access controllers through the local area network (LAN).\
\
When the AUX input is activated, each door in the scenario will lock or unlock according to its configuration, through the local network. For more details, see [Cross-Device Local Connection 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).
{% endhint %}
***
## View active scenarios
Admins can access active scenarios from the alerts inbox in Command to always know what is happening across the site.
{% stepper %}
{% step %}
**When a scenario is activated, a notification card slides out from the Alerts icon.**
The alert inbox icon turns red, pulses, and displays the number of active emergencies while at least one scenario is active.
{% hint style="danger" %}
Dismissing or hiding a notification card does not release the scenario. Users can dismiss cards individually or hide all visible cards at once.
{% endhint %}
{% endstep %}
{% step %}
**On the Command homepage, left navigation, click Alerts.**
{% endstep %}
{% step %}
**On the left, select Active Emergencies.**
The Active Emergencies tab lists all active scenarios alongside any unresolved, raised alarms. This view is the source of truth for what's currently active across your sites.
{% endstep %}
{% step %}
**Select a scenario to view more information.**
{% endstep %}
{% endstepper %}
***
## Release a scenario
{% stepper %}
{% step %}
**On the Command homepage, left navigation, click Alerts.**
{% endstep %}
{% step %}
**On the left, select Active Emergencies.**
{% endstep %}
{% step %}
**Select a scenario, and on the right, click Release.**
{% endstep %}
{% step %}
**Click Confirm to release.**
{% endstep %}
{% endstepper %}
{% hint style="info" %}
Scenarios can also be released from the [Verkada Pass App](/access-control/users-and-credentials/verkada-pass-app.md), the Command mobile app, or the [Scenarios API](/access-control/integrations-and-alerts/manage-doors-via-api/manage-lockdowns-and-scenarios-via-api.md).
{% endhint %}
---
# Agent Instructions: 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/access-control/integrations-and-alerts/configure-access-control-event-alerts/emergency-lockdown.md?ask=
```
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.