> 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/setting-a-card-type-for-bureau-printing-encoding.md).

# Setting a Card Type for Bureau Printing/Encoding

The main purpose of creating Card Types is for access control, however Card Types can also be created for encoding cards for other sites. This procedure describes how to configure a Card Type for Bureau Printing/Encoding.

1. Perform Steps 1 - 12 of the [Setting up Card Types](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/card-types/setting-up-card-types.md) procedure and then go to Step 2 of this procedure.
2. Click the **Bureau Encoding** tab.

   **Note:** This tab will only appear if your site is licensed for Bureau Printing/Encoding.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-80ce9e51c1628ea613d8380d3c4b403933ae9743%2Fbureauprint_bureauencodingtab.png?alt=media)
3. Do you want this Card Type to be used for normal access control as well as Bureau Printing/Encoding?

   <table><thead><tr><th width="78">If...</th><th>then...</th></tr></thead><tbody><tr><td>yes</td><td><p>check the <strong>Allow cards of this card type to be assigned to cardholders</strong> checkbox.</p><p>Cards of this Card Type will be able to be assigned to cardholders and used for normal access control, as well as being available for Bureau Printing/Encoding.</p><p><strong>Note:</strong> By clicking the <strong>Apply</strong> button now, the 'MIFARE Site Key' section disappears from this screen.</p></td></tr><tr><td>no</td><td><p>leave the <strong>Allow cards of this card type to be assigned to cardholders</strong> checkbox unchecked.</p><p>This Card Type will be able to be used for Bureau Printing/Encoding only.</p></td></tr></tbody></table>
4. Is your site Bureau Encoding MIFARE cards?

   <table><thead><tr><th width="78">If...</th><th>then...</th></tr></thead><tbody><tr><td>no</td><td>go to Step 5.</td></tr><tr><td>yes</td><td><ol><li><p>In the <strong>MIFARE Site Key and Encoding Options</strong> section, click the <strong>Import Keys...</strong> button.</p><p>An 'Open File' dialog displays.</p></li><li><p>Path your way to the appropriate MIFARE key file (that was configured on the <strong>Card Security</strong> tab of the Server Properties), and click the <strong>Open</strong> button.</p><p>An ‘Enter password’ dialog displays.</p><p><strong>Note:</strong> If the file selected does not contain exported MIFARE keys, then the error message <em>“The file selected does not contain valid MIFARE site key data”</em> displays instead of the 'Enter password' dialog.</p></li><li>Enter the password that was set for the MIFARE keys on the <strong>Card Security</strong> tab of the Server Properties, and click the <strong>OK</strong> button.</li><li><p>Click the <strong>OK</strong> button.</p><p>The selected file is imported and the encrypted MIFARE key within the file is loaded into memory.</p><p>The message changes to:</p><ul><li><em>"The MIFARE Plus/DESFire key seed for this Card Type will be changed upon applying changes"</em>, AND/OR</li><li><em>"The MIFARE Enhanced key for this Card Type will be changed upon applying changes".</em></li></ul></li><li><p>Click the <strong>Apply</strong> button to send the change to the server.</p><p>The message changes again to:</p><ul><li><em>"A MIFARE Plus/DESFire key seed has been loaded for this Card Type",</em> AND/OR</li><li><em>"A MIFARE Enhanced key has been loaded for this Card Type"</em>.</li></ul></li></ol></td></tr></tbody></table>
5. Click **OK** to exit and save your changes.

   Click **Cancel** to exit without saving your changes.

   Click **Apply** to save your changes and stay in this window.

   **Note:**

   If you decide that you do want this Card Type to be available for access control on your own site, you will need to delete this Card Type and start the procedure again, as it is not possible to re-enable the fields on this screen once they have been saved.


---

# 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/setting-a-card-type-for-bureau-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.
