> 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/configuration-client/introduction-to-command-centre/introduction.md).

# Introduction

#### Command Centre System

Command Centre is a comprehensive access control, alarm monitoring and security management system designed to satisfy the most stringent security requirements.

Control of the Command Centre system is via intelligent 32 bit field devices called Gallagher Controllers. These devices link to a central computer called the Command Centre Server.

#### Command Centre Server

The Command Centre Server runs on a personal computer (PC) under any of the following Microsoft operating systems:

* Windows Server 2025,
* Windows Server 2022,
* Windows 11 Pro/Enterprise,
* Windows Server 2019

**Note:** Windows 10 Pro N and 11 Pro N are NOT supported operating systems.

The Command Centre Server is a background application which drives Command Centre Workstations.

The use of a USB mouse for the Server is highly recommended. This is because USB devices support hot swapping, whereas Ps2 devices require a shutdown and restart of the Server in the event of a mouse failure.

#### Command Centre Workstations

The Command Centre Workstation is the user interface to the Command Centre system. Command Centre consists of two clients, (i.e. Gallagher Configuration Client and Gallagher Command Centre Client).

Workstations are connected to the Command Centre Server via the network. Through the workstations, operators can monitor, modify and manage the entire system, or selected parts of it, depending upon their allocated privileges.

**Note:** Microsoft Windows allows the size of text and other items to be changed via **Control Panel** > **Display**, however Command Centre does **not** support alternate icon sizes, (i.e. only the default option of 100% is supported).

#### Foreign Languages

While English is the default language for Command Centre, there is the ability to translate it into other languages. Languages are a licensable feature, and only [dialects](https://help.security.gallagher.com/knowledge-hub/configuration-client/glossary-of-terms.md#dialect) and languages listed in the 'Language' key in the license file are available to a site. All sites are by definition licensed for the fallback language, even if the fallback language is not specifically mentioned.

#### This help file

This help file describes the operation of the Command Centre Workstations and the actions the operators can perform in Configuration Client only. There is a separate help file for Command Centre Client, which is available by clicking the ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-21696e72ec0a06324b205d044b43d8eb573a6bd7%2Fsystemoperatorbutton.png?alt=media) button on the toolbar, then **Help**, or by pressing < **F1** > within Command Centre Client.

#### Command Centre database integrity recommendations

Sites have full access to the Command Centre databases. This means administrators can grant local and/or domain Windows users access to edit, manage and maintain the SQL Instance and attached Gallagher (CCFT) databases.

**Customer Responsibilities**

As per the Software License and Maintenance Terms and Conditions accepted upon installation of Command Centre, Gallagher will not be liable in any circumstances for the loss or corruption of data.

It is the responsibility of the customer to:

* Not modify any Data, Metadata or Schemas in the Gallagher Command Centre databases by any method other than via the Gallagher Command Centre Application.
* Not share the database instance with other services.
* Not upgrade the databases while in Availability groups.
* Implement appropriate measures to ensure adequate levels of data security.
* Manage, monitor and maintain their Gallagher Command Centre databases, this includes backups (scheduled and manual), archiving and database transaction log files.
* Accept full responsibility for any data loss or corruption associated with the unauthorized modification of data or schemas within the Gallagher system.
* Accept that if the event data is required for legal purposes, Gallagher will be unable to verify that the data has not been altered by an unauthorized method, or software outside the Gallagher Command Centre application.
* Communicate promptly and completely in response to all issues and requests for information from Gallagher.

**Support Approach**

Support requests resulting from the tampering, corruption, failure to maintain transaction log files or unauthorized modification of any Gallagher system Data or Schema will be at the Customers full cost where possible.


---

# 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/configuration-client/introduction-to-command-centre/introduction.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.
