> 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/command-centre-client/using-command-centre/working-with-viewers/tile-actions/cardholder-biometrics-tile-actions.md).

# Cardholder Biometrics Tile actions

The Cardholder Biometrics Tile displays either a photo of a cardholders face or a set of fingerprints/finger veins that have been captured for a Cardholder, for use at Morpho Biometric Readers.

![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-98774a333e612b4213ee1b72970f130249fa1b11%2Fcardholderbiometrics_operationalmode.png?alt=media)

**Note:** The Duress Biometrics section and the Reader Database ID field will only appear if these options were selected during configuration.

### Operator Privileges

<table><thead><tr><th width="211">To...</th><th>you need...</th></tr></thead><tbody><tr><td><strong>view</strong> a Cardholder's biometrics,</td><td><p>one of the following privileges in the division of the cardholder:</p><ul><li>"View Cardholders"</li><li>"Edit Cardholders"</li><li>"View Cardholder Notes"</li><li>"Edit Cardholder Notes"</li><li>"Edit Cardholder Notification"</li><li>"Print/Preview &#x26; Encode Card"</li><li>"Delete Cardholders"</li></ul><p><strong>Note:</strong> You only need the privilege to view the Cardholder in order to "Verify" their biometrics.</p></td></tr><tr><td><strong>capture</strong> or <strong>remove</strong> a Cardholder's biometrics,</td><td>the "Edit Cardholders" privilege in the Division of the Cardholder.<br><br><strong>Note:</strong> The above is required to enrol on a MSO 300, however when enrolling on Morpho Wave, the "View Site" privilege is also required.</td></tr></tbody></table>

### Tile Actions

<details>

<summary>Capturing Biometrics (Fingerprint or Finger Vein)</summary>

Use the following procedure to enrol a Cardholder for a Morpho Fingerprint or Finger Vein:

1. Click the **Capture** button for either the Main or Duress Biometrics group.

   **Note:** For fingerprint or finger vein capture to work the following needs to be installed:

   <table><thead><tr><th width="184">For the...</th><th>you need...</th></tr></thead><tbody><tr><td>Server Workstation</td><td>+ Microsoft Visual vc10redist_x86<br>+ Microsoft Visual vc12redist_x86<br>+ Microsoft Visual vc14redist_x86<br>+ Microsoft Visual vc14redist_x64</td></tr><tr><td>Client Workstation</td><td>+ Microsoft Visual vc10redist_x86<br>+ Microsoft Visual vc12redist_x86<br>+ Microsoft Visual vc14redist_x86<br>+ Microsoft Visual vc14redist_x64</td></tr></tbody></table>

   If they are missing, the following error message will display when you click the **Capture** button:

   *"Failed to capture fingerprints.*

   *Reason: Device DLL or one of its dependencies is missing or not registered."*

   These files are located in the `'Utilities\Morpho\Microsoft Redistributables'` folder of the Command Centre installation files. See Installing Microsoft Redistributables.

   The Capture Finger screen displays with instructions on what to do next within the appropriate finger capture area.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-caf8ba0b52452909b1c17583c9eed8d709811db4%2Fcapturefirstfingerprint_tile.png?alt=media)
2. Select the finger you want to capture biometric templates for from the **Finger** drop-down list.

   As a complete capturing process, both the Main and Duress Biometric groups require fingerprints or finger veins to be captured for two fingers, (e.g. the 'Left Index Finger' and the 'Left Middle Finger'), and three fingerprints/finger veins must be captured per finger.

   **Note:** Biometric captures are stored on the reader and take up quite a bit of space, therefore if duress is not an issue for your site it is suggested that you do not bother capturing 'Duress Biometrics'. Also, duress will only work if a cardholder has been given access to that Morpho Reader.
3. Place the appropriate finger on the enrolment device.

   As each biometric capture occurs the quality of that individual capture is displayed at the bottom of the biometric display area, which remains visible after they have moved on to the next capture.

   **Notes:**

   * The overall quality (score) of the biometrics that are captured needs to be more than 165 to be validated by the system.
   * At any time the user can click the **Recapture** button to re-start the process for capturing the three samples for the current finger.
4. Repeat Step 2 twice so you have three captures of the same finger.
5. Repeat Steps 2 - 3 for the second finger of that Biometric group.

   On capturing two fingers successfully:

   * an image displays under the appropriate Biometric group on the Cardholder Biometrics Tile to indicate that something has been captured,
   * the **Clear** button (used for deleting the captured biometrics) for the group is enabled, and
   * the **Verify** button is enabled.

     This button allows you to verify that the Cardholder's fingerprint/finger vein templates that have been captured can actually be used successfully for biometric authentication, (i.e. there is a match between the captured templates and the person's fingerprints/finger veins).
