> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/user/guide/devices-and-settings/device-specific-controls/anti-theft-and-security/social-distance.md). # Social distance Configure the Social distance block in Navixy so the device reports when another tagged device stays within a set distance for too long. Uses the device's built-in Bluetooth Low Energy (BLE) module to detect when another tracked device comes too close. When two devices stay within the set distance for longer than the set time, an event is reported to the Navixy platform. {% hint style="info" %} To receive notifications, create a corresponding alert rule in addition to enabling this block. {% endhint %} ## Settings * **Enable**: turn proximity monitoring on or off. * **Distance**: the minimum allowable distance between devices in meters. Measured in the absence of interference and obstacles. Real-world BLE range is affected by walls, metal, and other obstructions. * **Duration threshold (seconds)**: how long the two devices must remain within the distance before an event is raised. A short threshold triggers on brief passes. A longer threshold only triggers on sustained proximity. ## Availability Appears on device models that have a built-in Bluetooth module with proximity detection support. --- # 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://navixy.com/docs/user/guide/devices-and-settings/device-specific-controls/anti-theft-and-security/social-distance.md?ask=&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.