> 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.md).

# Printing/Encoding Cards

### Introduction

An operator with the correct privileges can configure card layouts, as well as print and/or encode card layouts.

**Notes:**

* To be able to encode cards, your site must have Photo ID with card encoding included in their license file. The license file must also include a valid Facility Code before you can encode cards with Gallagher data, and a key device, (e.g. Controller) must be on line.
* Gallagher Command Centre allows up to 256 Facility Codes.
* Printer/encoder drivers are **not** provided with the Command Centre installation files. Therefore, they need to be sourced and installed separately.
* If your site is using Gallagher, Salto and Morpho Biometric readers, cardholders can be issued with a single MIFARE SmartCard for access at all these readers. However, encoding of all three types together on the same card layout is only possible on 4k MIFARE cards. Refer to [Working with Objects](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/card-layouts-designing-printing-encoding/designing-card-layouts/working-with-objects.md) for further detail regarding adding these objects to card layouts.
* The EDIsecure RTP8500/XID8500 printer is capable of Magstripe encoding. If you require Magstripe encoding, open the Printing Preferences of the RTP8500/XID8500's Printer Properties, and for the Card Type, tick the **Magstripe** checkbox.

**Notes regarding MIFARE Enhanced Security feature**

* We recommend that all new Command Centre sites using MIFARE readers set a MIFARE Enhanced Security Key **before** any cards are encoded for the site, even if you do not intend using the MIFARE Enhanced Security feature.

  This gives you the option to implement the MIFARE Enhanced Security feature on your readers at a future date, whereas if you do not do it immediately, you will have to re-encode all cards. Refer to [Card Security](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/card-security.md) for further details.
* Sites using the MIFARE Enhanced Security feature, and purchasing pre-encoded cards from a third party, (either from Gallagher or from a supplier who encodes cards for them), need to provide the third party with the exported MIFARE Site Keys and password to allow the cards to be encoded with the enhanced MIFARE security.
* Cards encoded at sites using the MIFARE Enhanced Security feature can be used at sites that are not using this feature. However, cards not encoded with the high-security data or encoded using a different key seed will not work at a site using the MIFARE Enhanced Security feature, except on readers where the "Require Enhanced security MIFARE encoded cards" checkbox is unchecked (on the readers **Connections** property page).

When a card is printed, an event is generated in the Event Viewer window. The event details:

* the card type and the card number
* who printed the card
* which cardholder had a card printed, and
* the reason for printing the card, if this is configured for Photo ID.

### Hint:

Before printing a card type for the first time, it is recommended you test the layout by previewing the card for a cardholder with quite a long name. This will ensure that the layout will display both long and short cardholder names in a presentable manner.

Select the item below that you require further detail on:

* [Adding Reasons for printing](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/card-layouts-designing-printing-encoding/printing-encoding-cards/adding-reasons-for-printing.md)
* [Printing and/or Encoding a card from a cardholder](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/card-layouts-designing-printing-encoding/printing-encoding-cards/printing-and-or-encoding-a-card-from-a-cardholder.md)
* [Encoding MIFARE cards to operate on multiple Command Centre sites](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)


---

# 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.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.
