> 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/ko/need-help/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://1764840814-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/ko/need-help/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.