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

# Roles and Permissions for Classic Alarms

{% hint style="success" %}
This article is a guide for classic Alarms. Refer to this [article](/new-alarms/getting-started/roles-and-permissions-for-new-alarms.md) if you have new 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 Classic Alarms](https://docs.verkada.com/docs/alarms-professional-monitoring-overview.pdf). 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.
* **Org-level roles** allow users or groups to manage permissions and devices at a global level.
* **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.

***

## Site-level roles

<details>

<summary>No Access</summary>

* By default, cannot arm/disarm Alarm sites.
* Unable to view any details about Alarm sites in Command.
* When explicitly granted alarm user permissions, can arm/disarm an Alarm site in Command and from the Alarms mobile app.

</details>

<details>

<summary>Live-Only Viewer</summary>

* By default, cannot arm/disarm Alarm sites.
* When explicitly granted alarm user permissions, can arm/disarm an Alarm site in Command and from the Alarms mobile app.
* If Arm/Disarm Geofencing is enabled, the user will only be able to arm/disarm sites from the Verkada Alarms Mobile App.
* See live video and new events on the Alarm site page.

</details>

<details>

<summary>Site Viewer</summary>

* By default, cannot arm/disarm Alarm sites.
* When explicitly granted alarm user permissions, can arm/disarm an Alarm site in Command and from the Alarms mobile app.
* If Arm/Disarm Geofencing is enabled, the user will only be able to arm/disarm sites from the Verkada Alarms Mobile App.
* View all alarm activity and event history with historical footage.
* Listen in and initiate talk-downs to the alarm console.

</details>

<details>

<summary>Site Admin</summary>

* By default, can arm/disarm sites via Command and the Alarms mobile app. You can find the arm/disarm capability in the user settings profile (**Site Access** > **Alarm User** checkbox).
* Update all site settings, including trigger events and alarm response notifications/actions, via the Command and Alarms mobile apps.
* Add or remove Verkada devices and wired inputs/outputs on the site.
* View all alarm activity and event history with historical video.
* Listen in and initiate talk-downs to the alarm console.

{% hint style="danger" %}
You also need Org Admin permissions to generate key codes.
{% endhint %}

</details>

## Org-level roles

<details>

<summary>Org Admin</summary>

* Can generate user key codes.
* By default, can arm/disarm sites via Command and the Alarms mobile app. You can find the arm/disarm capability in the user settings profile (**Site Access** > **Alarm User** checkbox).
* Set up new alarm sites and change all site settings, including trigger events and alarm response notifications/actions via Command and the Alarms mobile app.
* Add or remove Verkada devices and wired inputs/outputs on the site.
* View all alarm activity and event history with historical video.
* Listen in and initiate talk-downs to the alarm console.

</details>

***

## Set permissions

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

<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 **Classic 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 **Classic Alarm** as the product line.
2. Select the role to grant to the group.
3. Click **Save**.
   {% endstep %}
   {% endstepper %}

</details>


---

# 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/classic-alarms/getting-started/roles-and-permissions-for-classic-alarms.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.