> 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-reference-information.md).

# Bureau Encoding reference information

Understand Bureau Encoding capabilities, restrictions, supported card technologies, and licensing limits.

Bureau Encoding allows MIFARE card technologies to be encoded locally on a Channel Partner's dedicated Command Centre system, using a supported printer/encoder or a Gallagher USB encoder. It is designed for off-site encoding of customer cards. It is not designed to run a site's access control.

### Advantages

1. The Channel Partner for a site can encode cards on demand for a site.
2. The Bureau Encoding software will update as Command Centre is upgraded, unlike Encoder 3.
3. Bureau Encoding allows the encoding of MIFARE Plus and DESFire technologies.
4. You can encode Non-Diversified DESFire and ASCII DESFire objects on the DESFire card while encoding.
5. Each site can have unique Site Keys for Plus and DESFire technologies.
6. You can also print cards with Bureau Encoding.

### Limitations

1. The Bureau Encoding System **cannot** be used as a site's Access Control system.
2. A Channel Partner's *Demo* system **cannot** be used.
3. It cannot have customisations added to it, unless they are related to encoding.
4. It must have a Key controller that is dedicated to the system.
5. It can only encode MIFARE technology (Classic, Plus and DESFire).
6. Licence expiry is set for 12 months maximum.
7. Card Serial Number (CSN) is not captured by Bureau Encoding.
8. Salto and Morpho objects cannot be encoded by Bureau Encoding.

{% hint style="info" %}
There is an option to have the Bureau Encoding option on a Channel Partner's own building access control system, but with restrictions:

* The site system should not be used as a test environment.
* Limitations 4 through 8 above still apply.

The main reason for these limitations is that Bureau Encoding records the cards that have been encoded, and is capable of collecting and securely storing the customer Site Specific Keys in the database. Rolling back to a past backup could cause records to become inaccurate.
{% endhint %}

***

🔗 **Related**

* [Bureau Encoding How to Use](/knowledge-hub/products/cc-hardware/credentials/encoding-solutions/bureau-encoding/bureau-encoding-how-to-use.md). Obtaining the licence, setting up card types, and encoding DESFire and MIFARE Classic cards.
* [Credentials - Keys](/knowledge-hub/products/cc-hardware/credentials/credential-information/credentials-keys.md). What the Card Master Key, Default Application Key, and Site Specific Key each do.
* [Encoder 3 Overview](/knowledge-hub/products/cc-hardware/credentials/encoding-solutions/encoder-3/encoder-3-overview.md). The legacy encoding application Bureau Encoding replaces for MIFARE work.


---

# 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-reference-information.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.