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

# View Site Devices

##

Site devices can be viewed through List View, which organizes structured data, or Map View, offering a spatial representation for easy visualization.

You can view site devices in two ways: List View, displaying organized data, and Map View, showing a geographical layout for better visualization.

### Device List View

Users can view a complete list of devices assigned to their site or location. The List View is the default display and toggles to Map View. The List View includes essential details for each device such as:

* Serial Number
* Status
* Last Reported Activity
* Last Known User
* Battery Charge
* Current Distance from the Device

#### Device Finder has 3 tabs displayed in List View:

* **All Devices:** Displays all devices known at the site, including those that are Powered Off, Idle/Off Cradle, Missing, Not Reporting, Cradled, or In Use.
* In Use: Shows devices currently in use and not cradled, with the status specifically listed as "In Use".
* Not Reporting: Lists devices that haven’t sent data within the last 12 hours, categorized as Missing, Not Reporting, or Powered Off.

### Device Map View

The Map View overlays the device list onto a map. Each device is represented by a locator, color-coded based on its status (e.g., Cradled, In Use, or Not Reporting). Key functionalities in

Map View include:

* Selecting a device's locator to view its Serial Number, Last User, Model, and Status.
* Auto-opening of the device card for quick details when a device is selected.
* A helpful toast message instructs users to click on the location icon for more details.
* Integration with OpenStreetMap for map visualization.

<br>


---

# 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/features/view-site-devices.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.