> 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/adding-reasons-for-printing.md).

# Adding Reasons for printing

### Introduction

This procedure enables an operator with the "Edit Site" operator privilege in the root division to manage a list of reasons for printing a card.

### Procedure

1. Click **Configure** from the menu bar, then **Photo ID**.

   The Photo ID Configuration window displays.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-45a40f1edb55e8b837befb7c67900c2a4d4234ac%2Fphotoidconf.png?alt=media)
2. Check the **Operator must provide a reason for printing or encoding a card** box, if required.
3. Click the **New\...** button, and type in your reason for printing a card.
4. Repeat Step 3 for each additional reason.
5. Click the **Close** button.

### Result

A list of 'Reasons for Printing' cards is created.

### Hints

{% hint style="info" %}
**Editing a Reason for Printing**

1. Highlight the reason you wish to edit.
2. Edit as required and click the Close button.
   {% endhint %}

{% hint style="info" %}
**Deleting a Reason for Printing**

1. Highlight the reason you wish to delete.
2. Press the **Delete** key on your keyboard.

   Note: You are not asked for confirmation. The reason is deleted when you press **Delete**.
3. Click the Close button.
   {% endhint %}


---

# 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/adding-reasons-for-printing.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.
