> 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/cloud-services/web-client.md). # Web Client Manage Command Centre cardholders securely from a web browser. ![Command Centre Web running in a browser on a tablet - cardholder access management screen](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-b4d8fdb818c50c845dcb71a6354312bbbff5d770%2FSECHUB-web-client-01-product-tablet.jpg?alt=media) **Command Centre Web** is the browser-based way to manage a site, with no full workstation install required. From **CC v9.10** it is an **annual subscription, licensed per named user**, and requires an **active Care Plan**. The first package is **Cardholder Management** (**C16051**), which gives remote cardholder admin for reception, guard stations, and anyone who needs cardholder tasks but not full alarm management. ## What it is Command Centre Web provides the flexibility and security to manage a site from anywhere with an internet connection, without setting up or installing a full Command Centre workstation. This saves time and money. The first subscription package, **Cardholder Management**, allows cardholder administration without a full workstation: creating cardholders, managing access and credentials, updating personal data, and viewing activity and history. It suits **reception, public guard stations**, and anyone who performs cardholder management but does not need other security tasks such as alarm management. ## Licensing Requires **Command Centre v9.10+** and an **active Care Plan**. Licensed **per named user**, as an **annual subscription**. | Item | Part # | Description | | ---------------------------------------------- | ---------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Command Centre Web - Cardholder Management** | **C16051** | Secure, browser-based access to Command Centre from any internet-connected location, with no workstation required. Manage cardholders remotely: create cardholders, manage access and credentials, update personal data, view activity history. | ## Cardholder Management module The first (and current) Command Centre Web module is **Cardholder Management**. From the browser, administrators can: * View cardholder **history** and **activity** * Manage **cards and credentials** (**excluding** printing or encoding cards) * Manage cardholder **access** and assign access * General **Personal Data Field (PDF)** management ![Command Centre Web cardholder Access screen in a browser - a cardholder's assigned Access Groups (Building 1 Level 1, Building 1 Level 2, Building 2) with Active state and From/Until dates, plus an Assign Access button; an "Early Access" feedback banner runs across the top](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-c75f823ea35a6c6d1ee3fd757334bf8201fa568f%2FSECHUB-web-client-techlib-01-cardholder-access-ui.png?alt=media) ## Configure Command Centre Web To start using Command Centre Web, tick **Enable Command Centre Web** on the **Cloud FT item**. **No web servers or extra infrastructure are needed.** The Command Centre Cloud and the appropriate **API Gateway for the region** must also be configured. After clicking **Apply**, the access **URL is populated or updated**, and that URL is how users reach the Web client. ![The Command Centre Cloud item Properties (Configuration tab) - Region set to Command Centre Cloud, Enable Gallagher API Gateway (Region: Australia), and the "Enable Command Centre Web" checkbox with the generated access URL populated (highlighted), alongside Mobile Credential Invitation settings](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-4e12d48f814018b2adafe01b13ee77cbfcccf870%2FSECHUB-web-client-techlib-02-cloud-ft-enable-web-config.png?alt=media) ## Data storage and security **No sensitive data is ever held in Command Centre Web or its associated cloud services.** Data remains hosted on the customer's **own on-premise Command Centre server**. Command Centre Web reaches it via **REST API through the Gallagher API Gateway, which has no persistent storage**. Any updates made in the Web client are sent back to the on-premise server over the same channel. Log-on is secured with **2-factor authentication via Gallagher Mobile Connect** (see the Authenticator setup in troubleshooting). ## System architecture Command Centre Web connects back to the site's on-premise server through the **Gallagher API Gateway**, so the browser or device never talks to the server directly. ![Command Centre Web architecture - Customer Premise (Command Centre server and REST APIs) connects through the Gallagher Cloud (Gallagher API Gateway and Command Centre Web) to an internet-connected device; data flows from the premise via the API Gateway, and the UI is served from Command Centre Web](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-fc7f4111a37b6348d984ddb2f4cf985ec7735dda%2FSECHUB-web-client-techlib-03-architecture-diagram.png?alt=media) For the full technical detail, see the Command Centre Web vEL9.10 release note. ## Resources * [Command Centre Web - Product Page](https://products.security.gallagher.com/security/nz/products/command-centre-web/p/C16050) * [Command Centre Web - Technical Information Paper (TIP)](https://gallaghersecurity.github.io/r/commandcentre-web) --- # 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/cloud-services/web-client.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.