> 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/features.md).

# Features

Device Locker is a software-based solution that uses BLE proximity detection to track enterprise device check-ins/check-outs. It eliminates the need for physical lockers while reducing device loss through automated missing device alerts.

Device Locker  is designed to support the needs of both end users and administrators in shared-device environments. It helps simplify everyday access and management workflows across the device ecosystem.

### The Problem

Enterprise mobile devices are typically assigned to a store or facility as a whole, not to individual departments. Without a structured check-out process, organizations face:

* No identification of which device belongs to which department
* Manual check-in/check-out systems that fail due to human error
* No accountability when devices go missing
* Devices found weeks later, creating operational gaps

### Key Capabilities

**Passive BLE Proximity Detection**

Device Locker detects enrolled devices within a specified range (e.g., 1 meter / 3 ft) and adds them to the device list. No user action is required for presence detection.

**Automated Device Assignment**

Device Locker assigns the device that is fully charged and least used when a user logs in. This optimizes battery availability and distributes wear across the fleet.

**Device Check-In Prompt**

Device Locker prompts logged-in users to check in their device or continue their active session when they come within range of Device Locker. This handles scenarios where the work area and Device Locker share the same room.

**Real-Time Device Status**

Device Locker displays a live count of devices by status:

1. **Available** - device is present and ready for use
2. **In Use** - device is checked out and a user is logged in
3. **Charging** - device is docked and charging
4. **Missing / Not Reporting** - device has not been detected within the configured grace period

**Admin Device Management**

Device Locker lets administrators register devices via barcode scan or manual input, unregister devices with a specified status (e.g., Missing, In Repair), and access check-out/check-in reports showing device IDs and associated users.

**Device Location & Tracking**

Device Locker displays location and tracking details for each device entry, helping teams locate and recover devices:

1. Approximate distance via BLE signal
2. Location via GPS coordinates
3. Device Finder functionality (ping device, send message)

**NFC Badge Authentication**

Device Locker supports NFC badge authentication during the check-out workflow, allowing users to access an assigned device after completing authentication.

**Backend Alerts**

Device Locker communicates device and locker status events to backend systems, enabling management action on missing devices, shortages, and status changes.

#### Device Locker supports two configurations:

**Wired - Multi-Device Docking Station**

Utilizes a powered multi-port USB hub/dock with USB data connections and a device controller (e.g., Raspberry Pi) to run the Device Locker app. Devices are connected via USB and tracked through the controller.

**Wireless - Tablet Kiosk**

Leverages BLE connectivity between a tablet kiosk and mobile devices to determine whether devices are within proximity of the kiosk. The tablet remains powered and in a fixed location.

### FAQs

**How does Device Locker assign a device to a user?**\
After a badge tap, Device Locker selects an available device and sends the assignment details to it. The device is ready for use once you complete login.

**How does BLE proximity detection work?**\
Device Locker uses BLE signals to sense enrolled devices nearby. This is how it knows when a device is in range for check-out or check-in.

**How does NFC badge authentication work?**\
You tap your enrolled NFC badge to identify yourself and start the check-out. Device Locker then assigns a device and prompts you to finish login on the device.

**How does automatic check-in and logout work?**\
When you return while logged in, Device Locker detects your device by BLE and prompts you to check in or continue. Choosing check-in logs you out and frees the device.

**Can Device Locker show device status in real time?**\
Yes. Status updates as devices are checked out, returned, charged, or go undetected, so you always see current availability.

**Can Device Locker help locate missing or misplaced devices?**\
Yes. The Device Info view shows approximate BLE distance and GPS coordinates, plus Find Device, Ping Device, and Send Message actions to help track one down.

**Can Device Locker send alerts or backend events?**\
Yes. Device Locker can flag devices that are overdue or not reporting, so the right people get notified.


---

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