> 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/cc-software/operate/encoding-kiosk-application.md).

# Encoding Kiosk application

The Encoding Kiosk Application writes **third-party (non-Gallagher) card data** onto Gallagher data on a card, so the card works at Gallagher-controlled doors. It can also write Gallagher data to a **second Gallagher sector or application** (for a card that must work at two Gallagher sites), or third-party to third-party.

{% hint style="info" %}
This feature is **not tied to any Command Centre version**. The software versioning and release-note titles wrongly suggest otherwise, but it can encode cards for use with **any** Command Centre version.
{% endhint %}

## Licence

`CommandCentre.lic` must contain:

```
[Features]
Encoding=1
EncodingKioskApp=1
```

## Two main use cases

1. **Third-party to Gallagher:** re-write existing third-party card data to a new Gallagher sector or application (same card number), so the card works at Gallagher doors.
2. **Gallagher to Gallagher:** re-write existing Gallagher data to a second Gallagher sector or application (same card number, different keys or facility code), so the card works at two Gallagher sites.

The process overviews below are illustrative only. Refer to the release notes for detailed steps.

### Third-party to Gallagher (in the Encoding Kiosk configuration utility)

1. Configure a **Third-Party Card Format** matching the third-party card data.
2. Configure a **Credential** for the third-party data to be read: Card Technology (MIFARE DESFire or Classic), the Third-Party Card Format, and the keys used to encode the third-party data.
3. Configure a **Credential** for the Gallagher data to be encoded: the same Card Technology, and the keys of the destination Gallagher site.
4. Configure **Mappings**: the sector or application to read from, the Facility Code accepted on read, and the Facility Code used on encode.
5. Configure a **Channel**: source third-party credential, destination Gallagher credential, and the encoding mappings used when the source credential is detected.

### Gallagher to Gallagher

1. Configure a **Credential** for the Gallagher data to be read: Card Technology, and the keys used for the original encoding.
2. Configure a **Credential** for the Gallagher data to be encoded: the same Card Technology, and the keys of the second Gallagher site.
3. Configure **Mappings**: the sector or application to read from and write to, and the Facility Code accepted on read and used on encode.
4. Configure a **Channel**: source and destination Gallagher credentials plus mappings.

***

🔗 **Related**

* [Auto Generated PDF](/knowledge-hub/products/cc-software/operate/auto-generated-pdf.md). Another Access Management Solutions feature.


---

# 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/cc-software/operate/encoding-kiosk-application.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.