> 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 %}
**내 프로젝트에서 프로젝트를 선택합니다.**
{% endstep %}

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

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

* 제품의 선택을 해제하여 화면에서 숨깁니다.

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

  <div align="left" data-with-frame="true"><img src="/files/4c4c3280aceae14191f74097d27054c2bbf8bbbb" 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.verkada.com/command/ko/need-help/site-planner-homepage-overview/change-site-plan-visibility-options.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.