> 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/instalacion/wire-a-door-to-a-verkada-access-controller/set-up-access-control-for-a-man-trap.md).

# Configure el control de acceso para una esclusa de seguridad

Aprenda a conectar puertas al AC41 para usar una esclusa de seguridad

Algunas instalaciones requieren necesidades de seguridad física más rigurosas, y su solución de control de acceso debería poder admitir estas aplicaciones especiales. Este artículo muestra cómo instalar y configurar el Verkada AC42 para una esclusa de seguridad.

Una *esclusa de seguridad* es un conjunto de 2 puertas en el que la primera puerta debe cerrarse antes de que se permita abrir la segunda, similar a una esclusa de aire.

Para admitir esto, debe cablear las puertas al AC42 de una manera específica para una esclusa de seguridad:

<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-2d01655a97a38e2abbd385809da451a07baf54cd%2Fa8303d470ae5a5afee952ef47915cacc512ae94f.png?alt=media" alt=""></div>

{% hint style="warning" %}
Conectar la cerradura de la puerta interior en serie con el interruptor de contacto de la puerta exterior no permite que la puerta interior se abra hasta que la puerta exterior esté cerrada.
{% 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/es/instalacion/wire-a-door-to-a-verkada-access-controller/set-up-access-control-for-a-man-trap.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.