> 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/ja/insutru/wire-a-door-to-a-verkada-access-controller/set-up-access-control-for-a-man-trap.md).
# マン・トラップのアクセスコントロールを設定する
マン・トラップ用途で AC41 にドアを配線する方法を学ぶ
いくつかの施設では、より厳格な物理セキュリティ要件が必要であり、アクセスコントロールソリューションはこれらの特殊な用途をサポートできる必要があります。この記事では、マン・トラップ向けにVerkada AC42を設置および設定する方法を紹介します。
1つの *マン・トラップ* とは、最初のドアが閉まるまで2つ目のドアを開けられない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/ja/insutru/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.
