> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/access-control/configuration/bluetooth-unlock/bluetooth-unlock-with-geofencing.md).

# Bluetooth Unlock with Geofencing

Bluetooth Unlock is a convenient feature that allows you to use the [Verkada Pass](/access-control/users-and-credentials/verkada-pass-app.md) mobile app to unlock doors. By default, users with Remote Unlock privileges can unlock doors remotely from anywhere. You can prevent mobile unlocks with geofencing based on your organization’s needs.

{% hint style="danger" %}
You must be an Access Site Admin to enable Mobile Geofencing. Learn more about [Roles and Permissions for Access Control](/access-control/getting-started/roles-and-permissions-for-access-control.md).
{% endhint %}

***

## Enable Geofencing

{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Access.**
{% endstep %}

{% step %}
**On the left panel, click Access Settings .**
{% endstep %}

{% step %}
**Toggle on Mobile Geofencing.**

<div align="left" data-with-frame="true"><img src="/files/3ZLL2ymeuCb7n73UxJJX" alt="" width="574"></div>
{% endstep %}

{% step %}
**(Optional) The default unlock distance is set to 1,640.42 ft (500m). You can set the geofence unlock distance to be between 1 and 32,808.4 ft (10,000m).**
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
The geofence distance is based on the latitude and longitude of your phone’s GPS location and the latitude and longitude of the address of the building that your access controller is assigned, *not by the distance from your phone to the door you are unlocking.*
{% endhint %}

{% hint style="info" %}
We recommend that you set geofencing to 1,640.42 ft (500m) for optimal performance.
{% 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.verkada.com/access-control/configuration/bluetooth-unlock/bluetooth-unlock-with-geofencing.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.