# Roles and Permissions

This article describes the set of roles and associated permissions for Verkada Command.

{% hint style="info" %}
As of April 16, 2026, Command organizes roles by scope first (organization, user management, site) and then by product area within each scope. This replaces the previous model that grouped roles primarily by product. See roles and permissions in each product area for more information.
{% endhint %}

### Roles and permissions by Verkada product

All users added to the organization can log in to Command, but need additional permissions to view all the products. Select a product from the list below for more information on its roles and permissions.

* [Roles and Permissions for Access Control](/access-control/getting-started/roles-and-permissions-for-access-control.md)
* [Roles and Permissions for Air Quality Sensors](/air-quality/getting-started/roles-and-permissions-for-air-quality-sensors.md)
* [Roles and Permissions for Alarms](/new-alarms/getting-started/roles-and-permissions-for-new-alarms.md)
* [Roles and Permissions for Classic Alarms](/classic-alarms/getting-started/roles-and-permissions-for-classic-alarms.md)
* [Roles and Permissions for Cameras](/verkada-cameras/getting-started/roles-and-permissions-for-cameras.md)
* [Roles and Permissions for Intercom](/intercom/getting-started/roles-and-permissions-for-intercom.md)
* [Roles and Permissions for Gateway](/connectivity/getting-started/roles-and-permissions-for-gateway.md)
* [Roles and Permissions for Guest](/guest/getting-started/roles-and-permissions-for-guest.md)
* [Roles and Permissions for Mailroom](/mailroom/getting-started/roles-and-permissions-for-mailroom.md)

***

## Organization-level roles

Organization roles apply across the entire Command organization and are not tied to a specific site. They control broad platform access, such as organization-wide settings, Access Control at the organization level, alerts, operations, and similar areas.

<details>

<summary>Organization Admin</summary>

Any organization member can be upgraded to an Organization Admin.

Access allows you to:

* View the organization when logged in.
* Configure personal notifications (which alerts the user wants to receive).
* Set personal and org-wide 2FA settings.
* Create floor plans.
* Add, delete, and modify access users.
* Set user and group permissions for the organization and all sites/subsites.
* Configure org-wide settings, including maximum archive duration, enable/disable cloud backup globally, and default camera playback quality.
* Rename or delete the org.
* Create new sites and subsites.
* Add and remove devices.
* Adjust camera stream encoding settings.

{% hint style="warning" %}
If the [Global Site Admin](/command/users-and-permissions/roles-and-permissions-for-command/customize-roles-and-permissions.md) policy is enabled, all Org Admins will automatically be granted Site Admin access to all sites.
{% endhint %}

</details>

<details>

<summary>Organization member</summary>

All users added to an organization are organization members. A user added to the organization who does not have admin permissions has the minimum level of access needed to sign in to the organization.

Access allows you to:

* View the organization when logged in.
* Configure personal notifications (which alerts the user wants to receive).
* Set personal 2-Factor Authentication (2FA) settings.

</details>

## User management roles

User management roles control who can manage people and identity in Command, such as creating or editing users and groups and assigning admin-level roles, often scoped to directories or the full organization. They are separate from organization roles to distinguish who can manage devices (for example, cameras) from who can manage users.

<details>

<summary>Command User Admin</summary>

{% hint style="warning" %}
Command User Admins cannot modify the Organization Admin role. They can assign or remove Command User Admins but cannot elevate or lower Organization Admin permissions.
{% endhint %}

Any organization member can be upgraded to a Command User Admin.

Command User Admin allows you to:

* Add and remove users, designate their roles, and assign them to groups.
* Add and remove groups and assign users to groups.
* Add and remove contacts for individuals outside of your organization.
* Create and assign alerts to groups and users in the organization.
* Manage and restrict access to Shared Links for users in the organization.
* Enable Support Access.

</details>

<details>

<summary>Command User Viewer</summary>

Command User Viewer allows you to:

* View users, their roles, and their groups.
* View groups, their roles, and their users.

