> 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/creating-a-new-morpho-biometric-card-type.md).

# Creating a new Morpho Biometric Card Type

### Introduction

A Morpho Biometric Card Type needs to be created in Gallagher Command Centre Configuration Client before the readers are added. This procedure describes how to create a new Morpho Biometric Card Type.

**Notes:**

* Only **one** Morpho Biometric Card Type is available per Command Centre Server.
* Operators require the "Configure Site" operator privilege to create, edit, view and delete Biometric Types, including the Mifare Key on the **Card Encoding** tab.

  If an operator has the "View Site" operator privilege, but not "Configure Site", they will be able to view Biometric Type properties, EXCEPT for the Mifare Key properties.

{% hint style="danger" %}
For multi-server systems, each server needs to have a Morpho Biometric Type set up manually, otherwise cardholders with a Biometric Type from a remote server will not be replicated on the local server. Biometric inactivity is managed by each server independently, using the Morpho Biometric Type configuration unique to each server.
{% endhint %}

***

### Configuration

1. In Command Centre Configuration Client, click **Configure** from the menu bar, then **Card Types**.

   The **Card Type** List Window opens (in [grid view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/grid-view.md)).
2. **Right click** and select **New\...Morpho Biometric Type**.

   By default the **General** tab displays.

   **Note:** Only one Morpho Biometric Type can exist in the system at any one time.
3. Enter a **Name** and **Description**, and select the appropriate **Division**.
4. Click each tab in turn to configure the Card Type:

<details>

<summary>Card Encoding tab</summary>

1. Click the **Card Encoding** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-aaa200cf83a35e859c1fd158c87941be5c5fb9d0%2Fmorphobiometrictype_cardencodingtab.png?alt=media)
2. Configure the settings on this screen as appropriate.

   <table><thead><tr><th width="166">Field</th><th>Description</th></tr></thead><tbody><tr><td>Region Code</td><td><p>This is the letter representing the <strong>Region Code</strong> for your Facility Code.</p><p><strong>Note:</strong> ‘A’ is the default and should be changed to match the Region Code in your site license. Refer to the <strong>Licensing</strong> tab of the Server Properties for the Region Code.</p></td></tr><tr><td>Facility Code</td><td><p>Although any Facility Code can be used for the Morpho Biometric Card Type, we recommend using the <strong>Facility Code</strong> as listed in the site license. Refer to the <strong>Licensing</strong> tab of the Server Properties for the Facility Code.</p><p>Note the Facility Code can only be changed once. If changed, it will require all existing fingerprint templates to be re-captured.</p></td></tr><tr><td>Current Facility Codes</td><td>If your site Facility Code has already been entered, then select it from this drop-down list. Adjust the card number allocation of existing Card Type, range needs to be 31 to 8388607.</td></tr><tr><td>Capture Type</td><td>Options for ‘Fingerprint Only’ or ‘Fingerprint +Vein’. This drives the behaviour within the system for correct templates to capture during enrolment and associated warnings.</td></tr></tbody></table>
3. The **Card Encoding** section is required for card encoding.

   <table><thead><tr><th width="192">Field</th><th>Description</th></tr></thead><tbody><tr><td>Fingerprint Starting Sector<br>and<br>Finger Vein Starting Sector</td><td><p>These fields allow you to select which sector of the Mifare object will be used.</p><p>(Range = 1 - 6. Default = 1)</p></td></tr><tr><td>Mifare Classic A Key</td><td><p>The key entered here will be used to provide protection around reading cards encoded with Morpho biometric templates. This key will provide read access to the Morpho section of encoded cards.</p><p><strong>Notes:</strong></p><ul><li>The A Key on the Morpho Card Type should match the A Key on the Card Object.</li><li>This key must be unique to sites to prevent cards being used on other sites. Therefore, it is recommended you use the <strong>Generate key</strong> button.</li><li>The key is masked with 'X' characters once <strong>Apply</strong> is clicked.</li></ul></td></tr><tr><td><strong>Generate key</strong> button</td><td>Clicking this button automatically generates a random value that populates the <strong>Mifare Classic A Key</strong> field.</td></tr><tr><td>DESFire Key</td><td><p>The key entered here is used to control access to the Morpho data encoded on a card.</p><p><strong>Note:</strong></p><ul><li>In order to prevent cards from another site being used, this key must be unique. To achieve this, it is recommended you use the <strong>Generate key</strong> button.</li><li>The key is masked with 'X' characters once <strong>Apply</strong> is clicked.</li></ul></td></tr><tr><td><strong>Generate key</strong> button</td><td>Clicking this button automatically generates a random value that populates the <strong>DESFire Key</strong> field.</td></tr></tbody></table>
