> 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/integrated-systems/aperio-integration/configuring-the-aperio-locks-readers/configuration-for-mobile-connect.md).

# Configuration for Mobile Connect

### Introduction

This procedure describes how to configure mobile credentials to gain access at Aperio locks.

**Note:** To improve the user experience, it is strongly recommended that the Aperio reader buzzer be enabled. Doing so, will provide audible feedback to the phone user. All Aperio E100 readers support buzzer configuration.

### Prerequisites

The Aperio Mobile Site Key, ID and Service Code must be configured on the **Mobile Access Settings** tab of the Server Properties in Command Centre Configuration Client prior to performing this procedure. See [Mobile Access Settings](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/mobile-access-settings.md) for further detail.

**Note:** You will need need to use the latest versions of software and firmware for this to work see below:

* Aperio Programming Application 30.0.23 or later
* wireless lock firmware 3.20.0 or later, using a Bluetooth capable lock
* Mobile Connect App: iOS 16.03.049, Android 16.03.038 or later

### Procedure

1. In the Aperio Programming Application, **right-click** on the lock/reader and select **Lock/Sensor** > **Configure…**

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

   The Configure Lock/Sensor wizard displays.
2. Select **Mobile Credentials** from the drop-down list and click **Add…**

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

   The Mobile Credential Configuration dialog displays.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-bd15ffa80ef5f84539186711687926b8d7dfc621%2Fmobilecredentialsdialog.png?alt=media)
3. From the **Credential provider/type** drop-down list, select "Gallagher Mobile Credential".

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-6fd6d4eccece9f80ca540c9913462374dfb3c735%2Fmobilecredentialsdialog_gallagherdesfire.png?alt=media)
4. Only leave the **Use Two Factor Authentication** checkbox ticked if your site requires users to authenticate via mobile screen lock before requesting access at the door.
5. Copy the **Key**, **Site ID** and **Service Code** from the **Mobile Access Settings** tab of the Server Properties in Command Centre Configuration Client.

   See [Mobile Access Settings](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/mobile-access-settings.md) for further detail.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-4202a179da5712fdfadeab8a42278e1d4e3952fd%2Fmobilecredentialsdialog_copykeys.png?alt=media)
6. Click **Next** until you reach the screen where you can **Apply** the changes.

#### Changing the auto-connect range for an Aperio Door

The auto-connect range, (i.e. the read distance between the phone and the lock), is set in the Aperio Programming Application, as follows:

**Note:** There is no manual connect.

1. In the Configure Lock/Sensor wizard, click **Next** until you reach the "RFID General Settings" screen of the wizard.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-c0a985d3fc7d71c83e73568bff648a2cf11c00ca%2Fpapconfigurebluetooth1.png?alt=media)
2. Click the **Change…** button in the Bluetooth LE section.

   The Configure Bluetooth LE dialog displays.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-a90f7b7e3de877717d5ec32b2203068eaefdfce1%2Fconfigurebluetoothledialog.png?alt=media)
3. Adjust the figure in the **Sensitivity** field as appropriate.

   **Note:** The installer needs to calibrate the locks to the appropriate sensitivity, (i.e. the read distance between the phone and the lock). Unlike Gallagher who use the Path Loss for calibration, Aperio use RSSI.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-063758b11df68c0039000f1a1b36a166e3d92a49%2Fcalibratedistance.png?alt=media)
4. Click **OK**.

   The Configure Bluetooth LE dialog closes.
5. Click **Next** until you reach the screen where you can **Apply** the changes.

#### Changing the physical location

This function applies to both communication hubs and locks/sensors. In the example below the physical location name is changed for a lock sensor.

1. Hover over Lock/Sensor and click **Change Physical Location Name…**

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

   The Change Physical Location Name dialog displays.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-c1102f5465de35a6c13cd2fcfdbd0e58c282945d%2Feditphysicallocation.png?alt=media)
2. Enter a description in the **Physical Location** field that clearly identifies the lock position and click **OK**.

   **Note:** The **Physical Location** field allows 21 characters to be entered but only 19 characters are passed to Mobile Connect.
3. Hold the credential at the lock, or engage the magnet for the sensor.

   For a communication hub the information is updated immediately.

   **Note:** This step is not necessary for V3 locks that are connected with a USB cable, or online locks that have the polling interval set to less than 15 seconds.

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

   After a successful reading a progress bar shows the download.

   After the update completes, the new location name is shown in the Lock/sensor section on the lower right side of the installation view.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-cd11b8e6423801b89feebdf0f08d243604d27c5c%2Feditphysicallocation_updatedname.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/integrated-systems/aperio-integration/configuring-the-aperio-locks-readers/configuration-for-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.
