> 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 <a href="#overview-0" id="overview-0"></a>

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="<https://youtu.be/szN04PGu3_0>" %}


---

# 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/device-finder.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.
