> 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/incident-response-portal.md).

# Incident Response Portal

The Incident Response portal is a web page where employees can account for evacuees during an active Response. Any Workplace employee can access the Incident Response portal to interact with active responses at their site.

***

## Incident Response portal

When a Response is launched in **Incident** or **Drill mode** with employee notifications enabled, all Workplace employees at the site receive a magic link via email and/or SMS to access the Incident Response portal. Employees can also log in at any time at [unite.my.verkada.com](https://unite.my.verkada.com).

***

## People Status page

You can search evacuees by name and view or update their status and location. To update an evacuee’s status or location:

{% stepper %}
{% step %}
**Log in to** [**unite.my.verkada.com**](https://unite.my.verkada.com)**.**
{% endstep %}

{% step %}
**(Optional) Apply** [**filters**](#h_457b70e469)**.**
{% endstep %}

{% step %}
**Select an evacuee.**

a. Select a **Status**.\
b. Select a **Location**.\
c. Click **Save**.

<div align="left" data-with-frame="true"><img src="/files/ePGXWFKVHX80dlpXZqZT" alt="" width="188"></div>
{% endstep %}
{% endstepper %}

### Filters

Workplace Employees can use the search bar and filters on the People Status page to find specific evacuees. Filters include:

{% stepper %}
{% step %}
**Evacuee status**
{% endstep %}

{% step %}
**Evacuee location**
{% endstep %}

{% step %}
**Teacher & Section (for K12 customers with an SIS integration)**
{% endstep %}

{% step %}
**Edited by me**
{% endstep %}
{% endstepper %}

***

## Sign in Guardians page

Employees will see the **Sign in Guardians** page for Response Templates with [Reunification enabled](/incident-response/configuration/create-response-templates.md). From here, employees can sign in and review guardians:

{% stepper %}
{% step %}
**Log in to** [**unite.my.verkada.com**](https://unite.my.verkada.com)**.**
{% endstep %}

{% step %}
**Select the Sign in Guardians page.**
{% endstep %}

{% step %}
**Select your location.**
{% endstep %}

{% step %}
**At the bottom, select Sign in a guardian.**
{% endstep %}

{% step %}
**Fill out the** [**form**](https://app.intercom.com/a/apps/q5re5q6g/knowledge-hub/all-content?activeContentId=13666171\&activeContentType=article\&editorMode=view\&search=guardian%20form) **on behalf of the guardian.**

<div align="left" data-with-frame="true"><img src="/files/aG3zXAq3xLmZRxomxIxf" alt="" width="375"></div>
{% endstep %}
{% endstepper %}

By default, the **Sign in Guardians** page shows all waiting guardians. Employees can filter to view:

* All guardians checked in during the Response
* Denied guardians
* Reunified guardians

By selecting a guardian, employees can view the student(s) they requested to release and the employee who checked them in.

***

## Reunify Students and Guardians

Employees will see the **Reunify Students + Guardians** page for Response Templates with [Reunification enabled](/incident-response/configuration/create-response-templates.md). By default, this page displays all student/guardian pairings where:

{% stepper %}
{% step %}
**The student’s status is not unknown and not reunified.**
{% endstep %}

{% step %}
**The guardian is signed in and fully approved (e.g., passed security screening or temporary guardian exception)**
{% endstep %}
{% endstepper %}

Employees can use location and status filters to refine which pairings appear. Filters only affect the individual’s view and do not impact what other employees see. The location filter applies to both guardians and students.


---

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