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

# Selector de sitios de altavoces

Aprende a navegar por tus sitios de altavoces en Command

Al navegar por los sitios de altavoces en Command, puedes cambiar fácilmente de un sitio a otro para administrarlos de forma detallada.

{% hint style="warning" %}
Cuando se selecciona un sitio de altavoces, solo verás los espacios, las zonas, los dispositivos y las transmisiones de ese sitio y de los posibles subsitios que contenga.
{% endhint %}

***

### Seleccionar un sitio de altavoces

{% stepper %}
{% step %}
**En Verkada Command, ve a Todos los productos > Altavoces.**
{% endstep %}

{% step %}
**Selecciona un sitio de altavoces.**
{% endstep %}

{% step %}
**Haz clic en Go To Site para inspeccionar el sitio.**
{% endstep %}
{% endstepper %}

### Cambiar el sitio de altavoces que estás inspeccionando

{% stepper %}
{% step %}
**En cualquier página de Speakers, haz clic en las iniciales del sitio en la barra de navegación izquierda.**
{% endstep %}

{% step %}
**Selecciona un sitio de altavoces.**
{% endstep %}

{% step %}
**La vista cambiará al sitio que hayas seleccionado.**
{% 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 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/es/configuracion/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 `automate deployments from our CI pipeline` 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.
