> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/morpho-biometric-integration/appendix-tamper-prevention-bypass-for-idemia-visionpass.md).

# Appendix: Tamper prevention bypass for IDEMIA VisionPass

For additional security purposes a tamper can be wired to a controller.

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-18e401fa186cc87640c95b1c3a0f178db0d78ec1%2F44861.png?alt=media)

### Operating principle for the switch

Product installed on the wall plate: switch enabled (contact closed).

Product opened (rear connectors accessible): switch disabled (contact open).

### Nominal characteristics of switch block

100 mA at 30 VDC max (Resistive load) according to the safety extra low voltage standard.

{% hint style="danger" %}
This VisionPass terminal is part of security system; it is customer’s responsibility to connect the tamper switch (contact) to physical access controller, in order to prevent the access to the connector blocks. UL has verified this product for access control functions only.
{% 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.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/morpho-biometric-integration/appendix-tamper-prevention-bypass-for-idemia-visionpass.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.