4. If your site is a Multi-Server system, and you need to export a key to send to another system, perform the following steps:
   1. Click the **Export Keys...** button.

      A 'Please choose a password' dialog displays.
   2. Enter a password.

      **Note:** The password must be at least eight characters long, and can be a maximum of 32 characters.
   3. Click the **OK** button.

      A ‘Save As’ dialog displays with a default filename **MorphoBiometricKeys.txt**
   4. Change the default filename if required, and path your way to the location where you want to save the key file.
   5. Click the **Save** button.

      The message *"Key successfully exported and protected by your password"* displays.
5. If you want to import a key from an exported file, perform the following steps:
   1. Click the **Import Key…** button.
   2. Path your way to the location where the key file you want to import is located and click on the key file you want to import.
   3. Click the **Open** button.

      An 'Enter password' dialog displays.
   4. Enter the correct password for the selected key file (this password will need to be supplied by the site that exported the key).
   5. Click the **OK** button.

      The **MIFARE Classic A Key** field displays the text 'IMPORTED KEY', and/or the **DESFire Key** field displays the text 'XXXXXXXXX IMPORTED KEY XXXXXXXXX' to confirm the key has been imported successfully.

      **Note:** Keys exported by earlier versions than vEL8.00 of Command Centre cannot be imported.
   6. Click the **Apply** button to save the new key(s).

      The key is masked with 'X' characters.

</details>

<details>

<summary>Biometric Inactivity tab</summary>

1. Click the **Biometric Inactivity** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-d16334e70f2362545fab7a1c2d19f1a2f3df9ced%2Fmorphobiometrictype_biometricinactivitytab.png?alt=media)
2. Do you wish to enable the Inactive Biometrics Expiry feature?

   <table><thead><tr><th width="66">If...</th><th>then...</th></tr></thead><tbody><tr><td>yes,</td><td><p>check the <strong>Disable Inactive Biometrics</strong> checkbox.</p><p>Go to Step 3.</p></td></tr><tr><td>no,</td><td><p>leave the <strong>Disable Inactive Biometrics</strong> checkbox unchecked.</p><p>Go to the next tab.</p></td></tr></tbody></table>
3. Enter a figure to represent the number of days of inactivity that will disable biometrics.

   **Notes:**

   * When this feature is first enabled the default timeout = 30 days. The range is 1-999 days.
   * If you set the biometrics to disable after 1 day of inactivity, they will become disabled 24 hours to the second after the **Apply** button is clicked.
   * Cardholders will be expired regardless of activity if card activity events are not configured to log events throughout the site.

     (Refer to [Event Defaults](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/event-defaults.md) for further detail.)

</details>

<details>

<summary>Advanced tab</summary>

1. Click the **Advanced** tab.

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

   **Note:** The fields will be populated with any previously configured values for existing biometric types.
2. Configure the **Privacy Settings**, (i.e. Template Storage Mode settings), as required.

   These settings control whether or not biometric templates will be stored in the Command Centre database, and whether or not operators may override this setting for individual Cardholders.

   **Note:** For privacy reasons, some sites may want to prevent templates from being stored in the Command Centre database, and instead encode them onto cards.
