> 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/deployment-resources/security-and-compliance/gallagher-policies-library/key-device-policy.md).

# Key Device policy

Understand key-device licensing, removal alarms, replacement, and return requirements.

Command Centre is licensed through key devices. A key device is any controller permanently installed and communicating with the Command Centre server. Each site can have one or two key devices, identified in the license file at purchase.

* Failure or removal raises an alarm. Before v7.00, only the *last* key device removed raised an alarm. From v7.00, any key-device removal generates an alarm.
* When the last key device is removed and the license file is not updated or the device is not returned, the system becomes read-only after an elapsed period.
* On a license update due to failure or removal, the Channel Partner must return the key device to the nearest Gallagher regional sales office within 30 days. Gallagher may invoice the Channel Partner for the full cost of the site's Command Centre software.
* Out-of-warranty key devices cannot be repaired or returned. The device must be replaced by the Channel Partner and sent to the nearest Gallagher sales office. See [Support](/knowledge-hub/deployment-resources/support-tools-and-troubleshooting/support.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/deployment-resources/security-and-compliance/gallagher-policies-library/key-device-policy.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.