> 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/es/configuracion-de-la-organizacion/buildings-and-floors/view-live-motion-on-floor-plans.md).
# Ver movimiento en vivo
Aprende cómo puedes ver el movimiento en vivo en tu plano de planta en tiempo real
La función de visualización de movimiento de Verkada ofrece dos formas de ver el movimiento en vivo en los planos de planta de su sitio en tiempo real.
***
## Configurar la detección de movimiento
Con la detección de movimiento, el campo de visión de la cámara pulsa cuando se detecta movimiento. Esto ocurre en tiempo real.
{% stepper %}
{% step %}
**En Verkada Command, ve a Todos los productos > Planos de planta.**
{% endstep %}
{% step %}
**Seleccione el edificio y el plano de planta que desea monitor.**
{% endstep %}
{% step %}
**En Planos de planta, en la parte inferior derecha, haga clic en** 
**Detección de movimiento.**
{% endstep %}
{% endstepper %}
***
{% hint style="info" %}
**¿Prefieres verlo en acción?** Echa un vistazo al [video tutorial](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/es/configuracion-de-la-organizacion/buildings-and-floors/view-live-motion-on-floor-plans.md?ask=&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.
