> 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/sound-systems/getting-started/roles-and-permissions-for-sound-systems.md).
# Roles & Permissions for Sound Systems
Learn about roles that define a user’s Sound Systems permissions in Verkada Command
This article describes the set of roles and associated permissions for Verkada Sound Systems. 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).
***
#### 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.
Permissions for Sound Systems are set at both the organizational and site levels. There is one org-level role and three site-level roles that define a user’s permissions to view and manage Sound Systems permissions and devices:
***
### Organization-level roles
Sound Systems roles grant permissions to manage organization-wide Sound Systems settings for all sites.
{% hint style="info" %}
Organization admins automatically inherit the Audio System Admin role.
{% endhint %}
#### Role overview
Audio System Admin
{% hint style="info" %}
Audio System Admins are automatically granted Audio Site Admin for **all sites.**
{% endhint %}
A user or group with Audio System Admin can do:
* Everything an Audio Site Admin can do
* Grant other users & groups the Audio System Admin role
* Manage Soundtrack Streams and connections
* Enable or disable the organization-wide explicit filter for Soundtrack
* View your organization's audit log
* View all sites in your organization
***
### Site-level roles
| Permission | Audio Site Operator | Audio Site Manager | Audio Site Admin |
| ----------------------------------------------------------- | :-----------------: | :----------------: | :--------------: |
| View Audio Site Spaces, Zones, & Streams | ✅ | ✅ | ✅ |
| View line-inputs | ✅ | ✅ | ✅ |
| Make announcements | ✅ | ✅ | ✅ |
| Play, pause, & skip current tracks | ✅ | ✅ | ✅ |
| Adjust Space Music Volume | ✅ | ✅ | ✅ |
| Change a stream's playlist to one in the Library | ✅ | ✅ | ✅ |
| Queue a track | | ✅ | ✅ |
| Block a track | | ✅ | ✅ |
| View Space Management page | | | ✅ |
| Adjust Space Announcement Volume | | | ✅ |
| Adjust output volume trim | | | ✅ |
| Change a stream's playlist | | | ✅ |
| Add a playlist to the Library | | | ✅ |
| Create, edit, delete, & reassign line inputs | | | ✅ |
| Commission & decommission Sound Systems devices | | | ✅ |
| Grant & revoke Audio Site-level permissions for other users | | | ✅ |
#### Role overview
Audio Site Operator
A user or group with Audio Site Operator can:
* View Audio Site Spaces, Zones, & Streams
* View line inputs
* Make announcements
* Play, pause, & skip current tracks
* Adjust Space Music Volume
* Change a Stream's playlist to one in your Library
Audio Site Manager
A user or group with Audio Site Manager can:
* Do everything an Audio Site Operator can do
* Queue a track
* Block a track
Audio Site Admin
A user or group with Audio Site Admin can:
* Do everything an Audio Site Manager can do
* Create and delete Spaces
* Create and delete Zones
* Manage Sound Systems device settings
* View the Space Management page
* Adjust Space Announcement Volume
* Change a stream's playlist
* Add a playlist to the Library
* Create, edit, delete, & reassign line inputs
* Commission & decommission Sound Systems devices
* Grant & revoke Audio Site-level permissions for other users
None
Does **not** have permissions to manage a site's Sound Systems settings or devices.
***
### Set permissions
You can set site permissions for existing users and groups by managing user roles or groups.
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 **Audio** 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 **Audio** as the product line.
2. Select the role to grant to the user.
3. Click **Save**.
{% 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 following URL with the `ask` and `goal` query parameters:
```
GET https://help.verkada.com/sound-systems/getting-started/roles-and-permissions-for-sound-systems.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.
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.