> 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/air-quality/getting-started/roles-and-permissions-for-air-quality-sensors.md).
# Roles and Permissions for Air Quality Sensors
This article describes the set of roles and associated permissions for Verkada [Air Quality Sensors](https://docs.verkada.com/docs/air-quality-sensors-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.
***
### 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
No Access
A No Access user **cannot** view air quality devices within a site.
Live-Only Viewer
A Live-Only Viewer user **cannot** view air quality devices within a site.
Site Viewer
* 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
Site Admin
For each category below, Site Admins can perform specific actions.
**Air Quality Sensors Home**
* Add/remove devices.
* Move devices between sites.
* Set up (enable/disable) and edit triggers and their sensitivity values.
* Reboot a device.
* Set up offline notifications for the sensors in the sites they have access to.
* Link a camera as a context camera to monitor events.
**Note:** You must be a Site Admin for the site the camera is in.
* Download a (comma-separated value) CSV file of the sensor data for any of the readings.
* Enable live audio and recorded audio (for [SV25](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf)s that support audio recording and have this feature enabled).
**Dashboards**
* Pair dashboards with a display.
* Share the dashboard with other users.
* Delete dashboards.
* Edit tiles to view a time-series line graph.
* Display sensor readings only.
* View a single aggregated metric, a gauge, or a list of the readings’ values.
* Delete tiles on the dashboard.
* Choose the sensor to view on the dashboard.
* Choose which sensor readings to display on each tile (for example, Temp/Vape Index/Humidity, and so on).
* Choose the timescale (3 hrs or 24 hrs \[only two options available]).
* Adjust the thresholds for each of the selected values to set their own ranges for good, fair, and bad values.
**Analytics**
* View the values and the sites where the Site Admin has access.
* Sort filters to view specific readings, such as Temp/Vape Index/Humidity, and duration (weekly, daily, monthly).
* Toggle between sites where the Site Admin has access.
## Org-level roles
Org Admin
{% hint style="danger" %}
The Org Admin must also be a Site Admin for the sites where the sensors are located.
{% endhint %}
* Create and edit dashboards.
* Enable/disable features for sensors (sensor audio, BACnet, calibration).
* **Only role** that can calibrate sensors.
* **Only role** that can create, edit, and remove dashboards.
***
## Set permissions
You can set site permissions for existing users and groups by managing user roles, groups, or sites.
{% hint style="danger" %}
Command site roles grant varying levels of access to cameras, viewing stations, air quality sensors, intercoms, gateways, and Command Connectors in a site and its subsites.
{% endhint %}
Users
{% 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 **Command** as the product line.
2. Select the role to grant to the user.
3. Click **Save**.
{% endstep %}
{% endstepper %}
Groups
{% 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 **Command** as the product line.
2. Select the role to grant to the group.
3. Click **Save**.
{% endstep %}
{% endstepper %}
Sites
{% 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 :pen-line:.
2. In the top right, click :plus-large: > **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 %}
---
# 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/air-quality/getting-started/roles-and-permissions-for-air-quality-sensors.md?ask=
```
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.