> 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.md). # Command Centre Software Configure, operate, and troubleshoot Gallagher Command Centre software. Command Centre is Gallagher's security management platform, the central software that brings **access control**, **intruder alarms**, **perimeter security**, and **building management** together in one interface. It scales from a single-door site to thousands of doors across multi-site enterprises, with twice-yearly feature releases. ## Three security domains under one roof * **Access control** - controllers, readers, credentials, doors, cardholders. * **Perimeter security** - fence energisers, sensors, gate hardware. * **Intruder alarms and building management** - zones, schedules, action plans. ## High level architecture [Command Centre system architecture diagram (PDF)](https://media.gallagher.com/m/33c0504caaa65a8c/original/System-Architecture-Diagram-Public-System-Architecture.pdf) shows how the server, controllers, and field hardware connect.
LayerWhat lives here
Server / SaaSCommand Centre, the management software itself. On-premise (typical), air-gapped, or cloud SaaS.
ControllersIP-based field controllers between server and field hardware. The C7000 is the current enterprise controller; the C6000 is current but SMB-only in scope.
Field hardwareT-Series readers, perimeter fence controllers, I/O modules, sensors, and monitored pulse fences.
ProtocolsBertbus (legacy), HBUS (current), MQTT 5.0 (internal), REST (external integrations).
CloudCloud API Gateway for remote integrations without firewall configuration; Mobile Connect for the cardholder credential app.
Command Centre is being modernised from a Windows thick-client model to a **web-based four-workspace model**. Both states matter, because the legacy clients are still in the field and the workspaces shape what is coming. **Today's clients:** * **Command Centre Client** - Windows thick client for operators and admins. * **Configuration Client** - installer and integrator tool for deep configuration. * **Command Centre Mobile Client** - guard mobile app. * **Mobile Connect** - cardholder credential app for end users. --- # 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.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.