> 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/site-installation/mobile-connect.md).

# Mobile Connect

### Introduction

The Gallagher Mobile Connect App allows a user to request access using their mobile device in place of a traditional access card. Access can be requested at a Gallagher HBUS Reader or Gallagher HBUS Terminal.

The App uses Bluetooth® wireless technology, or Near Field Communication (NFC) to communicate with the reader or terminal. A Command Centre operator can specify the reader's or terminal's communication method (either Bluetooth®, NFC, or both).

Note: Only Android devices can use NFC.

A Mobile Credential, stored by the App, is used to identify the mobile device. Second factor authentication (PIN or fingerprint) can be used to identify the device's user. Mobile credentials are registered to users in Command Centre, and use the FIDO (Fast IDentity Online) Universal Authentication Framework (UAF) protocol. This is a globally recognised method of authentication that is proven safe and secure.

In addition to requesting access, a suitably privileged user can use the App to perform an action at a Bluetooth® enabled reader or terminal. Actions that can be performed are listed here.

A Digital ID is also held on the Mobile Connect App, and appears as a digital 'Card' on a Cardholder's Mobile Device to provide visual identification of the Cardholder. It's layout can be configured in the same manner a Card's can be, and can contain text, images, and barcodes.

Digital IDs must be registered in Command Centre Client. Cardholders must have a Mobile Credential in order to receive the Digital ID.

***

### Registration process

<table><thead><tr><th width="60">Stage</th><th>Description</th></tr></thead><tbody><tr><td>1</td><td>An operator uses the Cardholder Cards tile in Command Centre to register a mobile credential with a user. When registered, a request is sent from Command Centre to the Command Centre Cloud. Command Centre sends the user's: email address, phone number, invitation expiry time, and mobile credential identifier.</td></tr><tr><td>2</td><td>The Command Centre Cloud sends an invitation email to the user's email address. This email contains a link to the Gallagher Mobile Connect App. The user must download and install the App on their device. The email also contains an <strong>Accept Credential</strong> button. The user must accept the credential.</td></tr><tr><td>3</td><td>The Command Centre Cloud sends an SMS containing a six digit confirmation code to the user's phone number. The user must enter the six digit code into the App in order to authorise their device.</td></tr><tr><td>4</td><td>The user must specify their second authentication factor, either PIN or fingerprint. If the door requires a second authentication factor, this must be entered using the device, not the keypad on a reader.</td></tr><tr><td>5</td><td>The user can now request access at a Gallagher reader.<br><br>Note: The credential identifier is stored on the Gallagher Controller. Internet connectivity is not required for a user to request access at a Gallagher reader.</td></tr></tbody></table>

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-379dd96262172a644e9717bddb4964fdabb8fad4%2Fblediagram.png?alt=media)


---

# 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/site-installation/mobile-connect.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.
