> 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/idemia-readers-morpho-extended-licenses.md).

# Extend an IDEMIA reader database

Apply a reader-specific IDEMIA license to increase biometric template database capacity.

A reader's user database can be extended by loading an Extended Database Licence. The licence is **reader-specific**, so the reader **License ID** on its label is required to purchase.

### Default user databases

| Reader                                  | Default user database | Expandable to |
| --------------------------------------- | --------------------- | ------------- |
| MA Sigma Lite and MA Sigma Lite + Multi | 500                   | 10,000 users  |
| MA Sigma Multi                          | 5000                  | 50,000 users  |
| MA VP Dual Finger Vein Reader           | 5000                  | 10,000 users  |

Default database sizes for current readers are in the function table on [IDEMIA reader compatibility and specifications](/knowledge-hub/products/integrations/third-party-readers/idemia-morpho/reference/idemia-readers-supported-morpho-readers.md).

### Database extension licences

| Part    | Licence                                           | Extends the database to |
| ------- | ------------------------------------------------- | ----------------------- |
| C864106 | MA J/Sigma Lite Reader Database Extension Licence | 3,000 users             |
| C864114 | MA 5xx/ MA Sigma Multi Extended Database Licence  | 50,000 users            |
| C864107 | MA VP / SIGMA 10K USER LICENSE                    | 10,000 users            |

### Requirements

* Morpho License Manager **4.10.0 to 6.1.0**. It is in the Morpho Utilities folder of the Command Centre installation media, vEL7.80 and above. For License Manager 6.3.0+, use **MBTB 4.8.0+** instead.
* The matching licence: an Extended Database licence that matches the Morpho reader License ID.
* Network to the reader: PC network connectivity to the Morpho readers on **port 11010**.

### Apply the licence with MBTB (License Manager 6.3.0 and above)

Use **MBTB (Morpho Biometric Tool Box) 4.8.0 and above** to add the extended template licence directly to the reader. Select the licence file with **Browse**, then select **Add Licenses**. Once added, the licences are displayed in the list and updated immediately.

### Apply the licence with MultiProtect License Manager 4.10 to 6.1.0

{% hint style="info" %}
This method is supported **until version 6.1.0** of MultiProtect License Manager. If you use an unsupported version, use **MBTB 4.8.0 or above** instead.
{% endhint %}

1. Install Morpho License Manager version 4.10.0 on your server, from the Command Centre installation media vEL7.80 and above. You can also install it on a laptop or PC, as long as it has network connectivity to the Morpho readers.
2. Open Morpho License Manager, right-click in the empty white space and choose **Select a Morpho Access**.
3. Enter the IP address of your Morpho reader and select **OK**.
4. The "Morpho Access" reader serial number is displayed. It matches the License ID printed on the reader's label.
5. Select **Add Licence** and browse to the Extended Database licence for the reader you are connected to. The licence number matches the Morpho Access serial and the reader's License ID.
6. Select **Add**. A confirmation window says "Licence has been correctly set."
7. The Morpho Access licence displays the new user database size.
8. In the Command Centre Configuration Client, right-click the reader and choose **resync database**.
9. Open the Morpho reader properties. The **Status and Overrides** tab then shows the new user database size.

### Reader replaced?

**Reader replaced?** Email IDEMIA (via your Gallagher representative or SOM) with the reader type, the old and new License IDs, and the IDEMIA RMA number to move the licence. Ask for the extension licences to be swapped to the new reader(s), and list the old and new readers in this form:

| Reader #  | Type of reader   | Old reader's License ID                | IDEMIA RMA# | New reader's License ID                |
| --------- | ---------------- | -------------------------------------- | ----------- | -------------------------------------- |
| Example 1 | Morph Sigma Lite | mso\_#########-###########-########### | ######      | mso\_#########-###########-########### |


---

# 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/idemia-readers-morpho-extended-licenses.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.
