# Roles and Permissions for Gateway

This article describes the set of roles and associated permissions for Verkada [Gateways](https://www.verkada.com/docs/?product=connectivity\&search=gateway). 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.

***

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

***

## Site-level roles

<details>

<summary>No Access</summary>

A No Access user cannot view gateways within a site.

</details>

<details>

<summary>Live-Only Viewer</summary>

A Live-Only Viewer user cannot view gateways within a site.

</details>

<details>

<summary>Site Viewer</summary>

Site Viewers can:

* Access Gateway Home page
* Access Gateway Details Page
* Run Speed test
* View connected devices
* View historical power usage
* View Activity logs
* View data graphs
* Set up alerts

</details>

<details>

<summary>Site Admin</summary>

Site Admins can do everything Site Viewers can as well as:

* Claim Device
* Setup Device
* Manage Device
* Delete Device
* Manage data License
* Access Gateway Home page
* Access Gateway Details Page
* Run Speed test
* Run Packet capture
* View connected devices
* Power cycle ports
* View historical power usage
* Switch to WAN mode
* View Activity logs
* Claim connected devices
* Change network settings
* Toggle smart data usage
* View data graphs
* Identify Device
* Reboot Device
* Set up alerts

</details>

***

## Org-level roles

<details>

<summary>Org Admin</summary>

Org Admins can:

* Claim SW License
* Claim data License

</details>

***

## Set permissions

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

{% hint style="danger" %}
You will have access to all cameras, viewing stations, air quality sensors, intercoms, gateways, New Alarms, and Command Connectors once you have been granted permissions for a site.
{% endhint %}

<details>

<summary>Users</summary>

1. In Verkada Command, go to **All Products > Admin**.
2. Under **Org Settings > Users & Permissions**, select **Users**.
3. Select a user.
4. At the top right, click **Manage Roles**.
   1. Set the needed permissions.
   2. Click **Save**.

</details>

<details>

<summary>Groups</summary>

1. In Verkada Command, go to **All Products > Admin**.
2. Under **Org Settings > Users & Permissions**, select **Groups**.
3. Select a group.
4. At the top, select **Site Roles > Manage Roles**.
   1. Set the needed permissions.
   2. Click **Save**.

</details>

<details>

<summary>Sites</summary>

1. In Verkada Command, go to **All Products > Admin**.
2. In the left navigation, select **Sites**.
3. At the top left, click **Manage Sites**.
4. Select a site to manage and in the right pane, click **Manage**.
   1. In the top right, click **Add** to add a new user or group.
   2. Select an existing user or group to edit their permissions.

</details>


---

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