> 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/printing-and-or-encoding-a-card-from-a-cardholder.md).

# Printing and/or Encoding a card from a cardholder

### Introduction

This procedure enables an operator to select a cardholder and either:

* print a card,
* encode a card, or
* print and encode a card.

You require either the "Print/Preview & Encode Card" or "Allows Re-Printing and Re-Encoding" operator privilege to view/edit a card, regardless of the card type setting. To print/preview and/or encode cards you must be in the same division as the Card Type of the card for the cardholder selected.

Operators with "View PINs" privilege in a division can view System Generated PINs assigned to cardholders. Whether this privilege works for User Defined PINs is controlled by a setting in the Server Properties, (i.e. the **Store PINs for later viewing** option on the **Card Security** tab), which controls whether the PIN is actually stored and encrypted for later decrypting and display.

**Note:**

If you are going to be encoding Morpho cards you do not need to have the Facility Code in the license file. However, if you are going to be encoding both Morpho **AND** Gallagher data, the Facility Code will need to be in the license file.

### Procedure

1. Click **Manage** from the menu bar, then **Cardholders**.

   The **Cardholder** List Window opens (in [grid view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/grid-view.md)).

   **Note:** Alternatively, you can locate the Cardholder by using the Find Tool. Refer to [Find Tool](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-monitoring/find-tool.md) for further detail.
2. **Right click** on the required cardholder, and select the required option from the context menu:

   * **Print Cards**
   * **Encode Cards**
   * **Print and Encode Cards**
   * **Quick Print Card**
   * **Quick Encode Card**
   * **Quick Print and Encode Card**

   **Notes:**

   * The Print/Encode options will be disabled if the Cardholder does not have any cards issued to them.
   * The “quick” options for printing and/or encoding cards are there to help speed up the process, however for them to work effectively the following configuration needs to be in place first:
     * the “Reason for printing” is not configured as compulsory
     * that a card has already been printed so that a default printer is known, and
     * the cardholder only has one card
   * If the card has previously been printed or encoded the relevant "quick" options will not be available, unless the Card Type has **Allow re-printing** or **Allow re-encoding** enabled. You will not be able to re-print/re-encode a card using a Card Type that does not allow re-printing/re-encoding, unless you have the "Allows Re-Printing and Re-Encoding" privilege, in which case using **Print** or **Encode** will prompt you to 'Proceed' or 'Cancel'. With re-encoding, if you have the "Edit Cardholder" privilege you are prompted to increase the Issue Level, and if you have both the "Edit Cardholder" and "Allows Re-Printing and Re-Encoding" privileges you can either increase the Issue Level or 'Proceed'.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-720c5767a2990414bcb406505cc95fefaf14c8b6%2Fencodingmenu.png?alt=media)

   The **Print/Encode** tab of the Cardholders properties displays, showing the option you selected in the **Action** field.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f3b11707a546b1b62999fae1fdb9a1bebb0bbc99%2Fchold_printencodetab.png?alt=media)
3. If the Cardholder has several cards issued (via the **Cards** tab), select the card you want to preview from the **Card** drop-down list.

   **Note:** If you are not in the same division as the Card Type of the card, the following error message will display:

   *“This card type is not available from the current division."*
4. If you want to preview the card layout before printing/encoding it, click the **Preview** button.

   The **Print Preview** window displays.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-b4b555f4a2ab22f3ef34bfe2d374ed24d51b2a77%2Fcardpreview.png?alt=media)

   **Note:** If this card layout is double-sided, 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 to select the other side of the card so you can preview that also.
5. Is the card preview acceptable?

   <table><thead><tr><th width="90">If...</th><th>then...</th></tr></thead><tbody><tr><td>yes</td><td>click the <strong>Close</strong> button.</td></tr><tr><td>no</td><td><p>you will need to go to the Card Type to edit the layout.</p><p>See <a href="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">Opening the Card Editor window</a> for further details.</p></td></tr></tbody></table>
6. Select the required device to be used for card printing/encoding from the **Device** drop-down list of available printers/encoders.

   The system will remember this printer and default to it every time you preview/print a card until you change it again using the same procedure.
7. Click the **Setup...** button to alter the printer settings if necessary, then click the **OK** button.

   **Note:**

   If you are encoding a MIFARE card, using a serial MIFARE encoder, you need to select the port that the encoder is connected to. To do this:

   1. Click the **Setup...** button to display the Printer properties.
   2. Click the **Encoding** tab.
   3. Select the port the encoder is connected to from the drop-down list.
8. Select the appropriate reason for printing/encoding from the **Reason** drop-down list, or type your own reason into the text field. The reason selected will be logged in the event details.

   **Note:**

   The **Start** button will be disabled until a reason is entered if the **Operator must provide a reason for printing or encoding a card** checkbox was checked on the Photo ID Configuration window when "Reasons for Printing" were configured.
9. The **PIN selection** section of the window will be enabled if you are encoding the card and PINs have not been disabled on the **PINs** tab of the Card Type.

   Either:

   * manually type a PIN number into the **User PIN** field, and then retype it into the **Confirm** field that displays.

     **Note:** As you enter the PIN it will display as a row of dots. The maximum PIN length is 8 digits. There is no mechanism to reduce the maximum size. Hence if a site sets minimum at 4, the user can enter PIN length anywhere from 4 to 8 digits, OR
   * click the **Generate PIN** button to automatically generate a random PIN.

     **Note:** Generated PINs will only display in the **User PIN** field while the window remains open. There will be no way of re-viewing the PIN number since the PIN itself is not stored. Generated PINs will be of length equal to the minimum PIN length set against the Card type.

   **Note:** The system prevents PINs with 3 consecutive or 3 repeating numbers from being either manually entered or automatically generated.
10. To view or hide the PIN click the **View PIN** / **Hide PIN** button.

    If you click the **View PIN** button, the User PIN displays and an event is logged to say you viewed PINs.

    By clicking the **Hide PIN** button, the PIN number disappears again.

    **Note:** If the PIN has not been stored and encrypted (via the setting in the Server Properties), the following dialog will display instead of the User PIN:

    *"The PIN for this card is not stored in a retrievable form."*
11. Click the **Start** button.

    **Note:** If this card has already been printed/encoded, the message *"The selected card details have already been \[printed/encoded]."* displays. In addition to this:

    <table><thead><tr><th width="384">If cards of this type...</th><th>the message will also say...</th></tr></thead><tbody><tr><td>have <strong>not</strong> been configured to allow them to be re-printed and/or re-encoded,</td><td><p><em>"Would you like to increase the issue level?".</em></p><p>Clicking the <strong>Yes</strong> button increases the issue level by 1.</p></td></tr><tr><td>have been configured to allow them to be re-printed and/or re-encoded, and you have the "Allow Re-Printing and Re-Encoding" operator privilege,</td><td><p><em>"Would you like to proceed anyway?".</em></p><p>Clicking the <strong>Yes</strong> button re-prints and/or re-encodes the card with the same issue level.</p></td></tr></tbody></table>

### Result

The result will depend on the option chosen at Step 3, as follows:

<table><thead><tr><th width="168">Option</th><th>The card...</th></tr></thead><tbody><tr><td>Print Cards</td><td>prints to the default printer.</td></tr><tr><td>Encode Cards</td><td>is encoded by the default printer.</td></tr><tr><td>Print and Encode Cards</td><td>is encoded and prints to the default printer.</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/printing-encoding-cards/printing-and-or-encoding-a-card-from-a-cardholder.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.
