> For the complete documentation index, see [llms.txt](https://docs.plextrac.com/plextrac-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plextrac.com/plextrac-documentation/product-documentation/analytics/assets.md).
# Assets
The **Assets** tab has two containers that can be expanded or collapsed to display all assets that the user has access to view:
* **Asset findings overview:** an overview of all assets
* **Assets**: a table view of assets with sortable headings
{% hint style="info" %}
Only assets from reports with a "Published" status are included in the analytics module.
{% endhint %}
## Asset Filters
Search filters allow users to refine and narrow search results based on specific criteria or parameters.
Analytics filter values and data sets are updated every minute. If a tag or field was updated but did not appear as expected, wait one minute and try again.
A list of all filters and values for the **Assets** tab exists below:
* Client(s)
* Client Tags
* Asset Types
* Asset(s)
* Asset Tags
* Ports
* Finding Severity
* Critical
* High
* Medium
* Low
* Informational
* Asset Severity
* Critical
* High
* Medium
* Low
* Informational
* Unspecified
* Finding Tags
* Report
* Report Tags
* Operating System
* Data Owner
* System Owner
* Physical Location
## Asset Findings Overview Container
This container graphically displays the number of assets that have findings and provides a breakdown of the severity of findings (for those assets with findings).
## Assets Container
This container displays a table that lists the asset name, client, criticality, type, and finding count. Column headers can be clicked to change the sort order and how the data is displayed.
Click an asset row for more information and a list of associated findings.
Assets can be edited directly by clicking **Edit Asset** at the top right of the page.
---
# 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://docs.plextrac.com/plextrac-documentation/product-documentation/analytics/assets.md?ask=&goal=
```
`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.