> 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/card-layouts-designing-printing-encoding/printing-encoding-cards/encoding-mifare-cards-to-operate-on-multiple-command-centre-sites.md).

# Encoding MIFARE cards to operate on multiple Command Centre sites

### Introduction

A site may wish to grant access to MIFARE® cards, (i.e. MIFARE Classic®, MIFARE Plus® and MIFARE® DESFire® cards only) that are being used on another (third party) Command Centre site. There are three ways to achieve this:

* By reading the cards unique id (CSN) if the reader is configured to do so.

  Refer to the 'Use MIFARE Serial Number as Card Data' section, at Step 9 of the [Creating Readers](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/hardware/creating-readers.md) procedure.
* If the default MIFARE Plus/DESFire key seed is used by both sites, then it is possible to create a Card Type with the third parties Facility Code as per existing functionality. In this case it is possible to enrol a third party card onto a site without creating a new card application.
* If the third party site uses a unique key seed, the local site will need to encode their own data onto a sector on the third party cards. This requires the third party cards to have a spare sector available. In addition, the local Command Centre system must have the appropriate key(s) configured to enable encoding of the sector on the third party card.

**Notes:**

* A document providing further detail on MIFARE mulitple applications ( **Sharing MIFARE Classic and Plus cards between sites.pdf** ) is located in the `'Documentation'` directory of the Command Centre installation files.
* Some higher security sites may be unwilling to share the Card Master Key (CMK) with another site. This would cause problems for sites using MIFARE DESFire cards if the CMK is required for encoding. For further detail on the process, refer to **Sharing MIFARE DESFire cards between sites.pdf** located in the `'Documentation'` directory of the Command Centre installation files.


---

# 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/card-layouts-designing-printing-encoding/printing-encoding-cards/encoding-mifare-cards-to-operate-on-multiple-command-centre-sites.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.
