> 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/configuring-biometric-verification.md).

# Configuring Biometric Verification

### Important information when changing the Facility Code of the Morpho Biometric Type

Before changing the facility code of the Morpho Biometric Type, ensure you have taken a backup of the Gallagher Command Centre database.

In version vEL5.20.xxx (or later) of Gallagher Command Centre, there are restrictions on changing the facility code of the Morpho Biometric Type, (i.e. the facility code cannot be changed if cardholders have been assigned cards which use that facility code).

The following procedure should be used after upgrading to avoid having to change the facility code of the Morpho Biometric Type when there are cards using that facility code allocated to cardholders.

### After Upgrading

Perform the following steps after upgrading Command Centre:

1. Determine the facility code to use for the Morpho Biometric Type.

   The Command Centre license will enable encoding of MIFARE cards with Gallagher data using 1 or more facility codes.
2. How many facility codes have previously been used to encode MIFARE cards?

   <table><thead><tr><th width="180">If...</th><th>then...</th></tr></thead><tbody><tr><td>only 1 facility code</td><td>this facility code could also be used when encoding Morpho data on the MIFARE cards.</td></tr><tr><td>several facility codes</td><td><p>one of them may be selected as the facility code to use when encoding Morpho data on the MIFARE cards.</p><p>The facility code that has been used to encode the most cards is recommended, as a cardholder will require a new card to be issued if they need card access using a Morpho reader and have previously been issued a card with a different facility code.</p></td></tr></tbody></table>

   **Note:** A facility code that has never been used could also be chosen.
3. Adjust the card number allocation of existing Card Types.

   All Card Types with a facility code matching that chosen in Step 2 must have their card number allocation range changed to be within the range 31 to 8388607 inclusive. Cardholder's fingerprints/veins are allocated card numbers in the range 8388608 to 16777215. Card numbers in the range 1 - 30 are used by Morpho Readers to create events such as Biometric Reader Tampered and can no longer be assigned to cardholders.
4. If necessary, change the facility code of the Morpho Biometric Type.

   If the facility code of the Morpho Biometric Type is not the value selected in Step 2, then change the facility code of the Morpho Biometric Type to the value selected in Step 2.
5. Edit the card layout of all Card Types that need encoding with the Morpho Biometric Type.

   The Morpho MIFARE Object can be added to the card layout using the Card Layout Editor.
6. Encode cards.

   Cards will need to be re-encoded to gain access using Morpho readers in verification mode. Any cards whose card number is not in the range 31 to 8388607, or uses a different facility code to the Morpho Biometric Type cannot be encoded and must be removed from the cardholder, and a new card allocated. The old card can then be re-encoded.


---

# 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/configuring-biometric-verification.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.
