> 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/configuration/spotify-connect-setup.md).
# Spotify Connect Setup
Learn how to connect your Sound Systems device to Spotify
Verkada Sound Systems devices support [Spotify Connect](https://support.spotify.com/us/article/spotify-connect/). This lets you play music to your spaces and zones from the Spotify app.
{% hint style="danger" %}
You need Audio Site Admin permissions to manage the Spotify Connect integration.
{% endhint %}
***
## Configure Spotify Connect
{% hint style="danger" %}
You must create at least one [space](/sound-systems/configuration/sound-systems-spaces.md) before you can set up Spotify Connect.
{% endhint %}
{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Speakers.**
{% endstep %}
{% step %}
**Click on your Speaker site > Go To Site.**
{% endstep %}
{% step %}
**Select the space or zone to connect.**
{% endstep %}
{% step %}
**Ensure Allow Casting is enabled.**
{% endstep %}
{% step %}
**Connect your phone or computer to the same network as your Sound Systems device.**
{% hint style="danger" %}
To connect for the first time, connect your phone or computer to the same network as your Sound Systems devices.
{% endhint %}
{% endstep %}
{% step %}
**In the Spotify app, start playing a song, then tap** 
**in the bottom right.**
{% endstep %}
{% step %}
**In the list that appears, locate the name of your Space or Zone and tap on it to connect.**
After the initial connection, your phone or computer no longer needs to be on the same network as your Sound Systems devices.
{% endstep %}
{% endstepper %}
***
## View Spotify Connect streams
From the Speakers home page, you can view your active Spotify Connect streams for a given Site.
{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Speakers.**
{% endstep %}
{% step %}
**On the left navigation, select Sites.**
1. Select your site.
2. On the right, click **Go to Site.**
{% endstep %}
{% step %}
**The site's active streams will appear on the left under Streams.**
{% endstep %}
{% endstepper %}
***
## Disconnect a Spotify Connect stream
{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Speakers.**
{% endstep %}
{% step %}
**On the left navigation, select Sites.**
1. Select your site.
2. On the right, click **Go to Site.**
{% endstep %}
{% step %}
**In the player bar, click the Stream Selector drop-down in the bottom left.**
{% endstep %}
{% step %}
**Click the Spotify stream you want to disconnect.**
{% endstep %}
{% step %}
**Click** :x: **on the player bar to disconnect the Spotify stream.**
{% 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/configuration/spotify-connect-setup.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.