> 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/command/ja/herupugadesuka/site-planner-homepage-overview/configure-site-planner-user-preferences.md).

# ユーザー設定

価格、Plan Editorの操作、計測単位のユーザー設定を行う

{% stepper %}
{% step %}
**Verkada Command で、All Products > Site Planner に移動します。**
{% endstep %}

{% step %}
**右上で、次をクリックします。** <i class="fa-gear">:gear:</i>**.**
{% endstep %}

{% step %}
**次の設定について、好みを切り替えることができます:**

a. ～の下で **エディター:**

* クリックしてドラッグ
* スクロールしてズーム
* 測定単位

e. 以下 **部品表:**

* 価格を表示
  {% endstep %}

{% step %}
**（任意）左下の「デフォルトにリセット」をクリックすると、変更を元に戻せます。**
{% endstep %}

{% step %}
**\[Done]をクリックします。**

<div align="left" data-with-frame="true"><img src="https://1706941156-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRq5qDDjsYNxwNzF1bcB%2Fuploads%2Fgit-blob-8a4e0a65411645fd4a8b599cfb747b4a0836e485%2Ffd638b20b18b3e6e4594bcf299261c14ce07501d.png?alt=media" alt="" width="385"></div>
{% endstep %}
{% endstepper %}

{% hint style="info" %}
価格を非表示にすると、MSRPなしで顧客に製品を提示でき、最終見積もりでのコストに関するやり取りをコントロールできます。これにより、エディターと部品表からすべての価格が削除されます。
{% 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/command/ja/herupugadesuka/site-planner-homepage-overview/configure-site-planner-user-preferences.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.
