> 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/server-properties/mobile-access-settings.md).

# Mobile Access Settings

### Introduction

This tab enables you to specify the site wide settings for Mobile Connect.

### Procedure

1. Open the **Command Centre Server Properties** window. [How?](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/opening-the-server-properties-window.md)
2. Click the **Mobile Access Settings** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-4d4a6b682786f34fa79e738bf402df0e4c294cb8%2Fbluetoothsettingstab.png?alt=media)
3. Configure the **General** settings as required.

   <table><thead><tr><th width="144">Field</th><th>Description</th></tr></thead><tbody><tr><td>Turn on Mobile Connect NFC</td><td>When checked, Android devices will use NFC to request access at the readers. NFC applies to Auto Connect only. If the user has NFC disabled on their device, their device will revert to Bluetooth® to make the access request. Default is OFF.</td></tr><tr><td>Second factor authentication always required for mobile</td><td>When checked, presentation of a second authentication factor is required at all Bluetooth® enabled readers, unless the access mode is set to ‘Free-No PIN’. Default is OFF. Second factor authentication is enforced for mobile credentials only.<br><br><strong>Note:</strong> If the access mode is set to ‘Free-No PIN’ and a personalised action has been assigned to the user, a second authentication factor <strong>will</strong> be required. Refer to <a href="https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/access-zones/configuring-personalised-actions-for-access-zones.md">Configuring Personalised Actions for Access Zones</a> for details on how personalised actions work.<br>NFC works over a short range, hence a user may take their device out of range to provide their second factor. When this happens, the App displays an icon encouraging the user to re-enter the field.</td></tr></tbody></table>
4. Configure the **Bluetooth low energy** settings as required.

   <table><thead><tr><th width="144">Field</th><th>Description</th></tr></thead><tbody><tr><td>Turn on Bluetooth low energy technology</td><td>When checked, Bluetooth® comms are enabled. Default is OFF.</td></tr><tr><td>Advertise reader name</td><td>When checked, the reader's name will be displayed in the Gallagher Mobile Connect App. Default is ON.<br>If the reader has been configured with a Short Name, the Short Name will be used. Names longer than 26 characters will be truncated. If set to OFF, a generic identifier incorporating part of the reader's HBUS serial number will be shown in the Gallagher Mobile Connect App, (e.g. Reader: 12345).</td></tr><tr><td>Transmit Power</td><td><p>Controls the Bluetooth® signal strength. Default is -26 dBm.<br><br><strong>Notes:</strong></p><ul><li>Increasing the transmit power will increase the Bluetooth® connection distance.</li><li>Reducing the transmit power can be used to prevent closely located readers from interfering with each other Bluetooth® communications.</li></ul></td></tr><tr><td>Auto connect range</td><td><p>When checked, all mobile devices will automatically initiate an access request when they sense a signal stronger than this value. Lower values indicate a stronger signal, and thus higher values will allow access from farther away. Default is 45 dBm.<br>Auto connect will be disabled when:</p><ul><li>the Door that this reader is assigned to has no Access Zone assigned to it, or</li><li>the Door that this reader is assigned to has one Access Zone that is in access mode 'Free-No PIN', or</li><li>the reader is assigned to an Elevator with all floors in access mode 'Free-No PIN'.</li><li>the Door's Emergency Release has been triggered.<br><br><strong>Note:</strong> Auto connect may not be suitable for all reader installations, (e.g. if a user is situated close to the reader, continual connection attempts from the reader will reduce the device's battery).</li></ul></td></tr><tr><td>Manual connect range</td><td>When checked, the user will be able to manually initiate an access request from this range (which must be a longer range than the auto-connect range), using the Gallagher Mobile Connect App. Default is 64 dBm.</td></tr></tbody></table>

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

   **Notes:**

   * Increasing the path loss value will increase the reader's Bluetooth® read range.
   * Consideration should be given to the installation environment, as environmental factors may reduce the reader's Bluetooth® read range. It is advised that each reader's transmit power and connection ranges are individually calibrated. The Gallagher Mobile Client App can be used to calibrate the signal strength for each reader.
   * Consideration should be given to the signal strength of readers that are installed back-to-back. For example, a reader installed at the front door is set to ‘Secure-PIN’ and the exit reader on the other side of the wall is set to ‘Secure’, a user could connect to the exit reader and gain entry without entering a PIN.
   * If a reader is assigned to an Elevator, the user will be required to enter a second authentication factor, if any of the Elevator's floors require a PIN.
5. When licensed, the **Aperio** section will appear in the lower part of this screen.

   Configure as required if your site wants to use mobile credential access at Aperio locks.

   **Note:** These settings will be used in the Aperio Programming Application to configure mobile credentials for Aperio locks. See [Configuration for Mobile Connect](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/aperio-integration/configuring-the-aperio-locks-readers/configuration-for-mobile-connect.md) for further detail.

   <table><thead><tr><th width="144">Field</th><th>Description</th></tr></thead><tbody><tr><td>Mobile site key</td><td><p>Populate this field with a 32 character hexadecimal string. Characters accepted are only A-F and 0-9.<br>Clicking the <strong>Generate</strong> button automatically populates the field with a random hexadecimal string and enables the <strong>Apply</strong> button. If the <strong>Apply</strong> button is clicked now, the 32 characters are converted to 32 X's.<br><br><strong>Notes:</strong></p><ul><li>Clicking the <strong>Show</strong> button will display the key that you have entered. Clicking the <strong>Apply</strong> button changes the text back to X’s and the <strong>Show</strong> button is enabled again. An operator event is also logged.</li><li>If the site key has somehow been compromised you can change an already saved key by clicking the <strong>Generate</strong> button. If you do this the following warning message will display:<br><em>"Are you sure you want to change the Aperio mobile site key? Changing the Aperio mobie site key will require manual reconfiguration of all Aperio doors on site. Mobile credential access to these doors will no longer be granted until this has been done."</em></li></ul></td></tr><tr><td>Site ID and Service Code</td><td>Once you have added a mobile credential these 'Read-only' fields are popluated.<br>Site ID: 8 character hexidecimal format<br>Service Code: 2 digits</td></tr></tbody></table>
6. Click **OK** to exit and save your changes.

   Click **Cancel** to exit without saving your changes.

   Click **Apply** to save your changes and stay in this window.


---

# 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/server-properties/mobile-access-settings.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.
