> 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/verkada-cameras/ja/she-ding/view-and-edit-camera-settings/change-a-cameras-orientation.md).
# カメラの向きを変更する
最適な位置になるようカメラの視野を回転します
場合によっては、標準以外の向きで設置すると、カメラはより広い視野を実現できます。たとえば、カメラを90°の角度で取り付けると、長い廊下や階段室を全体的にカバーできます。標準以外の向きで設置されている場合は、Commandでカメラの向きを変更する必要があります。
{% hint style="info" %}
ライブフィードが通常の向きで期待どおりに表示されるように、ステータスLEDが床を向くようにカメラを設置してください。
{% endhint %}
***
## 設定
{% stepper %}
{% step %}
**Verkada Commandで、［All Products］>［Cameras］に移動します。**
{% endstep %}
{% step %}
**設定するカメラを選択します。**
{% endstep %}
{% step %}
**右下の［Settings］をクリックします。**
{% endstep %}
{% step %}
**［Device］>［Orientation］の下で、クリックします。** :pencil-line:**.**
a. 向きモードを選択します。\
b. クリック **保存** 変更を確定します。
{% endstep %}
{% endstepper %}
{% hint style="warning" %}
[Fisheye](https://www.verkada.com/security-cameras/fisheye/) では、次の3つの追加表示モードをサポートしています。Panoramic、Four-Way Split、Pan-Tilt-Zoom。参照: [Fisheyeの表示モードを変更する](/verkada-cameras/ja/she-ding/view-and-edit-camera-settings/change-fisheye-view-modes.md) 詳細情報は
{% endhint %}
---
# 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/verkada-cameras/ja/she-ding/view-and-edit-camera-settings/change-a-cameras-orientation.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 `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.
