> 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/speaker-site-selector.md).

# Speaker Site Selector

Learn how to navigate your speaker sites in Command

When you navigate your speaker sites in Command, you can effortlessly switch between sites for granular management.

{% hint style="warning" %}
When a speaker site is selected, you will only see the spaces, zones, devices, and streams on that site and any subsites it may contain.
{% endhint %}

***

### Select a speaker site

{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Speakers.**
{% endstep %}

{% step %}
**Select a speaker site.**
{% endstep %}

{% step %}
**Click Go To Site to inspect the site.**
{% endstep %}
{% endstepper %}

### Change the speaker site you are inspecting

{% stepper %}
{% step %}
**From the Any Speakers page, click the site initials in the left navigation bar.**
{% endstep %}

{% step %}
**Select a speaker site.**
{% endstep %}

{% step %}
**This will change your view to the site you selected.**
{% 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/speaker-site-selector.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.