> 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/getting-started/roles-and-permissions-for-new-alarms.md).

# Roles and Permissions for New Alarms

{% hint style="success" %}
This article is a guide for New Alarms. Refer to this [article](/classic-alarms/getting-started/roles-and-permissions-for-classic-alarms.md) if you have classic Alarms. See [New Alarms vs Classic Alarms](/new-alarms/getting-started/new-alarms-vs-classic-alarms.md) if you are unsure which version of Alarms you have.
{% endhint %}

This article describes the set of roles and associated permissions for Verkada Alarms. For more information on roles and permissions for other Verkada product lines, see [Roles and Permissions for Command](/command/users-and-permissions/roles-and-permissions-for-command.md).

* **Site-level roles** determine the access a user or group has to devices in the site.
* **Permissions** are set using roles, which define the level of access users and groups have to devices and settings within an organization and its sites.

***

### Permissions considerations

* Subsites inherit permissions from all parent sites, including the ultimate parent.
* Users can belong to multiple groups. When roles conflict, the user receives the **highest role** granted directly or through any group.
* Group-assigned roles can be manually upgraded but not downgraded. Remove the user from the group with the higher role to downgrade their access.

***

## New Alarms roles

#### Arm / Disarm

Users with this role can arm and disarm the site and resolve alarms through Command (web or mobile). They cannot access the alarm site configuration or other products unless explicitly granted permission.

{% hint style="info" %}
This role is suited for users such as guards, cleaning staff, or contractors who need basic permissions to arm or disarm the alarm system without broader site or product access.
{% endhint %}

#### Unassigned

This is the default role for users without an assigned New Alarms role. Users with this role cannot arm and disarm, access the alarm site configuration, or access other products.

***

## Site-level roles

<details>

<summary>No Access</summary>

* Cannot view the alarm site.
* If added as a **response contact** for the alarm site, they can resolve an alarm and disarm the site through the incident link and agent call.

</details>

<details>

<summary>Site Viewer</summary>

* Cannot create or edit an alarm site.
* Cannot arm or disarm alarm sites or resolve an alarm via Command.
* Can view all alarm activity and event history with historical footage and live streams.
* If added as a **response contact** for the alarm site, they can resolve an alarm and disarm the site through the incident link and agent call.

</details>

<details>

<summary>Site Admin</summary>

* Can create or edit an alarm site.
* Can create and edit keycodes along with all other alarm configurations.
* Can arm or disarm alarm sites or resolve an alarm via Command.
* Can add or remove Verkada devices and wired inputs/outputs on the site.
* Can view all alarm activity and event history with historical video.
* If added as a **response contact** for the alarm site, they can resolve an alarm and disarm the site through the incident link and agent call.

</details>

{% hint style="warning" %}
If a user is granted a **keycode** to the alarm site, they can arm or disarm the site and resolve an alarm via the keypad.
{% endhint %}

***

## Set permissions

You can set site permissions for existing users and groups by managing user roles, groups, or sites.

<details>

<summary>Users</summary>

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

{% step %}
**Under Org Settings > Users & Permissions, select Users.**
{% endstep %}

{% step %}
**Select a user.**
{% endstep %}

{% step %}
**To the right of Site Roles, click Manage.**

1. In the top left, select **Alarm** as the product line.
2. Select the role to grant to the user.
3. Click **Save**.
   {% endstep %}
   {% endstepper %}

</details>

<details>

<summary>Groups</summary>

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

{% step %}
**Under Org Settings > Users & Permissions, select Groups.**
{% endstep %}

{% step %}
**Select a group.**
{% endstep %}

{% step %}
**To the right of Site Roles, click Manage.**

1. In the top left, select **Alarm** as the product line.
2. Select the role to grant to the group.
3. Click **Save**.
   {% endstep %}
   {% endstepper %}

</details>

<details>

<summary>Sites</summary>

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

{% step %}
**In the left navigation, select Sites.**
{% endstep %}

{% step %}
**Select a site to manage.**

1. In the right pane, next to **Site Permissions**, click <i class="fa-pen-line">:pen-line:</i>.
2. In the top right, click <i class="fa-plus-large">:plus-large:</i> > **User** or **Group.**
3. Select user(s) or group(s) to edit their permissions, then click **Next.**
4. Edit the permissions as needed.
5. Click **Add.**
   {% endstep %}
   {% endstepper %}

</details>

***

### Common Alarm permission configurations

|                                                                                                                                                                                                         |                          |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------ |
| **Scenario**                                                                                                                                                                                            | **Role Configuration**   |
| <p>User requires full administrative control of the alarm site.</p><p><br>​For example, a Security Director, Facilities Manager.</p>                                                                    | Site Admin               |
| <p>User can view alarm incidents for investigation and arm or disarm the system through Command (web or mobile), but cannot modify the site configuration.<br>​<br>​For example, a SOC team member.</p> | Site Viewer + Arm/Disarm |
| <p>User can only arm and disarm the site through Command (web or mobile) and has no access to the alarm site or other products within it.</p><p>For example, a guard, janitor, or contractor.</p>       | No access + Arm/Disarm   |


---

# 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, and the optional `goal` query parameter:

```
GET https://help.verkada.com/new-alarms/getting-started/roles-and-permissions-for-new-alarms.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.