> 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/communications-encryption/encryption-using-command-centre.md).

# Encryption using Command Centre

This procedure describes how to send the encryption keys and certificates to the biometric readers via the network.

### Procedure

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

   The Card Type List Window opens.
2. **Right-click** on the Morpho Biometric Type and select **Properties**.
3. Click the **Advanced** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-74fef5949a5c576e6d512ecefe4a0a61485ced01%2Fmorphobiometrictype_advancedtab_sendencryption.png?alt=media)
4. Check the **Send encryption keys via network** option.
5. Click the **OK** button.

   The certificates and keys are processed automatically in the background.
6. Go to each reader and ensure the **Encrypt Communications** checkbox is ticked.
7. Check status and overrides to confirm the reader is in "Secure communication".


---

# 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/communications-encryption/encryption-using-command-centre.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.
