> 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/access-control/es/configuracion/configure-a-door-in-command/add-a-camera-live-feed-to-a-door.md).

# Agregue una transmisión en vivo de cámara a una puerta

Aprenda a agregar la transmisión en vivo de una cámara a una puerta con control de acceso

Cuando asigna una cámara a una puerta, agrega una capa de seguridad al ver el historial y la actividad de la puerta.

{% hint style="warning" %}
Puede agregar hasta dos cámaras por puerta.
{% endhint %}

{% stepper %}
{% step %}
**En Verkada Command, vaya a Todos los productos > Acceso .**
{% endstep %}

{% step %}
**Seleccione un sitio del menú desplegable.**
{% endstep %}

{% step %}
**Seleccione la puerta a la que desea agregar una cámara y haga clic en Configuración.**
{% endstep %}

{% step %}
**En Emparejamiento de cámaras, junto a Interior o Exterior:**

a. Haga clic en **Agregar cámara**.

<div align="left" data-with-frame="true"><img src="https://1576776939-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaaHs5RfKqv9Z49mi02cC%2Fuploads%2Fgit-blob-9a1fb271b91b6b6db918850a4d7082cc0bf5f7ef%2F88eefc8169c30c21f56ea0d7c18be0a2a801a990.png?alt=media" alt="" width="599"></div>

b. Seleccione la cámara que desea agregar.\
c. Haga clic en **Listo** para guardar.
{% endstep %}

{% step %}
**Ahora debería ver la transmisión en vivo asociada con la puerta.**
{% 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/access-control/es/configuracion/configure-a-door-in-command/add-a-camera-live-feed-to-a-door.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.