> 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/designing-card-layouts/formatting-cards.md).

# Formatting Cards

### Introduction

This procedure describes how to format Card Type cards or Digital ID Type cards. It enables you to format the card size, orientation and whether the card is double-sided.

### Procedure

1. Open the **Card Editor** window. [How?](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/card-layouts-designing-printing-encoding/designing-card-layouts/opening-the-card-editor-window.md)
2. Click the ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-863a3d3f54942305a90c4536afc7c46ddedf598e%2Fformat.png?alt=media) icon, then **Select Card Format**.

   The **Choose Card Format...** window displays.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-90f06a85fd4538441232aefcbd4403cb7d1a5c4a%2Fcardformat.png?alt=media)
3. Select the **Paper Type** from the drop-down list, (i.e. the size of the card).

   **Note:** For Digital ID Type cards the size affects its display on Mobile Devices.
4. Click the appropriate radio button to indicate the card orientation, i.e. Portrait (tall) or Landscape (wide).
5. Check the **Double Sided** checkbox if required.

   **Note:**

   The orientation has to be the same for both sides of a double-sided card, however by rotating text you could have one side portrait and the other side landscape. Rotation of images is not possible however, therefore if you wish to rotate an image you should do this in the source graphics package.
6. Click the **OK** button.

   **Notes:**

   * If Double Sided is checked, "Reverse Side" is now enabled on the drop-down list from the ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-8cf8c8b9ab3670d3c605af5834c413ca8c5134f6%2Freverse.png?alt=media) icon.
   * "Common Encoding Properties" is another option available from the drop-down list, for MIFARE objects. If an object has not already been added to the card layout, when selected, the Common Card Encoding Properties dialog box opens with the **MIFARE Encoding Technology** field displaying ‘None’ and the following message:

     *"Select a MIFARE encoding technology to continue".*

     Encoding properties will display once a MIFARE technology is selected.


---

# 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/designing-card-layouts/formatting-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.
