> 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/allegion-engage-interface/command-centre-configuration/encoding-gallagher-credentials-to-an-engage-card.md).

# Encoding Gallagher Credentials to an Engage Card

### Introduction

Engage cards can be used for Gallagher readers. This involves setting up two card types, (i.e. an *Engage* Card Type and a *DESFire* Card Type) for a single card to allow the cardholder to access both Engage and Gallagher readers.

### Configuration

1. Click **Configure** from the menu bar, then **Card Types**.

   The **Card Type** List Window opens.
2. Configure an Engage Card Type.

   See [Creating an Engage Card Type in Gallagher Command Centre](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/allegion-engage-interface/command-centre-configuration/creating-an-engage-card-type-in-gallagher-command-centre.md) for the procedure.
3. Create a DESFire Card Type with the correct Facility code on the **Setup** tab, and make sure "Engage Card Type" is unchecked on the **Engage** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f202f321c0809f8b705d3e42f83f2d27162ac8e2%2Fdesfirecardtype4.png?alt=media)
4. Once created, right click on the DESFire Card Type from the **Card Type** List Window, and select **Edit Card Layout**.

   The Card Editor window displays.
5. Select **New MIFARE DESFire Object** ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-b6d106226c6f0254fdddd6a87ae4a6ab3cb822c7%2Fdesfire.png?alt=media)

   An object box displays with placeholders around it.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-b637ac1cca5eeb51ed54bfab798c1e54e8bd6a99%2Fdesfirecardtype.png?alt=media)
6. **Right click** on the MIFARE DESFire object, then click **Common Encoding Properties** from the drop-down menu.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-8f86d6e45cd3bf4a6ebd893928bd11b4243807aa%2Fdesfirecardtype2.png?alt=media)
7. Uncheck the **Gallagher Issued** checkbox, and replace all Fs in the **Default Application Key** field to 0s.

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

   **Note:** If this step is missed, when encoding the DESFire card, the following warning message will display:

   *"Authentication failed with supplied key(s)."*
8. Select a Cardholder which already has the Engage Card Type that was created at Step 2.
9. On the Cardholder’s **Cards** tab, insert the DESFire Card Type that was created at Step 3.

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

   See [Adding a Card to a Cardholder](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/cardholders/adding-a-card-to-a-cardholder.md) for the full procedure if required.
10. Connect the card encoder to the PC and place a DESFire card on the encoder.
11. Click the Cardholder’s **Print/Encode** tab.
12. Select "Encode Card" from the **Action** drop-down list.
13. Select the correct card type from the **Card** drop-down list and click the **Start** button to start encoding.

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

    After card encoding completes the card will allow access at Allegion locks and Gallagher door readers.

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


---

# 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/allegion-engage-interface/command-centre-configuration/encoding-gallagher-credentials-to-an-engage-card.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.
