> 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/device-finder.md).
# Device Finder
## Overview
The security of shared Android devices remains one of the biggest challenges in the enterprise environment. Research shows that 45% of data breaches among companies are caused by lost or stolen devices and that 9% of organizations either don’t know how or don’t care to protect themselves from mobile-related compromises. Device Finder is part of the BlueFletch EMS toolset that provides enterprise-grade security for employee Android devices - from current device status and site/location assignments to last user login and last access point connection.
* Leverage network data with login/logout events to increase device accountability and visibility in their assigned site/location.
* Create a device trail by being able to see where the device was last seen or which user logged in last.
* Dispatch audible alerts to track down misplaced or missing devices.
{% embed url="" %}
---
# 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/device-finder.md?ask=&goal=
```
`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.