> For the complete documentation index, see [llms.txt](https://docs.bluefletch.com/bluefletch-enterprise/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bluefletch.com/bluefletch-enterprise/product-guides/virtual-device-locker.md).

# Device Locker

Device Locker is a software-based solution for managing shared mobile devices across retail, healthcare, and other enterprise environments. Using Wi-Fi and BLE, it supports device connectivity and proximity tracking within a designated area. This enables structured device check-in and check-out workflows while maintaining visibility into device presence.

Device Locker is designed to improve accountability and operational control of shared devices - supporting clear device responsibility, real-time location visibility, and follow-up workflows for misplaced, missing, or overdue devices. VDL can be deployed in environments that use a physical docking station or a virtual docking model based on device proximity. <br>

* **Asset accountability:** Ties each check-out to a specific user and/or location for clear device ownership.
* **Operational visibility:** Real-time status of all devices, including docking detection, presence, and assignment state.&#x20;
* **Administrative control:** Tools for device registration, unregistration, and reporting. Includes check-out and check-in logs with device IDs and associated users.
* **Device tracking:** Location awareness based on Wi-Fi connectivity and BLE proximity.&#x20;
* **Deployment modes:** Supports physical docking stations and proximity-based virtual docking. Adapts to wired or wireless hardware configurations.


---

# 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://docs.bluefletch.com/bluefletch-enterprise/product-guides/virtual-device-locker.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.