> 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/change-site-plan-visibility-options.md).

# 표시 옵션

사이트 계획을 더 쉽게 관리할 수 있도록 다양한 요소를 표시하거나 숨기세요

{% stepper %}
{% step %}
**Verkada Command에서 All Products > Site Planner로 이동합니다.**
{% endstep %}

{% step %}
**My Projects 아래에서 프로젝트를 선택합니다.**
{% endstep %}

{% step %}
**왼쪽 탐색에서 계획 > 계획 편집을 선택합니다.**
{% endstep %}

{% step %}
**아래쪽에서 클릭합니다** <i class="fa-object-intersect">:object-intersect:</i>**.**

* 보기에서 숨기려면 제품 선택을 해제하세요.

  **참고:** 제품 숨기기 **하지 않습니다** 계획에서 제거하지 않습니다.
* 사이를 전환 **위성** 및 **도로 지도** 지도 보기를 변경합니다.
* 슬라이더를 사용하여 아이콘 크기(25%-500%)를 변경합니다.

  <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-0493d80c5eae18bc9659365c97dc1ccd42762938%2F5391caaf6d3d15217a52979aa29ad640ab9d0c49.png?alt=media" alt="" width="378"></div>

{% 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/command/ko/need-help/site-planner-homepage-overview/change-site-plan-visibility-options.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.