> 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/command-centre-mobile-client.md).

# Command Centre Mobile Client

Configure and troubleshoot the Command Centre Mobile Client.

![Command Centre Mobile app menu on a phone - Alarms, Cardholders, zones and more](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-39146002c444bee4466fc05ab4ea1150a5e8612b%2FSECHUB-cc-mobile-client-01-product-app.png?alt=media)

The Command Centre Mobile App extends security and access control to security staff on the move, on guard or on patrol. It lets them view cardholder details, monitor site alarms and status, and trigger overrides and macros from a phone (iOS and Android).

The Mobile Client is the guard-facing mobile surface. It is distinct from Mobile Connect, which is the cardholder credential app for end users.

## What it does

Whether security staff are on guard or on patrol, the Mobile Client lets them spend more time away from the desk while keeping complete awareness of what is happening on site, and manage everyday security issues from wherever they are.

Core capability, on the base licence:

* View cardholder details
* Monitor site alarms and status
* Trigger overrides and macros

## Licensing

One Mobile Application licence is included with server software (**C201311**). The per-device licence (**2A8559**) is required for the second mobile device onward.

| Item                                   | Part # | What it adds                                                                                                                                              | Platform        |
| -------------------------------------- | ------ | --------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------- |
| **Mobile Client Licence (per Device)** | 2A8559 | Base mobile functionality: view cardholder details, monitor site alarms and status, trigger overrides and macros                                          | iOS and Android |
| **Mobile Evacuation**                  | 2A8568 | View cardholders located within a monitored area and move them from a monitored area to another location, for example a muster zone or outside the system | iOS and Android |
| **Mobile Access Reader**               | 2A8561 | Move cardholders into access zones. The cardholder's access privileges are authenticated via Command Centre for accurate access decisions                 | **iPhone only** |

## Where to start

* **Setting up a device that cannot connect?** See [Unable to add a Mobile Client](/knowledge-hub/products/cloud-services/command-centre-mobile-client/troubleshoot/mobile-client-unable-to-add-a-mobile-c.md).
* **Choosing a connection method?** See [Connection Options - Signed Token vs TLS Client Certificate](/knowledge-hub/products/cloud-services/command-centre-mobile-client/configure/mobile-client-connection-options-signe.md).
* **Notifications not arriving?** Start with [Troubleshooting a mobile device](/knowledge-hub/products/cloud-services/command-centre-mobile-client/troubleshoot/mobile-client-notifications-troublesho.md), then [Troubleshooting a server](/knowledge-hub/products/cloud-services/command-centre-mobile-client/troubleshoot/mobile-client-notifications-troubl-2.md).
* **Need logs?** See [Getting logs from the Mobile Client](/knowledge-hub/products/cloud-services/command-centre-mobile-client/troubleshoot/mobile-client-getting-logs-from-the-mo.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/products/cloud-services/command-centre-mobile-client.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.