> 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/idemia-morpho/configure/set-up-card-pin-and-biometric-combinations.md).

# Set up card, PIN and biometric combinations

Set up card plus biometric plus PIN, card only, and finger only access on IDEMIA readers.

These are the usual card and reader combinations for IDEMIA (Morpho) readers. The user guide describes every configuration. To add a Morpho object to cards, see [Encode cards for IDEMIA readers](https://help.security.gallagher.com/knowledge-hub/products/integrations/third-party-readers/idemia-morpho/configure/idemia-morpho-encoding-a-card-to-use-on-morpho-readers.md).

### Card, biometric and PIN

The card must have the card number and biometrics encoded on it.

1. On the card type, tick **Use PINs**.

   ![MIFARE DESFire Properties, PINs: Use PINs ticked, minimum PIN length 4](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-b32fc59cb6bcdbe997b56480601cbe9f8b7880b3%2FSECHUB-TS-MORPHO-GENERAL-02-card-type-use-pins.png?alt=media)
2. On the card type used for the cardholder, set the Morpho object to **Card Number + Biometrics**, with **Reader ignores PIN** unticked. If cards are already encoded and you change this, they must be re-encoded.

   ![DESFire Properties - Morpho: Contents Card Number + Biometrics, Reader ignores PIN unticked](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-dd5a40d9668b974a11ec6262ed072333dc914a65%2FSECHUB-TS-MORPHO-GENERAL-03-desfire-properties-card-number-biometrics.png?alt=media)
3. The reader does not need **Always request PIN** ticked. But if the cards were encoded with **Reader ignores PIN** ticked on the card type, ticking **Always request PIN** makes the Morpho reader ask for a PIN from a cardholder presenting a card.

   ![Morpho Sigma Multi Reader Properties, Advanced Setup: Always request PIN, which overrides the Reader ignores PIN setting of the card layout; the reader always requests a PIN, and the setting only applies to biometric readers with PIN entry keypads](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-f00bf77f024c2d444edfcd2909aeaa7c00eefa4f%2FSECHUB-TS-MORPHO-GENERAL-04-reader-advanced-setup-always-request-pin.png?alt=media)

### Card only

Use this when a biometric is not required.

1. In the **Card Layout** editor of the card type, make sure the Morpho object has only **Card Number Only** selected. A card encoded with a biometric before must be re-encoded with the new setting.

   ![MIFARE DESFire Morpho no Biometrics - Card Editor: DESFire Properties - Morpho, Contents Card Number Only, Reader ignores PIN unticked](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-4aafa87e1c654e6cb9733d310f5c361e7beec156%2FSECHUB-TS-MORPHO-GENERAL-05-card-editor-card-number-only.png?alt=media)
2. On the reader, the mode must be **Card Selects**.

   ![Morpho Sigma Lite Reader Properties, Setup: Authentication Mode Card Selects, Connection Mode MA5G (the IP address is covered)](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-b055adca9bff7c227c33c2fc7a224ffa58de20b0%2FSECHUB-TS-MORPHO-GENERAL-06-reader-authentication-card-selects.png?alt=media)

With **Card Selects**, a cardholder without a Morpho object on their card cannot get through. On a site where some cardholders still use their finger, [Encode cards for IDEMIA readers](https://help.security.gallagher.com/knowledge-hub/products/integrations/third-party-readers/idemia-morpho/configure/idemia-morpho-encoding-a-card-to-use-on-morpho-readers.md) explains when to use **User Selects** instead.

The newer reader screen does the same: on the reader's **Setup** tab, tick only **Card** under **Authentication Method**, and encode the cards with a **Morpho DESFire** object set to **Card Number Only**. The reader then works as card only and does not need a biometric.

![Morpho Sigma Multi Reader Properties, Setup: Authentication Method with only Card ticked (the IP address is covered)](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-076672f6638cd8e1109cf6951ba681e0c1abc172%2FSECHUB-TS-MORPHO-GENERAL-09-reader-setup-card-authentication.png?alt=media)

![Card Editor: Morpho DESFire object, DESFire Properties - Morpho with Contents Card Number Only and Reader ignores PIN unticked](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-3acedb618a203a30031bd5d90e9557bb9460946b%2FSECHUB-TS-MORPHO-GENERAL-10-card-editor-desfire-card-number-only.png?alt=media)

### Finger only

1. The fingerprint templates must be stored in the **database**, so they can be sent to the readers and stored there to allow access (Morpho Biometric Type, **Advanced** tab, **Save biometrics to database**).

   ![Morpho Biometric Type 1 Properties, Advanced: Privacy Settings, Save biometrics to database ticked](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-2a7f3f2687268a051538ad3a151875f96d88f325%2FSECHUB-TS-MORPHO-GENERAL-07-biometric-type-save-biometrics-to-database.png?alt=media)
2. Set the readers to **Finger Only**. (The same can be had with the reader in **User Selects** mode.)

   ![Morpho Sigma Lite Reader Properties, Setup: Authentication Mode Finger Only (the IP address is covered)](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-f3ed6fde0305d9808a27bb10eb8c1c415e38a063%2FSECHUB-TS-MORPHO-GENERAL-08-reader-authentication-finger-only.png?alt=media)


---

# 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/idemia-morpho/configure/set-up-card-pin-and-biometric-combinations.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.