6. Click the **Verify** button.

   The Verify Biometric pop-up displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-6b08c30c64f1e3d40b8534d4e85049cf58786cd9%2Fverifyfingerprint_popup.png?alt=media)
7. Place the appropriate finger on the enrolment device.

   The system verifies whether the captured biometrics match the existing templates already captured, and the appropriate message box displays indicating if there is a match or not. Once a match has been made the finger image is removed and result is displayed at the bottom.
8. Click the **Close** button.

</details>

<details>

<summary>Capturing Biometrics (Hand)</summary>

The following procedure describes how to enrol a Cardholder's fingerprints using a MorphoWave Reader:

**Note:** Previously used DESFire cards should not be encoded for different cardholders.

1. Click the **Hand** tab.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-99ce13465e5e31de633dcdc75cf2fd8c455b3bf0%2Fcardholderbiometrics_operationalmode_morphowavetab.png?alt=media)

   **Note:** All eight finger locations displaying as ‘blank’ indicates that the Cardholder is not enrolled for MorphoWave.
2. Click the **Capture** button.

   The MorphoWave Fingerprint Enrolment screen displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-69d33d7289d3c279ff5eb6286bff128fb64d2c1d%2Fmorphowavefingerprintenrolmentscreen1.png?alt=media)

   **Note:** Hand overlays display briefly to demonstrate the order of the fingers.
3. If the Morpho Biometric Card Type (in the Configuration Client) has been configured to allow changes at the time of enrolment, you can change the following default values if necessary:
   * **Fingerprint Quality** by selecting Standard, High or Very High (Default and recommended option = Standard), and
   * 'Access and Duress hands’ by selecting Access, Unused or Duress for each hand.
4. If there is more than one **Enrolment Reader** listed, ensure the correct one is selected.
5. Change the status of each fingerprint as required:

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-a46b50232bf620883d4a0a6b7df92585af4b63c9%2F38897.png?alt=media) Active

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-b1aca8cb0c634a8fa6f85b01f9996aad0b293987%2F38898.png?alt=media) Bandaged

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-85e5a19faae17efacfd564c5229108b9fdcc7276%2F38899.png?alt=media) Missing

   **Note:** At least one fingerprint must be active on each hand.
6. Click the **Next** button.

   The wizard displays the enrolment screen for the hand selected as the ‘set access’ hand.

   **Notes:**

   * When both hands are selected as "ACCESS" hands, the right-hand enrolment is displayed first.
   * Only "ACCESS" biometrics will be encoded to the card, (e.g. if one hand is selected as "DURESS", then this hand’s fingerprints will not be written to the card).

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

   A green light on the MorphoWave Reader indicates connection has been established.
7. Insert the hand to enrol between the cover and optical sensor of the reader, ensuring it is flat, palm down, and fingers are spread slightly apart.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-8fa6b7af94285a092068661e619912754f2e1ba3%2Fmorphowavecompactreader.png?alt=media)
8. Slide the hand in the appropriate direction for the hand being enrolled, (i.e. from right to left for the right-hand, and from left to right for the left-hand, with the Index finger first).

   Once the hand has enrolled successfully, a message displays indicating that the device is ready to enrol the other hand.

   **Notes:**

   * After 5 unsuccessful attempts the system times out.
   * If enrolment is unsuccessful, a message indicating the reason will display. *For example:*

     If the hand slides from the wrong direction the message *"Bad hand direction"* displays.

     If the hand is not waving properly between cover and optical sensor the message *"Wave hand in parallel"* displays.
9. Repeat Steps 7 - 8 for the other hand.

   Once that hand has enrolled successfully, another message displays indicating the hand has been enrolled, and the **Accept** button becomes enabled.