3. The 'Duplicate Detection' option prevents the same fingerprint/vein/Wave from being enrolled twice.

   Check the **Prevent duplicate biometrics from being enrolled** checkbox if required, and select the appropriate **Threshold** from the drop-down list.

   **Notes:**

   * The first time this option is selected and applied, the system will check for any duplicate fingerprints and raise an event for each duplicate it finds.
   * For the 'Duplicate Detection' feature to work, an IDENT License and USB Dongle (C864403/C864405) are required on the server.
   * Duplicate Detection for face biometrics is not supported.
4. Ensure the **Send encryption keys via network** checkbox remains checked, if you require Command Centre to send the encryption keys and certificates to the biometric readers via the network.

   See [Encryption using Command Centre](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/morpho-biometric-integration/communications-encryption/encryption-using-command-centre.md) for further detail.

   <div data-gb-custom-block data-tag="hint" data-style="danger" class="hint hint-danger"><p>A non-network solution, (i.e. the <strong>Send encryption keys via network</strong> checkbox is not checked), requires a separate Biometric Encryption Utility that can be used on a laptop or similar in a safe room/network to connect to the readers and assign them the appropriate keys and certificates. This is done from the reader properties. See <a href="https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/morpho-biometric-integration/communications-encryption/encryption-using-the-biometric-encryption-utility.md">Encryption using the Biometric Encryption Utility</a> for further detail.</p></div>

</details>

<details>

<summary>Finger tab</summary>

Configuration on this tab is only required if your site is using Morpho Fingerprint or Finger Vein readers.

1. Click the **Finger** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-6048c913e679b4a967560278545ee8cc9d896f0b%2Fmorphobiometrictype_morphofingertab.png?alt=media)
2. Configure the settings on this screen as appropriate.

   <table><thead><tr><th width="192">Field</th><th>Description</th></tr></thead><tbody><tr><td>Capture Type</td><td>Options for ‘Fingerprint Only’ or ‘Fingerprint +Vein’. This drives the behaviour within the system for correct templates to capture during enrolment and associated warnings.</td></tr><tr><td>Main Finger Defaults *</td><td>Select the required fingers from the drop-down lists, to be used for normal day-to-day identification at a reader.</td></tr><tr><td>Duress Finger Defaults *</td><td>Select the required fingers from the drop-down lists, to be used for identification at a reader when under duress.</td></tr></tbody></table>

   \* **Note:** All four finger selections on this screen must be unique. If a finger selection is not unique, an error message will display.

</details>

<details>

<summary>Hand tab</summary>

Configuration on this tab is only required if your site is using MorphoWave readers.

1. Click the **Hand** tab.

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

   This screen allows you to identify network connected MorphoWave Readers intended for enrolment.

   **Note:** MorphoWave Readers that are used for enrolment do not get added to Command Centre as Morpho Biometric reader items. These readers are only configured on this screen, and are limited to enrolment functionality only. If a site decides it wants to use an enrolment reader for access purposes, they can remove the enrolment configuration and create the reader as a Morpho Biometric Reader item, allowing them to then use the reader for access at a door.

   <div data-gb-custom-block data-tag="hint" data-style="danger" class="hint hint-danger"><p>Encrypted MorphoWave readers cannot be used for enrolment. A connection error will be seen when trying to capture.</p></div>
2. Configure the settings on this screen as appropriate.

   <table><thead><tr><th width="192">Section</th><th>Description</th></tr></thead><tbody><tr><td>Fingerprint Quality</td><td><p>Click the appropriate radio button for a default acceptable fingerprint quality. (Default and recommended option = Standard)</p><p>If you want operators to have the ability to change the acceptable quality at the time of enrolment, tick the <strong>Allow change at enrolment</strong> checkbox.</p></td></tr><tr><td>Access and Duress hands</td><td><p>Set default access and duress hands. (Default = Both hands for access, therefore none for duress)</p><p><strong>Note:</strong> A minimum of one hand must be selected for access.</p><p>If you want operators to have the ability to change the access and duress hands at the time of enrolment, tick the <strong>Allow change at enrolment</strong> checkbox.</p></td></tr></tbody></table>
