> 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/incident-response/getting-started/get-started-with-incident-response.md).

# Get Started with Incident Response

Learn about the Incident Response offering from Verkada Workplace

Incident Response helps organizations track the well-being and location of people during an incident. It enables organizations to account for employees and visitors, and allows schools to reunite students with their guardians.

{% hint style="danger" %}
Incident Response is only available in sites with Verkada Guest.
{% endhint %}

***

## Set up Incident Response

{% hint style="danger" %}
You need **Org Admin** permissions to configure Incident Response.
{% endhint %}

### Initial site

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

{% step %}
**Click Import Existing Guest Sites.**
{% endstep %}

{% step %}
**Select your site > Import Site.**
{% endstep %}
{% endstepper %}

### Additional sites

After setting up the first Workplace site for Incident Response, you can configure additional sites.

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

{% step %}
**On the left navigation, click Incident Response Settings.**
{% endstep %}

{% step %}
**At the top, select Organization > Sites.**
{% endstep %}

{% step %}
**Click Import Site.**
{% endstep %}
{% endstepper %}

***

## Response templates

Workplace Site Admins can create Response Templates for different types of incidents. A Response Template defines:

* Who needs to be accounted for as evacuees
* What statuses can be assigned to evacuees
* Where evacuees can be marked as present

For schools, configure the Response Template for Reunification and set up a Guardian Form.

{% hint style="warning" %}
See [Create Response Templates](/incident-response/configuration/create-response-templates.md) for more information.
{% endhint %}

***

## Workplace Employees

Employees assigned to an Incident Response site can take part in any active Response at that site. Employees are shared across all Workplace products (Guest, Mailroom, and Incident Response) for that site.

{% hint style="danger" %}

* You need **Workplace Site Admin** permissions to manage site-level employee lists.
* You need **Org Admin** permissions to manage the organization-level employee list.
  {% endhint %}

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

{% step %}
**On the left navigation, click Incident Response Settings.**
{% endstep %}

{% step %}
**At the top, select Site > Employees.**
{% endstep %}

{% step %}
**Select Manage Employee List.**
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
See [Manage Host Lists in Guest](/guest/configuration/manage-host-lists-in-guest.md) for more information.
{% endhint %}

***

## Launch a Response

{% hint style="danger" %}
You must have the **Workplace Site Admin** role or[ explicit permissions](/command/users-and-permissions/roles-and-permissions-for-command/custom-roles.md#workplace) to launch a Response from Command.
{% endhint %}

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

{% step %}
**On the Incident Response Home, click Launch Response.**
{% endstep %}

{% step %}
**Select a Response Template.**

{% hint style="warning" %}
At the beginning of a Response, all evacuees have **Unknown** status and location.
{% endhint %}
{% endstep %}

{% step %}
**Click Launch.**

When a real Response is launched, all employees will receive notifications with magic links to the [Incident Response portal](/incident-response/getting-started/incident-response-portal.md).

<div align="left" data-with-frame="true"><img src="https://3922624211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fn49pz7ZddUdVxNdz2EFE%2Fuploads%2Fgit-blob-80eb931955c613ccbd9286b6a1cc67c55f4d3a9d%2F7a71e02311aa5330d387458c32ea839bfb9f90f4.png?alt=media" alt="" width="188"></div>
{% endstep %}
{% endstepper %}

***

## End a Response

{% hint style="danger" %}
You must have the **Workplace Site Admin** role or[ explicit permissions](/command/users-and-permissions/roles-and-permissions-for-command/custom-roles.md#workplace) to end a Response.&#x20;
{% endhint %}

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

{% step %}
**On the Incident Response Home, click Active Response.**

<div align="left" data-with-frame="true"><img src="https://3922624211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fn49pz7ZddUdVxNdz2EFE%2Fuploads%2Fgit-blob-08d26370f24e2030d89ddf46cecca217fe977375%2F71fbc94f4fb1839db5b4d5618af5f6c415d8d453.png?alt=media" alt="" width="375"></div>
{% endstep %}

{% step %}
**In the top right, click End.**
{% endstep %}

{% step %}
**In the confirmation menu, select End Incident.**
{% endstep %}
{% endstepper %}

Ending a Response locks further changes on the Incident Response portal. For real Responses and drills with notifications enabled, all employees are notified when the Response ends.


---

# 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/incident-response/getting-started/get-started-with-incident-response.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.
