> 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/performing-bluetooth-actions.md).

# Performing Bluetooth® Actions

### Introduction

Actions that can be performed by a suitably privileged user at a Gallagher Bluetooth® enabled reader using the Mobile Connect App are:

* Gain entry to an Access Zone
* Arm or disarm the Door’s Access Zone
* Change the access mode for the Door’s Access Zone
* Change the state of Outputs

**Notes:**

* In order to perform actions at a reader, the reader must be configured for Bluetooth® and Manual Connect.
* When a second authentication factor is required, the second factor must be presented before the action can be requested. The user will have up to 30 seconds to perform the action without needing to re-enter their second factor.
* Actions are not available when the reader is assigned to an Elevator. If allowed, entry to the Access Zone will be the only action available.
* Other users can continue to request access at the reader while a user decides which action to perform. Bluetooth® comms are only used to perform the privilege check and the action.

### Procedures

Refer to the appropriate procedure:

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><i class="fa-door-open">:door-open:</i> Gaining entry to an Access Zone</td><td><a href="https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/mobile-connect/performing-bluetooth-actions/gaining-entry-to-an-access-zone.md">Gaining entry to an Access Zone</a></td></tr><tr><td><i class="fa-bell">:bell:</i> Arming or disarming the Door’s Access Zone</td><td><a href="https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/mobile-connect/performing-bluetooth-actions/arming-or-disarming-the-doors-access-zone.md">Arming or disarming the Door's Access Zone</a></td></tr><tr><td><i class="fa-door-open">:door-open:</i> Changing the Door’s access mode</td><td><a href="https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/mobile-connect/performing-bluetooth-actions/changing-the-doors-access-mode.md">Changing the Door's access mode</a></td></tr><tr><td><i class="fa-toggle-on">:toggle-on:</i> Changing the state of Outputs</td><td><a href="https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/mobile-connect/performing-bluetooth-actions/changing-the-state-of-outputs.md">Changing the state of Outputs</a></td></tr></tbody></table>


---

# 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/performing-bluetooth-actions.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.
