> 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/products/cc-hardware/credentials/encoding-solutions/bureau-encoding/bureau-encoding-how-to-use.md). # Set up and use Bureau Encoding Request a Bureau license, configure card types and Site Specific Keys, and encode supported cards. How to get a Bureau license, set up card types and Site Specific Keys, and encode DESFire and MIFARE Classic cards on a Bureau Encoding system. {% hint style="info" %} Read [Bureau Encoding - Reference Information](/knowledge-hub/products/cc-hardware/credentials/encoding-solutions/bureau-encoding/bureau-encoding-reference-information.md) first. It sets out what a Bureau system may and may not be used for. {% endhint %} ### Obtain a Bureau license Channel Partners can request a dedicated Bureau license from Technical Support for their own office. These licenses are for encoding only, not access control, and have less functionality than a normal Command Centre license. A dedicated MAC address is required for the system and license. License limits: * `Cardholders=5` * `Controller 3000s=1` * `Controller 5000s=1` * `Workstations=1` * `Divisions=1` * `Doors=1` License features: * `Photo-ID=1` * `Encoding=1` * `CardPrinting=1` * `BureauCard=1` Technical Support can add Facility Codes for the sites managed by the Channel Partner on request. ### Set up card types and Site Specific Keys Once Facility Codes are enabled, card types can be created for each site in Configuration Client. These can be configured as needed: layout, objects, card ranges, and so on. Unique Site Specific Keys (SSK) can be included per card type. The matching password will be needed after selecting the relevant SSK. ![Bureau Encoding step 1](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-3700e935389dfc6c46fc17e3fa54f3d96cfcbb88%2FSECHUB-ENCODING-BUREAU-01-bureau-encoding-step-01.png?alt=media) After the card type has been set up, choose whether to Batch Print, Batch Encode, or both. Then specify the card range and start encoding or printing. ![Bureau Encoding step 2](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-54b88d51850646e014fe7717fcc1feb09b90f589%2FSECHUB-ENCODING-BUREAU-02.png?alt=media) {% hint style="info" %} Encoding Morpho and Salto applications cannot be done on the Bureau Encoding system. These can only be done on-site, as they use information unique to each site. {% endhint %} ### Encode DESFire multiple objects This section applies when you are encoding multiple DESFire applications onto a card, or adding more applications onto a previously encoded card. {% hint style="info" %} In the context of this guide, the Default Gallagher DESFire keys are considered a unique Site Specific Key. {% endhint %} Each Gallagher application must have a unique: 1. Facility Code 2. Unique SSK (Site Specific Key) If this is not met, Gallagher readers may run into issues reading the applications from the card. {% hint style="warning" %} If one of the applications uses the Default Gallagher DESFire keys during initial encoding, and in future this application has its keys rolled to a key that matches one of the other application keys, this will cause access issues due to card reading problems. {% endhint %} #### Add a second Gallagher object onto a pre-encoded DESFire card To perform this action you **must** know or have access to the Default Application Key used to encode the card first. If you don't know this key, you **cannot** encode more objects onto the card. Where to get the Default Application Key: * **Encoded by Gallagher in New Zealand.** Gallagher can supply this key on request. * **Encoded on a Command Centre site.** Go to the site, examine the Server Properties, look under the Card Security tab, and locate the DESFire application key. * **Encoded on a Bureau Encoding system.** It will be the Default Gallagher Default Application Key. When creating the card type in the Bureau Encoding server, uncheck the **Gallagher Issued** checkbox to allow adding the Default Application Key. You will then be able to encode the cards with additional DESFire objects. **Does sharing the Default Application Key affect card security?** The Default Application Key is only there to allow subsequent applications to be added to the card. Knowing the Default Application Key does not affect any current objects on the card already, nor does it allow interaction with the DESFire objects already on the card in any way. ### Encode MIFARE Classic cards Bureau Encoding by default encodes Gallagher data onto sector 15. This can be altered in both Encoder 3 and Bureau Encoding. #### CAD creation Bureau Encoding by default encodes Gallagher data on sector 15, and also adds data in sector 14: the CAD (Card Application Directory). The CAD always precedes the Gallagher encoded data. If Gallagher data was encoded on sector 10, the CAD would be in sector 9. To prevent CAD creation: 1. Add the string `PhotoIDMinimalEncode=1` to the licence. 2. Go to the card type in Bureau Encoding and open its properties. 3. Go to the Printing and encoding tab. 4. Uncheck **Update Application Directory**. ![Bureau Encoding step 5](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-051044235dc2fcac8a2f01f46606af3ad149aef1%2FSECHUB-ENCODING-BUREAU-05-bureau-encoding-final-step.png?alt=media) {% hint style="warning" %} Once the CAD has been written to the card, the entire card must be erased to remove it. Card erasing is not supported by any software, Bureau or Command Centre, but can be done at Gallagher's in New Zealand for a fee. {% endhint %} *** 🔗 **Related** * [Bureau Encoding - Reference Information](/knowledge-hub/products/cc-hardware/credentials/encoding-solutions/bureau-encoding/bureau-encoding-reference-information.md). The advantages and the license restrictions that apply to a Bureau system. * [Credentials - Keys](/knowledge-hub/products/cc-hardware/credentials/credential-information/credentials-keys.md). What the Default Application Key is and why it is safe to share. * [Credentials - Sharing DESFire cards between Sites](/knowledge-hub/products/cc-hardware/credentials/credential-information/credentials-sharing-desfire-cards-betw.md). Using the Default Application Key to share a card between two sites. * [Encoding Kiosk - Adding a Gallagher credential](/knowledge-hub/products/cc-hardware/credentials/encoding-solutions/encoding-kiosk/encoding-kiosk-adding-a-gallagher-cred.md). Adding a second Gallagher object without a Command Centre connection. --- # 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/products/cc-hardware/credentials/encoding-solutions/bureau-encoding/bureau-encoding-how-to-use.md?ask=&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.