3. Specify the network connected MorphoWave readers that will be used for enrolment by clicking the **Add** button.

   The Add or Modify Enrolment Readers dialog displays.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-32082c98aa347d3c543caa08c824be4a15f626a7%2Fmorphowave_addenrolmentreaders.png?alt=media)
4. Enter the **Reader Name** and **IP Address**, and select the appropriate **Workstation** from the drop-down list.
5. Click the **OK** button.

   The Add or Modify Enrolment Readers dialog closes, and the readers details populate the **Enrolment reader(s)** grid.

   **Notes:**

   * The **Modify** button allows existing Enrolment Readers to be modified, and the **Delete** button allows them to be deleted.
   * Enrolment of a cardholder’s fingerprints for use by a MorphoWave Reader is done via the **Cardholder Biometrics** tile in the Command Centre client. See *"Cardholder Biometrics Tile actions"* in the Command Centre Client Help file for further detail.
   * From v9.30 onwards, multiple workstations can be linked to the same enrollment reader IP Address, by creating a new Enrolment reader item with a different workstation.

</details>

<details>

<summary>Face tab</summary>

Configuration on this tab is only required if your site is using VisionPass readers.

1. Click the **VisionPass** tab.

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

   <div data-gb-custom-block data-tag="hint" data-style="danger" class="hint hint-danger"><p>Encrypted VisionPass readers cannot be used for enrolment. A connection error will be seen when trying to capture.</p></div>
2. Specify the network connected VisionPass readers that will be used for enrolment by clicking the **Add** button.

   The Add or Modify Enrolment Readers dialog displays.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-3da23bc93699e3a05155fa795aaca437c7096357%2Fmorphobiometrictype_visionpass_addmodifyenrolmentreaders.png?alt=media)
3. Enter the **Reader Name** and **IP Address**, and select the appropriate **Workstation** from the drop-down list.
4. Click the **OK** button.

   The Add or Modify Enrolment Readers dialog closes, and the readers details populate the **Enrolment reader(s)** grid.

   **Notes:**

   * The **Modify** and **Delete** buttons only become enabled when a Reader is clicked on in the **Enrolment reader(s)** grid, allowing existing readers to be modified or deleted.
   * From v9.30 onwards, multiple workstations can now be linked to the same enrolment reader IP Address, by creating a new Enrolment reader item with a different workstation.

</details>

5. Click the **Custom Fields** tab if you want to add and assign a custom field value to this Morpho Biometric Type.

   For further details regarding the **Custom Fields** tab, see [Custom Fields](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/custom-fields.md).
6. Click the **Notes** tab if you want to add a note(s) about this Morpho Biometric Type.

   For further details regarding the **Notes** tab, see [Notes](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/notes.md).
7. Click **OK** to exit and save your changes.

   Click **Cancel** to exit without saving your changes.

   Click **Apply** to save your changes and stay in this window.

### Result

A Morpho Biometric Card Type has been configured and is ready for use.

To capture fingerprints against cardholders, see [Enrolling Users](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/morpho-biometric-integration/enrolling-users.md).

***

### Editing and Deleting Morpho Biometric Types

Refer to [Editing items](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/editing-items.md) and [Deleting items](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/deleting-items.md) for procedures on how to edit and delete Morpho Biometric Types.

**Note:** You cannot delete Morpho Biometric Types if there are any Cardholders enrolled with Morpho Biometrics or any Morpho Biometric Readers configured to be assigned to Gallagher Controllers, Doors, Elevator Cars or HLI Elevator Cars.


---

# 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/creating-a-new-morpho-biometric-card-type.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.
