> 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/encoding-troubleshooting/encoding-troubleshooting-reverting-to.md).

# Revert to Gallagher Default Keys

Export current keys before reverting a site to Gallagher Default MIFARE keys.

Reverting to Default Gallagher Keys can be done. Before doing so it is **essential** to export the current keys to a file, so the Channel Partner can revert if the cards are not using the Gallagher Default Keys.

Valid reasons for using the Gallagher Default MIFARE keys include multi-tenanted buildings, and sharing cards across multiple sites.

{% hint style="warning" %}
Always export current keys to a file before reverting. If site cards are encoded with custom Site Specific Keys and you revert without a backup, those cards will stop working and the keys cannot be recovered.
{% endhint %}

***

🔗 **Related**

* [Encoding Troubleshooting - Putting Site Specific Keys on a Cardax IV connected T series reader](/knowledge-hub/products/cc-hardware/credentials/encoding-solutions/encoding-troubleshooting/encoding-troubleshooting-putting-site.md). The Admin Card method for readers that cannot receive keys over Cardax IV.
* [Credentials - Site Specific Key (SSK) vs Default Site Key](/knowledge-hub/products/cc-hardware/credentials/credential-information/credentials-site-specific-key-ssk-vs-d.md). Confirming which key set a site is currently using.
* [Credentials - Rolling keys on cards issued to a new site with a SSK](/knowledge-hub/products/cc-hardware/credentials/credential-information/credentials-rolling-keys-on-cards-issu.md). The fix when cards were encoded with the Default keys.


---

# 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/encoding-troubleshooting/encoding-troubleshooting-reverting-to.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.