> 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/get-started-with-sound-systems.md).

# Get Started with Sound Systems

Set up and connect your Verkada Sound System devices

Verkada Sound Systems provides enterprise-grade music, instant announcements, and AI-powered deterrence across every site, all managed from your Command platform.

{% hint style="danger" %}
You need Audio Site Admin permissions to add a Sound Systems device to Command.
{% endhint %}

#### What you need

* PoE-enabled switch or PoE injector
* DHCP-enabled network
* Cat5 or Cat6 cabling

### Create a site

Sites are the logical way of grouping and managing devices within your Command organization. Site-level permissions make managing and viewing your devices easier. See [Manage Your Sites and Subsites](https://help.verkada.com/verkada-cameras/configuration/manage-sites-and-subsites) for more information on site creation and management.

### Add a Sound Systems device

At least one Sound Systems device needs to be added to Command before you can see the **Speakers** tab in the **All Products** menu. Sound System devices can be added from the **Devices** page. See [Add Network Speaker to Command](/sound-systems/configuration/add-network-speaker-to-command.md) or [Add Network Audio Player to Command](/sound-systems/configuration/add-network-audio-player-to-command.md) for steps on setting up your respective devices.

### Licensing

Every network speaker, network audio player, and Soundtrack stream needs a license. Verkada licensing is applied for each Command organization, and the licenses co-term on a single expiration date. Your licenses may have been automatically added if you claimed your devices via order number. Otherwise, manually add the licenses from the Admin page. See [Manage Your Licenses](/command/licensing/manage-your-licenses.md) for more information on adding and managing licenses.

### Connect a Sound Systems device

Most Verkada Sound Systems devices are powered via PoE and connect to the network via Ethernet. The NS151 wireless network speaker can be powered via AC power and utilize Wi-Fi for connectivity. See the [Sound Systems datasheet](https://docs.verkada.com/docs/network-speakers-overview.pdf) for the power and network requirements of your specific device.

### Check Network Settings 

Verkada Sound Systems devices are designed to be plug-and-play. However, if your environment includes a firewall with custom rules and policies, you may need to make some configuration changes to get your devices connected to the cloud. See [Sound Systems Network Settings](/sound-systems/getting-started/sound-systems-network-settings.md) for more information.


---

# 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/get-started-with-sound-systems.md?ask=<question>&goal=<user_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.