> 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-software/reference/command-centre-licencing.md). # Command Centre Licensing Understand Command Centre licence types, capacity limits, features, and upgrade eligibility. Command Centre has an entry-level structure that extends to large enterprise-wide capacity and functionality through licensing. The `CommandCentre.lic` file controls what the software can do. *** ## Command Centre licence types | Part number | Name | Description | | ----------- | ----------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- | | C201311 | Standard Command Centre | Standard licence for all enterprise sites. Additional items are purchasable. | | C302401 | Starter Kit System | Lets small sites get up and running easily. | | C201611 | High Security | For approved High Security installations. | | (none) | Demo | Free. Issued to test and demonstrate new versions, features, and functionality. All limits and features enabled at no charge with a limited expiry. | | (none) | Server Test | Free. Used in a development or sandpit environment to test features or upgrades. Typically an exact copy of the site's Server licence. | *** ## What does the licence file hold? | Licence area | Description | | -------------- | ------------------------------------------------------------------------------------------------- | | Serial Number | Each site has a unique serial number (e.g. 12345). | | Expiry | New site licences run 30 years or more; demo licences run 6 months. | | Version | The version of Command Centre the site is entitled to run. | | Limits | Configurable quantities: number of doors, workstations, mobile credentials, and so on. | | Features | Features that can be enabled and configured: encoding, card printing, cardholder sync, and so on. | | Customisations | Purchasable customisations: Alcolizer, video management systems, and so on. | | Plugins | Used by the Gallagher Controller API to enable functionality (e.g. ASCII). | | Key Device | The licence is tied to physical controllers on a site by **MAC address**. | | Encoding | Facility Codes and Crypt Seeds are recorded to control card encoding and protect site PINs. | | Certificate | Prevents licence tampering. **If the certificate is not correct, Command Centre will not start.** | *** ## What are the server licence defaults? Every server licence ships with the following by default: | Item | Default | | ------------------ | --------------------------------------------------- | | Doors | 16 for Standard server licences, 8 for Starter Kits | | Workstations | 1 (additional to the server) | | Competency | 1 | | Notifications | Can be configured | | Fence Zones | 6 can be configured | | Mobile Credentials | 10 can be used | | Mobile Clients | 1 can be used | | Guard Tours | Can be configured | | Bulk Config Tool | Can be used to configure a site easily | Anything beyond the defaults (extra doors, workstations, fence zones, mobile credentials, customisations) is a purchasable line item on top of the base licence. *** ## What is CarePlan? A **CarePlan** agreement is required for a site to stay current with new versions. * All new server licences with the default limits and features get **free CarePlan**. * Others get the **first year free**. * Annual CarePlan renewals can be purchased. CarePlan eligibility is what entitles a site to version upgrades. *** ## How to update a licence? * **Purchasable changes** (more doors, features, customisations) must go through the site's nominated **Channel Partner**, who sends them to the **Sales Support** team. * **Demo changes and version upgrades** (for sites with eligible Care Plan) also go through the nominated Channel Partner and can be sent to the **Technical Support** team. *** 🔗 **Related** * [Command Centre - Supported Printers](/knowledge-hub/products/cc-software/configure/command-centre-supported-printers.md). Card printing and encoding, one of the licensable features. --- # 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-software/reference/command-centre-licencing.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.