> 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/ko/configuration/configure-a-door-in-command/add-a-camera-live-feed-to-a-door.md).

# 도어에 카메라 라이브 피드 추가

출입 통제 도어에 카메라의 라이브 피드를 추가하는 방법을 알아보세요

문에 카메라를 지정하면 문 기록과 활동을 볼 때 보안이 한층 강화됩니다.

{% hint style="warning" %}
문당 최대 두 대의 카메라를 추가할 수 있습니다.
{% endhint %}

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

{% step %}
**드롭다운 메뉴에서 사이트를 선택하세요.**
{% endstep %}

{% step %}
**카메라를 추가할 문을 선택한 다음 설정을 클릭하세요.**
{% endstep %}

{% step %}
**카메라 페어링에서 내부 또는 외부 옆에:**

a. 클릭 **카메라 추가**.

<div align="left" data-with-frame="true"><img src="https://3458411332-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. 추가할 카메라를 선택하세요.\
c. 클릭 **완료** 저장하려면
{% endstep %}

{% step %}
**이제 문과 연결된 실시간 영상을 볼 수 있어야 합니다.**
{% 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/ko/configuration/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.