</details>

## Site roles

Site-level roles can be assigned to individual users or groups and apply only to a specific site. Subsites inherit permissions from parent sites above them in the hierarchy.

#### Command site roles overview

Command site roles include permissions across product suites, such as Cameras, Alarms, Sensors, Intercoms, and Gateways.

<details>

<summary>Site Admin</summary>

**Cameras**

Site Admins can access live and recorded footage for cameras within the sites for which they have permissions. They can also configure site permissions and camera settings.

Site Admins can:

* Add, remove, and manage user permissions on a site for existing users.
* Add cameras to the organization and to any site where they are a Site Admin.
* Delete cameras from the organization only from sites where they are a Site Admin.
* Create, rename, and delete sites and subsites.
* View live streams.
* Share live links (SMS and link).
* View historical video.
* Archive video and download as an MP4.
* View non-private archives. **Note:** To view non-private archives, Organization Admin permissions are also required.
* Perform motion searches.
* Take live feed snapshots.
* Configure camera settings.
* Utilize auto and manual focus.
* Utilize optical and digital zoom.
* Create camera embeds.
* View camera stats.
* Has full access to controls and features, including Sentry Mode for PTZ cameras.

**Alarms**

* 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.

**Air Quality Sensors**

* Add or remove sensors, move them between sites you administer, and reboot hardware.
* Turn triggers on or off, edit them and their sensitivity, get offline alerts for sensors on sites you can access, and link a context camera (you must be a Site Admin on that camera’s site).
* Download sensor readings as a CSV; for supported SV25 units with the feature on, use live and recorded audio.
* Pair a dashboard with a display, share it with others, or delete it; build tiles by picking sensors, readings (for example temperature, vape index, humidity), a 3 hour or 24 hour window, line charts or simpler metric views, and good, fair, or bad thresholds; remove tiles you no longer need.
* See readings across the sites you can access, filter and sort by reading type and by week, day, or month, and switch between those sites.

**Gateway**

* Open gateway details, run a speed test, and see connected devices.
* Review power history, activity logs, and data graphs.
* Set up alerts.
* Claim, set up, manage, identify, reboot, and delete devices on the site.
* Manage data licenses.
* Open the gateway home page.
* Run packet capture, power cycle ports, and switch a gateway to WAN mode.
* Claim connected devices, change network settings, and toggle smart data usage.

**Intercom**

* Receive calls with video.
* See 24/7 live intercom video, even if not on an active call.
* View historical video and events.
* Unlock the door both during and outside of a call.
* Unlock the door 24/7.
* Talk down to the intercom.
* Change Receivers and device settings.

</details>

<details>

<summary>Site Viewer</summary>

**Cameras**

A Site Viewer can access live and recorded footage for cameras in the site.

Site Viewers can:

* View live streams.
* Utilize digital zoom.
* View historical video.
* Perform motion searches.
* View camera settings.
* View camera stats.
* Take live feed snapshots.
* Archive and download video (non-private archives only).
* For PTZ cameras, a Site Viewer has full access to controls but limited access to features and settings.
  * Can view existing settings.
  * Cannot enable, disable, or edit Sentry Mode settings.

**Alarms**

* 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.

**Air Quality Sensors**

* View the sensors in the site
* View analytics values for the sensors in the site
* Toggle between different durations (live, today, this week, etc.)
* View dashboards

**Gateway**

* Open gateway details, run a speed test, and see connected devices.
* Review power history, activity logs, and data graphs.
* Set up alerts.

**Intercom**

* Receive calls with video.
* See 24/7 live intercom video, even if not on an active call.
* View historical video and events.

</details>

<details>

<summary>Live-Only Viewer</summary>

**Cameras**

Live-Only Viewers can **only** view live streams (no access to historical video) of the cameras in the site.

Live-Only Viewers can:

* View individual camera live streams.
* Utilize digital zoom.
* Create and view grids.
* View floor plans.
* Has no access to controls or Sentry Mode for PTZ cameras.

