> 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/licensable-features/visitor-management/using-visitor-management/receptionist-functions/performing-visitor-actions/capturing-biometrics.md).

# Capturing Biometrics

### Introduction

You can capture the biometric credentials (fingerprints / finger veins) of a visitor on a visit. The biometrics are used to open secure doors on-site. What areas the visitor has access to are defined by the 'Access Groups' selected on the visit.

### Before you begin

Before you begin this procedure:

* A Morpho Biometric Type must already be created. Refer to [Creating a New Morpho Biometric Type](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/morpho-biometric-integration/creating-a-new-morpho-biometric-card-type.md) for the procedure.
* A suitable enrolment device (for capturing fingerprints or finger veins) must be connected to Visitor Management via a USB connection.

### Procedure

To enrol a visitor for a Morpho Fingerprint or Finger Vein, complete the following procedure:

1. Select the visitor's record.
2. Click the **Biometrics** action button.

   The Capture Biometrics window displays.

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

   This window displays the Visitor's name, Arriving and Departing information, and Biometrics, if previously assigned.

   **Notes:**

   * The reception configuration determines if the Biometrics action is displayed or not.
   * To remove a previously assigned fingerprint/vein from the visitor for this visit, click the **Clear** button.
   * The Privacy Settings selected (via the **Advanced** tab of the Morpho Biometric Type) affect what appears on the bottom of this window.
3. Click the **Capture** button.

   The Morpho Finger Capture screen displays.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-95dd922afc0166a2396859ba86acd3a17ac1d83a%2Fsagemfingerprintcapture.png?alt=media)
4. Place the appropriate finger on the enrolment device.

   The percentage bar on the right of the screen indicates how successful the capture is.
5. Repeat Step 4 twice so you have three captures of the same finger.
6. Repeat Steps 3 - 5 for the second finger.

   On capturing two fingers successfully:

   * an image displays under the appropriate Finger on the Capture Biometrics screen to indicate that something has been captured,
   * the **Clear** button (used for deleting the captured biometrics) is enabled, and
   * the **OK** button is enabled.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-29d8ddfa4bfec238fd1a7863edd5cb6f970474da%2Fvm_capture_fingerprints_window2.png?alt=media)
7. What model of Morpho Biometric readers do you have?

   <table><thead><tr><th width="246">If...</th><th>then...</th></tr></thead><tbody><tr><td><strong>MA1xx</strong>, <strong>MA Sigma</strong>, <strong>MA J</strong>, <strong>MA VP</strong> or <strong>MA5xx</strong> without an IDENTPLUS licence</td><td><p>these readers only have one database, therefore the <strong>Reader Database ID</strong> field can be ignored.</p><p>Go to Step 9.</p></td></tr><tr><td><strong>MA5xx</strong> with an IDENTPLUS licence</td><td><p>these multi-database readers have 5 databases that each hold 10,000 sets of fingerprints/veins.</p><p>Go to Step 9.</p></td></tr></tbody></table>
8. Do you expect to capture biometrics for more than 3000 visitors?

   <table><thead><tr><th width="72">If...</th><th>then...</th></tr></thead><tbody><tr><td>no</td><td>enter 0 in the <strong>Reader Database ID</strong> field.</td></tr><tr><td>yes</td><td><p>select an appropriate value in the <strong>Reader Database ID</strong> field between 0 - 15 to indicate which of the 16 databases is to be used. The number of fingerprints/veins in each database can be determined from the reader status screen.</p><p>A value greater than zero will mean that visitors will be required to enter this Database ID using the reader's keypad before placing their finger for identification. For databases 10 - 15, a '#' needs to be entered in place of the '1', (e.g. for database 14, a visitor would enter '#4').</p></td></tr></tbody></table>
9. Do you expect to capture biometrics for more than 10,000 visitors?

   <table><thead><tr><th width="72">If...</th><th>then...</th></tr></thead><tbody><tr><td>no</td><td>enter 0 in the <strong>Reader Database ID</strong> field.</td></tr><tr><td>yes</td><td><p>select an appropriate value in the <strong>Reader Database ID</strong> field between 0 - 4 to indicate which of the 5 databases is to be used. The number of fingerprints/veins in each database can be determined from the reader status screen. A value larger than 4 will be accepted but the fingerprints/veins will be stored in database 0.</p><p>A value greater than zero and less than 5 will mean that visitors will be required to enter this Database ID using the reader's keypad before placing their finger for identification.</p></td></tr></tbody></table>

   **Notes:**

   * The general rule is that database 0 is used to store fingerprints/veins if the Reader Database ID is the same or larger than the number of databases supported by a particular reader. For instance, if a visitor has a Reader Database ID of 10, and has access to both a MA3xx and MA5xx (with IDENTPLUS licence), then database 10 will be used on the MA3xx and database 0 will be used on the MA5xx.
   * The larger an Access Group, the longer it takes to sort and send to the reader.
10. Click the **OK** button to exit and save your changes.

    **Notes:**

    * You will not be able to save the visitor's biometrics if only one 'Main' biometric has been captured.
    * It is possible to report on biometric details in a Cardholder Report. On the first page of the Cardholder Report wizard, (i.e. the 'Report Style' page), there is an **Include Biometric Details** checkbox that can be turned off/on as required.


---

# 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/licensable-features/visitor-management/using-visitor-management/receptionist-functions/performing-visitor-actions/capturing-biometrics.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.