10. Click the **Accept** button.

    The MorphoWave Fingerprint Enrolment screen closes, and the **Hand** tab of the Cardholder Biometrics Tile now shows enrolled fingerprints.

    ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-80cf88eb8e5bc7a3704e9ef12576f0e0669c201a%2Fcardholderbiometrics_morphowavetab_enrolled.png?alt=media)

    **Notes:**

    * The MorphoWave DESFire object will not encode "UNUSED" and "DURESS" fingerprints to a card. Only "ACCESS" fingerprints will encode to cardholder’s card.
    * Once fingerprints are enrolled and saved (to either database and card, or database only), any changes to the fingerprints status will result in the following message displaying on the Cardholder Biometrics Tile:

      *"If these biometrics are encoded to a card, the card will need re-encoding."*
    * If a cardholder has had biometrics enrolled previously and the fingerprint status for both hands has changed to "UNUSED", the following message will display on the Cardholder Biometrics Tile:

      *"At least one hand must be set to Access to use the reader. If these biometrics are encoded to a card, the card will need re-encoding."*

      When the operator starts encoding the card for the cardholder (with "Card Number + Biometrics") the following warning message will display, giving them the option to either proceed with encoding or not.

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

      **IMPORTANT:** Even if the card is encoded, the cardholder won’t be able to access any MorphoWave Biometric Readers. However, if the card has other objects, (e.g. MIFARE DESFire object), it can still be read by Gallagher readers.
11. Click the **Save** button to save the fingerprints to the database, or click the **Revert to Saved** button to undo.
12. Click the **Verify** button.

    **Note:** A dialog will display if there is more than one enrolment reader available. If so, select the correct reader from the list and click the **Next** button.

    A message displays on the tile indicating which hand to verify.

    ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-418bb264bed2c69a50d3122b7502b3e4a52a3175%2Fmorphowave_readytoverify.png?alt=media)
13. Wave the appropriate hand over the enrolment reader to verify the saved fingerprints.

    A message displays indicating the hand was successfully verified, followed by a message indicating it is ready to verify the other hand.
14. Wave the other hand over the enrolment reader.

    A message displays indicating that hand was also successfully verified.
15. Click the **Close** button.

</details>

<details>

<summary>Capturing Biometrics (Face)</summary>

{% hint style="danger" %}
If your site uses both VisionPass and VisionPass SP access readers, you must use VisionPass for enrolment. However, if the site exclusively uses VisionPass SP readers, then a VisionPass SP enrolment reader will suffice.
{% endhint %}

The following procedure describes how to enrol a Cardholder's face using a VisionPass Reader:

1. Click the **Face** tab.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-99185dcdc36c4d3e1b9a2bd874202df983a0f33d%2Fcardholderbiometrics_operationalmode_facetab.png?alt=media)
2. Click the **Capture** button.

   The VisionPass Face Enrolment screen displays.

   *Enrolment with* **VisionPass** *device:*

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-1133706addb56603eda258c4bb55a8abcdbf2709%2Fvisionpassfaceenrolmentscreen1.png?alt=media)

   *Enrolment with* **VisionPass SP** *device:*

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-85708a9d338519a391577309ed68e74e15073634%2Fvisionpassfaceenrolment.png?alt=media)
3. If there is more than one **Reader** listed, ensure the correct one is selected from the drop-down list.
4. Once enrolment process starts, Command Centre will establish connection with the VisionPass Enrolment Reader and capture a face template.

   **Notes:**

   * If there is no enrolment reader set up, *"Connection failed"* and *"No biometric capture devices were found."* messages display.
   * We recommend cardholders stand in front of the enrolment device with their face clearly visible, and remove all "non-always on" accessories, (e.g. remove glasses, face masks).

   The *"face captured successfully"* message displays.

   When the capture process is completed the cardholder picture displays briefly on the screen, so you can ensure the cardholder is the correct person.

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

   **Note:** The enrolment reader requires firmware version to be 2.14.4 or higher.
5. When the enrolment process is completed click the **Accept** button to accept the result.

   **Note:** If the face template isn’t satisfactory, the **Recapture** button can be clicked to restart the face capture process.

   Once the face template has been accepted, the dummy face displays on the Cardholder Biometrics Tile as solid with the modified time.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-6a7c95332b75e4347a94430116ec08daa065f45b%2Fvisionpassfaceenrolment_modified.png?alt=media)

   The face template can be modified by clicking the **Capture** button again, or it can be removed by clicking the **Clear** button.

   Once the **Clear** button is clicked the *"Ensure that the person is in front of the capture device"* message will display again.
6. Click the **Save** button to save the facial template to the database, or click the **Revert to Saved** button to undo.
7. Click the **Verify** button.

   If there is only one enrolment reader available, the verify process will start immediately, and if the facial template is correct the face will be successfully verified. To verify again, click the **Verify** button.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-8636c5dcfdd00411deea96c8f021bfa74289ed29%2Fvisionpassfaceenrolmentscreen2.png?alt=media)

   **Note:** If there is more than one enrolment reader available, a dialog will display. Select the correct reader from the list and click the **OK** button, and then the **Verify** button.
8. Click the **Close** button.

</details>

<details>

