> For the complete documentation index, see [llms.txt](https://docs.spectralink.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spectralink.net/amie-advanced/metrics-reference/managed-devices.md).

# Managed Devices

The number of devices in your fleet that have completed enrollment.

## How it's calculated

A count of every enrolled device within the group you have selected. Nothing is filtered out by age or activity — a device that has not been heard from in a year still counts.

## What's included and excluded

* **Included:** every device that holds the credentials it needs to talk to the service, whether or not it has checked in recently.
* **Excluded:** devices without those credentials.

{% hint style="warning" %}
TODO: What does a device without credentials represent to an administrator — one that never finished being added? Does it appear anywhere else in the product?
{% endhint %}

## Time window and timezone

None. This is a current count, recalculated each time the screen loads.

## Data freshness

Calculated when the screen loads, from a read-only copy of the database. Nothing is cached between loads, though a change made moments earlier may not be reflected immediately. Reload the page, or change the selected group, to recalculate.

## Filters and breakdowns

The group selector in the header narrows this figure to the devices in the selected group.

On the Dashboard the count is paired with a "% checked in last 24h" subline, the share of these same devices that have checked in during the last rolling 24 hours. It is rounded to a whole number, so in a large fleet a handful of devices checking in can still read **0%**. When the device count itself is zero, the percentage also reads **0%**.

## Edge cases

* **Zero is ambiguous.** It can mean you have no devices, that all of them have been removed, or that the selected group resolves to nothing the service can count.
* **The related check-in percentage is rolling, not daily.** "Last 24 hours" means the 24 hours before you loaded the screen, not since midnight.

## Where you'll see it

* [Dashboard](/amie-advanced/using-the-platform/dashboard.md) — as the **Managed Devices** card
* [Devices overview](/amie-advanced/using-the-platform/devices-overview.md) — as the **Devices managed** banner

{% hint style="warning" %}
TODO: The Dashboard and Devices overview each calculate this count separately. Confirm whether they are expected to always agree.
{% endhint %}

## Related metrics

* [Battery Health Distribution](/amie-advanced/metrics-reference/battery-health-distribution.md): **Managed Batteries** sits beside this figure on the Dashboard and counts batteries the same way. The two are selected by different means internally, so a group selection can narrow one more than the other.


---

# 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.spectralink.net/amie-advanced/metrics-reference/managed-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.