**Alarms**

* 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.

**Intercom**

* Receive calls with video.
* See 24/7 live intercom video, even if not on an active call.

</details>

{% hint style="warning" %}
See [Roles and permissions by Verkada product](#roles-and-permissions-by-verkada-product) for detailed site role and permissions information for specific products accessible from Command.
{% endhint %}

***

## Set permissions

<details>

<summary>Users</summary>

#### Grant permissions

1. In Verkada Command, go to **All Products > Admin.**
2. Select **Users & Permissions** > **Users.**
3. Select a user to grant permissions.
4. Click **Manage** to the right of Organization Roles, User Management Roles, or Site Roles.&#x20;
   1. For site roles, select the relevant product.
   2. Select the role to grant to the user.
   3. Click **Save**.&#x20;

#### Revoke permissions

1. In Verkada Command, go to **All Products > Admin.**
2. Select **Users & Permissions** > **Users.**
3. Select a user to revoke permissions.
4. Click **Manage** to the right of Organization Roles, User Management Roles, or Site Roles.&#x20;
   1. For site roles, select the relevant product.
   2. De-select the role to remove from the user.
   3. Click **Save**.&#x20;

</details>

<details>

<summary>For groups</summary>

#### **Granting permissions**

1. In Verkada Command, go to **All Products > Admin.**
2. Select **Users & Permissions** > **Groups.**
3. Select a Command group to grant permissions.
4. At the top, click **Roles.**
5. Click **Manage** to the right of Organization Roles, User Management Roles, or Site Roles.&#x20;
   1. For site roles, select the relevant product.
   2. Select the role to grant to the group.
   3. Click **Save**.

#### **Revoking permissions**

1. In Verkada Command, go to **All Products > Admin.**
2. Select **Users & Permissions** > **Groups.**
3. Select a Command group to revoke permissions.
4. At the top, click **Roles.**
5. Click **Manage** to the right of Organization Roles, User Management Roles, or Site Roles.&#x20;
   1. For site roles, select the relevant product.
   2. De-select the role to remove from the group.
   3. Click **Save**.

</details>

***

## FAQ

<details>

<summary>Why has my organization disappeared?</summary>

A user must be a member at the organization level to see the organization in the dropdown when they log in. If a user is a member of an organization, they appear on the user list that Organization Admins and Site Admins can access in Command.

If your organization disappeared, it can be due to one of these reasons:

* Your user account was removed from the organization.
* The organization was deleted.

**Troubleshoot**

* If you are the affected user, contact the Organization Admin and request to re-add you to the organization.
* If a user has reported this to you, verify they are a member of the organization.

</details>

<details>

<summary>Why are cameras missing from my organization?</summary>

Sites do not inherit users from the organization or other sites. Users who are members of the organization cannot see cameras unless they have explicitly been granted permissions to the site or sub-site where the cameras reside.

* If you are the affected user, contact the Organization Admin or Site Admin and request access to the desired sites and subsites.
* If a user has reported this to you, grant them access to the desired sites and subsites.

</details>

<details>

<summary>Why can’t I access certain features or settings, such as other users?</summary>

If you are unable to access certain features or settings, you don’t have sufficient permissions. Only Admins can access all features and settings.

Organization Admins are not automatically escalated to Site Admin for any site. This is a separate feature set. Therefore, Organization Admins do not inherently have permission to view any one particular site, but they can assign themselves the required roles to see their desired sites.

**Troubleshoot tips:**

* If you are the affected user, contact the Organization Admin or Site Admin and request that they elevate your permissions to Organization Admin or the desired site or subsite.
* If a user has reported this to you, elevate their permissions on the organization or desired site or subsite.

</details>

{% hint style="info" %}
**Prefer to see it in action?** Check out the [video tutorial](https://www.youtube.com/watch?v=7ldbcKo8u0Q).
{% 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/command/users-and-permissions/roles-and-permissions-for-command.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.