<summary>Cardholder Enrolment Troubleshooting</summary>

The following table describes some of the known issues that can occur during the process of enrolling Cardholders in Gallagher Command Centre, and possible solutions:

<table><thead><tr><th width="240">Problem</th><th>Solution</th></tr></thead><tbody><tr><td>Unable to enrol a cardholder successfully</td><td><p>Try the following, (i.e. try the first option. If that fails, try the next):</p><ol><li>Try enrolling the same fingers.</li><li>Try enrolling different fingers.</li><li>Lower the finger quality threshold.</li><li>Provide the user with a Morpho “Card Number Only” Mifare card and set the reader to “User Selects” authentication mode (on the <strong>Setup</strong> tab of the reader properties). This allows the particular user to use a card to gain access at the Morpho reader.</li></ol></td></tr><tr><td>Cardholder is enrolled but gets rejected access at a reader</td><td><p>Try the following, (i.e. try the first option. If that fails, try the next):</p><ol><li>Check the carhdolder has enrolled biometrics, and that they have access to the the zone.</li><li>Attempt re-enrolment with greater Finger quality threshold (on the Morpho Biometric Capture screen), by moving the slider bar to the right during enrolment.</li><li>Try enrolling different fingers. The middle and thumb are typically the best.</li><li>Consider lowering the reader False Acceptance Rate (FAR) by one notch, (e.g. &#x3C; 0.001% to &#x3C; 0.01%).</li><li>Provide the user with a Morpho “Card Number Only” Mifare card and set the reader to “User Selects” authentication mode (on the <strong>Setup</strong> tab of the reader properties). This allows the particular user to use a card to gain access at the Morpho reader.</li></ol></td></tr><tr><td>The following error message displays:<br><em>"Failed to capture biometrics - Unspecified Error.</em><br><em>Please refer to the 'Troubleshooting - Morpho Biometrics' section in the User Guide."</em></td><td><strong>Possible cause:</strong><br>Although you have Morpho in your license file, you have not yet completed any Morpho setup other than creating a Morpho Biometric card type.<br><strong>Solution:</strong><br>Complete all other Morpho configuration required.</td></tr><tr><td>A card cannot be encoded with biometric data</td><td><strong>Possible cause:</strong><br>There is no dongle in the machine encoding the card.<br><strong>Solution:</strong><br>Obtain and install a dongle in the machines used for encoding cards.</td></tr><tr><td>The following error message displays:<br><em>"Failed to capture fingerprints.</em><br><em>Reason: Device dll or one of it's dependencies is missing or not registered."</em></td><td>The following need to be installed from the 'Morpho Utilities\Microsoft Visual C++ Redistrib (x86 &#x26; x64)' folder of the Command Centre installation files:<br><strong>For Server Workstation:</strong><br>+ Microsoft Visual C++ 2005 Redistributables (x86 &#x26; x64)<br><strong>For Client Workstation:</strong><br>+ Microsoft Visual C++ 2005 Redistributables (x86 &#x26; x64)<br>+ Microsoft Visual C++ 2010 Redistributables (x86 &#x26; x64)</td></tr><tr><td>The following error message displays:<br><em>"Card &#x3C;number> can not be encoded as the compressed biometrics for Cardholder, Sample are not available. Please consult the documentation for more information."</em></td><td><p><strong>Possible cause:</strong><br>The reason for this message appearing is either because:</p><ul><li>the fingerprints need to be compressed using the Compression Utility if no dongle on the encoding station is present, OR</li><li>there is no dongle attached.</li></ul><p><strong>Solution:</strong><br>Compress and store fingerprints on the server using the CompressFingerprints Utility. Refer to the <strong>CompressFingerprints Utility Release Note.pdf</strong> (in the <strong>Morpho Utilities.zip</strong> of the Command Centre installation files) for further details.</p></td></tr></tbody></table>

### Multi-server systems

In a multi-server system each server has its own unique Morpho Biometric Type configurable for biometric inactivity. As a result, biometric inactivity is managed by each server independently, using the Morpho Biometric Type configuration unique to each server. This could result in the following issues occurring:

* A Cardholder who moves from one site to another might find their biometrics inactive as the biometric inactivity does not take into account the Cardholder’s activity throughout the entire system.
* How biometric inactivity is configured could conflict between sites, resulting in an inconsistent user experience, (e.g. biometric inactivity turned "on" on one server and "off" on the other, or with differing inactivity expiry durations).

</details>


---

# 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/command-centre-client/using-command-centre/working-with-viewers/tile-actions/cardholder-biometrics-tile-actions.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.
