> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/smb/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/smb/smb-app/site/access-control.md).

# Access Control

The Gallagher SMB solution can support up to 10 access control doors. Access control doors have a Gallagher SMB reader which a user can either present their smartphone or SMB key tag or enter an SMB User Code into a Keypad.

iOS smartphones communicate with the reader using Bluetooth®. Android smartphones communicate with the reader using NFC or Bluetooth®. A tag will communicate with the reader using NFC.

Access granted and access denied events will appear in the Activity log. The user’s name, credential type, and door name are reported.

{% hint style="info" %}

* Ensure Bluetooth® is enabled on your device. Android devices also need NFC enabled.
* Location permission must be enabled on Android devices, as without this permission the device’s Bluetooth® won’t scan, even if Bluetooth® itself is enabled.
* The area assigned to the door must be disarmed before the door will unlock. Two-factor authentication is required to disarm (their smartphone must have a passcode, biometrics, or facial recognition).
* Users are given the privilege to enter areas; not doors, which means a user given access to a particular area will be able to enter through any of the access-controlled doors leading into that area.
* Only Site Managers and privileged Site Admins can view doors and their locked/unlocked status within the Gallagher SMB app.
* Doors will lock automatically when the area they are associated with is armed.
  {% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.security.gallagher.com/smb/smb-app/site/access-control.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.