> 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/aperio-mobile-access-integration.md).

# Aperio Mobile Access Integration

If your site has Aperio BLE capable locks connected to Command Centre, then the Gallagher Mobile Connect app can be used to open such locks. This requires Gallagher Command Centre version vEL9.00 or newer.

Aperio mobile access will be available for all users with mobile credentials provided that the prerequisites are fulfilled. However, Aperio locks must be BLE compatible and updated with firmware that provides Gallagher mobile credential support. This can be verified with the Aperio Programming Application Protocol (PAP) by **right-clicking** on the lock/ reader and selecting **Retrieve System Information**.

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

The System information for Lock/Sensor screen displays showing the BLE item under supported items.

**Note:** Aperio firmware version needs to be 3.19.50 or higher for Gallagher Mobile Credential support.

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

Aperio BLE locks do not advertise access unlike Gallagher readers. Cardholders must contact the Aperio lock with their phone similar to a card to activate the reader. The lock will then appear on the Mobile Connect app if they are a member of the lock’s facility. No feedback is given on access inside the app itself. Cardholders are encouraged to check the lock itself for the access result.

For Aperio lock configuration with the PAP tool, refer to [Aperio Integration](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/aperio-integration.md).

### Prerequisites

For an Aperio BLE credential to be provided to mobile credential cardholders:

* Gallagher Mobile Connect app (for each cardholder)
* Mobile credentials assigned (for each cardholder)
* Command Centre Cloud connected
* Aperio site key generated

For an Aperio lock to recognise Gallagher mobile credentials:

* Aperio BLE compatible lock (with firmware 3.19.50 or higher)
* Aperio Hub connected to Gallagher controller
* Aperio PAP configuration with Gallagher mobile credentials

### Licensing

Aperio licensing required:

* 2A8995 APERIO DOOR LICENCE WITH HARDWARE

### Access

To access an Aperio BLE lock:

1. Open the Mobile Connect app.
2. Hold the phone up to the reader where a card would normally be read, typically there is a wireless symbol to indicate the badge point.

   The lock will show up on the Mobile Connect app and auto-connection will initiate.
3. If 2FA is enabled, you must authenticate with your screen lock.

   Access is granted or denied.
4. If in the 2FA scenario, you may be denied access if you have not set an Android or iOS screen lock. Your phone must be secured for credentials to be available.

   Set a screen lock by following the manufacturer instructions for the appropriate device.


---

# 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/aperio-mobile-access-integration.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.
