> 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/bluefletch-launcher/device-loss-prevention.md). # Device Loss Prevention Device Loss Prevention enables administrators to prevent unauthorized access, track real-time location, and reduce the risk of device loss or theft. It enhances overall device security and promotes accountability to protect sensitive corporate data across the workforce. **Low Battery Mode:** Prompts users to cradle devices when battery levels drop below a configured threshold while maintaining background location services. **Luggage Tag:** Locks devices automatically when they move outside approved network ranges or geofences to prevent unauthorized access. **Secure Device Mode:** Enforces mandatory user sign-in within a configurable timeout period and triggers an alarm if access is not verified. --- # 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/bluefletch-launcher/device-loss-prevention.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.