> 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/organization-settings/buildings-and-floors/view-live-motion-on-floor-plans.md).

# 실시간 동작 보기

평면도에서 실시간으로 동작을 보는 방법을 알아보세요

Verkada의 모션 표시 기능은 사이트의 평면도에서 실시간으로 움직임을 확인하는 두 가지 방법을 제공합니다.

***

## 모션 감지 설정

모션 감지에서는 움직임이 감지되면 카메라의 시야가 깜박입니다. 이는 실시간으로 이루어집니다.

{% stepper %}
{% step %}
**Verkada Command에서 모든 제품 > 평면도로 이동합니다.**
{% endstep %}

{% step %}
**모니터링할 건물과 평면도를 선택하세요.**
{% endstep %}

{% step %}
**평면도에서 오른쪽 아래의** <img src="https://1764840814-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRq5qDDjsYNxwNzF1bcB%2Fuploads%2FJWUkn5Hw11bSAfjXraQx%2FScreenshot%202026-04-27%20at%2012.02.02%E2%80%AFPM.png?alt=media&amp;token=732a99f7-cf23-4059-9330-25ea8a94fa83" alt="" data-size="line"> **모션 감지.**

<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%2FOjq28TqZNYaIxHQKiV1C%2F8381315f1963c41fe6cac47289756a87346ab925.gif?alt=media&amp;token=b240412f-b192-4d43-a8b3-518941c0dbab" alt=""></div>
{% endstep %}
{% endstepper %}

***

{% hint style="info" %}
**실제 사용 모습을 보고 싶으신가요?** 다음을 확인하세요 [비디오 튜토리얼](https://www.youtube.com/watch?v=wtpgjmmTnXc).
{% 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/organization-settings/buildings-and-floors/view-live-motion-on-floor-plans.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.