> 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/filtering-and-sorting-the-endpoint-view.md).

# Filtering and Sorting the Endpoint View

### dope.swg has set up the Endpoint Management View to be simple and informative for your organization’s needs. But flying first class, you can choose always to do things your way.

You can filter the table to display by the health status of your endpoints, i.e. Healthy, Error, Dormant, Disabled, etc.

To do this, simply select the filter icon next to the column name, and select the status you wish to filter by from the dropdown.

![](/files/2P9eJs5TqgDZZnYe7uwl)

This dropdown allows multiple status selections at once, e.g. you could search for endpoints in both “Healthy” and “Dormant,” or in any combination you select. You can also filter for endpoints in Debug and in Fallback Recover states.

Once you have made your selections the Endpoint Manager View will filter to show just those devices.


---

# 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://inflight.dope.security/dope.console/endpoint-manager-view/filtering-and-sorting-the-endpoint-view.md?ask=<question>&goal=<endgoal>
```

`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.