> 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/products/integrations/third-party-readers/invixium/reference/invixium-integration-common-faqs.md). # Common questions Find answers about enrollment, access decisions, supported readers, OSDP, and Invixium support. ### Enrollment Cardholders are enrolled in Command Centre as normal. Enroll biometrics through a web page opened in the Command Centre Client. Only enroll the biometric used for identification. IXM WEB is on-premises, so internet access is unnecessary except for license upgrades. ### Access decisions The reader makes temperature and mask decisions. The Controller makes cardholder access decisions. ### Reader support The Command Centre license limit is **100 devices**. Contact the regional representative for more. Use one Invixium reader per Entry zone and one per Exit zone. Zones are named after the Command Centre door. Dual authentication is not supported. This includes Invixium face or finger with a Gallagher reader for PIN or card. ### OSDP access messages If cardholders receive duplicate OSDP access messages, disable **Panel Feedback** on the **Access Control** tab. Enable **Events** on the **OSDP** tab. ### Support Contact Gallagher Security Technical Support first. Invixium also provides a public [Customer Portal](https://www.invixium.com/support/). --- # 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/products/integrations/third-party-readers/invixium/reference/invixium-integration-common-faqs.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.