> 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/batch-printing-and-or-encoding.md).

# Batch Printing and/or Encoding

### Introduction

Operators can set up a batch printing/encoding job for sending to a suitable combined printing and encoding device based on:

* A Card Type plus a range of Card Numbers

  ( **Bureau Batch Job** )
* A selection of cardholders plus a given Card Type(s)

  ( **Cardholder Batch Job** )

**Note:** The MIFARE USB encoder is supported.

### Operator Privileges

Different operator privileges are required for the two types of batch jobs, as follows:

To perform a **Bureau Batch Job** for a Card Type, the Card Type must belong to a division for which you have the “Bureau Batch Printing/ Encoding” operator privilege.

To perform a **Cardholder Batch Job** for a selection of cardholders, the cardholders should all belong to a division for which you have the “Print/Preview & Encode Card” operator privilege. If the selection contains any cardholders belonging to another division, then the Batch Job will proceed but it will exclude these out-of-division cardholders.

### Procedures

Before a Bureau Batch Job can be run, a Card Type needs to be configured so it can be used for Bureau Printing/Encoding. See [Setting a Card Type for Bureau Printing/Encoding](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/card-layouts-designing-printing-encoding/batch-printing-and-or-encoding/setting-a-card-type-for-bureau-printing-encoding.md) next for the procedure.

The procedure for performing a Batch Job has been split into two separate procedures for the two different types of Batch Jobs, (i.e. Bureau and Cardholder).

**IMPORTANT:**

The encoder remembers the last cards serial number that it read or encoded. Therefore, if you set up a job and then cancel it without encoding any data onto the card, it records that cards serial number as being the last one and will not encode it again. In this situation you need to encode a different card first, then put the other card back on the encoder to encode it.

* [Setting a Card Type for Bureau Printing/Encoding](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/card-layouts-designing-printing-encoding/batch-printing-and-or-encoding/setting-a-card-type-for-bureau-printing-encoding.md)
* [Performing a Bureau Batch Job](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/card-layouts-designing-printing-encoding/batch-printing-and-or-encoding/performing-a-bureau-batch-job.md)
* [Performing a Cardholder Batch Job](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/card-layouts-designing-printing-encoding/batch-printing-and-or-encoding/performing-a-cardholder-batch-job.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/batch-printing-and-or-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.
