> For the complete documentation index, see [llms.txt](https://inflight.dope.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://inflight.dope.security/dope.console/endpoint-manager-view/endpoint-count.md).

# Endpoint Count

### You want your organization’s internet security to be kept up to date — that’s what first class is all about. dope.swg keeps the Endpoint Manager View updated so you are kept informed across your organization.

## **Dormant endpoints**

A dope.swg endpoint that has not sent a health check for more than 7 days is considered to be “dormant.”

A dope.swg endpoint in a dormant state for 28 days will be deleted from the Endpoint Manager View. It will no longer be counted as an active device in your organization.

## **Uninstalled endpoints**

If a dope.swg endpoint is uninstalled from a device, the endpoint sends an uninstalled health check to the dope.security cloud. On receipt of this health check, the endpoint is deleted from the Endpoint Manager View. It is also no longer considered an active device in your organization and is removed from your active device count.

{% hint style="info" %}
For deletions of a dormant or uninstalled device, an event is added to the Audit Log where it can be viewed for 30 days. See [Audit Log](/dope.console/settings/audit-log.md) for more information.
{% endhint %}


---

# 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://inflight.dope.security/dope.console/endpoint-manager-view/endpoint-count.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.