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

# スピーカーサイトセレクター

Command でスピーカーサイトを操作する方法

Command でスピーカーサイトを切り替えると、サイト間を簡単に移動して、細かく管理できます。

{% hint style="warning" %}
スピーカーサイトを選択すると、そのサイトと、そのサイトに含まれるサブサイトのスペース、ゾーン、デバイス、ストリームのみが表示されます。
{% endhint %}

***

### スピーカーサイトを選択する

{% stepper %}
{% step %}
**Verkada Commandで、［すべての製品］>［スピーカー］に移動します。**
{% endstep %}

{% step %}
**スピーカーサイトを選択します。**
{% endstep %}

{% step %}
**「サイトに移動」をクリックして、サイトを確認します。**
{% endstep %}
{% endstepper %}

### 確認するスピーカーサイトを変更する

{% stepper %}
{% step %}
**スピーカーのいずれかのページで、左側のナビゲーションバーにあるサイトのイニシャルをクリックします。**
{% endstep %}

{% step %}
**スピーカーサイトを選択します。**
{% endstep %}

{% step %}
**選択したサイトの表示に切り替わります。**
{% 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/ja/she-ding/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.
