> 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/installation/wire-a-door-to-a-verkada-access-controller/set-up-access-control-for-a-man-trap.md).
# 맨트랩용 출입 통제 설정
맨트랩 사용을 위해 AC41에 도어를 배선하는 방법을 알아보세요
일부 시설은 더 엄격한 물리적 보안 요구 사항이 필요하며, 귀하의 출입 통제 솔루션은 이러한 특수 용도를 지원할 수 있어야 합니다. 이 문서에서는 맨트랩에 Verkada AC42를 설치하고 구성하는 방법을 보여줍니다.
A *맨트랩* 는 첫 번째 문이 닫힌 후에만 두 번째 문이 열릴 수 있는 2개의 문으로 이루어진 구조로, 에어록과 비슷합니다.
이를 지원하려면 맨트랩을 위해 문들을 AC42에 특정한 방식으로 배선해야 합니다:
{% hint style="warning" %}
실내문의 잠금장치를 실외문의 접점 스위치와 직렬로 연결하면 실외문이 닫혀야만 실내문이 열리게 됩니다.
{% 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/access-control/ko/installation/wire-a-door-to-a-verkada-access-controller/set-up-access-control-for-a-man-trap.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.
