> 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/installation/wire-a-door-to-a-verkada-access-controller/set-up-access-control-for-a-man-trap.md).
# Set Up Access Control for a Man Trap
Learn how to wire doors to the AC41 for man trap usage
Some facilities require more rigorous physical security needs, and your access control solution should be able to support these special applications. This article shows how to install and configure the Verkada AC42 for a man trap.
A *man trap* is a set of 2 doors where the first door must be closed before the second is permitted to open, similar to an airlock.
To support this, you must wire the doors to the AC42 in a specific way for a man trap:
{% hint style="warning" %}
Connecting the interior door’s lock in series with the exterior door’s contact switch does not allow the interior door to open until the exterior door is closed.
{% 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/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.
