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

# Card Layouts - Designing / Printing / Encoding

### Introduction

The following functions all relate to card layouts, and are available in Command Centre, providing your site has the correct license options. Select the item below that you require further detail on:

* [Overall Process](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/card-layouts-designing-printing-encoding/overall-process.md)
* [Designing card layouts](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/card-layouts-designing-printing-encoding/designing-card-layouts.md) (using the Photo ID feature in Command Centre)
* [Printing/Encoding Cards](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/card-layouts-designing-printing-encoding/printing-encoding-cards.md)
* [Batch Printing and/or Encoding](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/card-layouts-designing-printing-encoding/batch-printing-and-or-encoding.md) (covers printing/encoding cards for multiple cardholders, and printing/encoding multiple cards of a particular Card Type)

***

### Licensing

Each function related to card layouts, (i.e. designing card layouts, card printing and card encoding), is an individually licensable feature. There are a number of license options available depending on your site requirements. Therefore, depending on which option your site has could mean that one or more of the options mentioned in this topic may not be available to you. The following table indicates the license options available:

<table><thead><tr><th width="300">To...</th><th>the license file should include...</th></tr></thead><tbody><tr><td>design and print card layouts</td><td><code>[Features]</code><br><code>Photo-ID=1</code><br><code>CardPrinting=1</code></td></tr><tr><td>design, print and encode card layouts</td><td><code>[Features]</code><br><code>Photo-ID=1</code><br><code>Encoding=1</code><br><code>CardPrinting=1</code></td></tr><tr><td>batch print and encode cards for cardholders</td><td><p><code>[Features]</code><br><code>Encoding=1</code><br><code>[Configuration]</code><br><code>FacilityCode=&#x3C;code></code></p><p><strong>Note:</strong> Batch printing and encoding will be restricted to Card Types whose Facility Code appears in the license file.</p></td></tr><tr><td>bureau print and encode cards</td><td><p><code>[Features]</code><br><code>BureauCard=1</code><br><code>[Configuration]</code><br><code>FacilityCode=&#x3C;code></code> OR <code>BureauFacilityCode=&#x3C;code></code></p><p><strong>Note:</strong> Bureau printing and encoding will be restricted to Card Types whose Facility Code appears in the license file (either beside 'Facility Code' or 'Bureau Facility Code').</p></td></tr></tbody></table>


---

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