> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/qna/using-navixy/not-all-devices-are-shown-in-the-objects-list.md).

# Not all devices are shown in the objects list

Check service plan limits on the user account; the most restrictive active plan controls how many trackers appear in the objects list

## Question

Not all devices are shown in the objects list. Why?

## Answer

First, check if any filters are applied:

* Clear all filters in the tracker list.
* Remove any text from the search field.

If the issue persists, it’s likely due to a service plan limitation on the number of visible trackers. Here’s how this works:

If the user has at least one tracker assigned to a plan that limits the number of allowed trackers, and the actual number of trackers exceeds that limit, the platform will only display the number of trackers allowed by the most restrictive plan.

**Example:** A user has 100 trackers:

* 99 trackers use a plan with a 100-tracker limit.
* 1 tracker uses a plan with a 5-tracker limit.

In this case, the user will only see **5 trackers**, because the plan with the 5-tracker limit affects visibility.

**How to fix it:** Adjust the restrictive plan (in this example, remove or update the plan that limits the user to 5 trackers).

## Links

* [Object list](/docs/user/guide/tracking/objects-list.md)
* [Maximum device count for a user](/docs/qna/using-navixy/maximum-device-count-for-a-user.md)


---

# 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://navixy.com/docs/qna/using-navixy/not-all-devices-are-shown-in-the-objects-list.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.