> For the complete documentation index, see [llms.txt](https://docs.datalogz.io/guides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.datalogz.io/guides/inventory/inventory-summary.md).
# Inventory Summary
The Summary tab is where you start in [Inventory](/guides/inventory.md). An estate with thousands of assets and hundreds of open findings does not tell you what to do first. Summary does, by narrowing the whole estate to four questions you can act on today: how healthy is it, what changed, what do people actually use, and what am I watching.
Everything on the page is a jump-off point. Each tile, count, and asset links through to the filtered Assets grid or straight to an asset page.
### **What Summary shows**
* **Estate health at a glance.** Ratio tiles for asset health and activity, each showing a healthy/unhealthy or active/inactive split with counts, scoped to the connector and team selected in the left nav.
* **Change detection.** The **Start here** panel lists what was created and updated in the last 30 days, with field-level detail on datasets: which tables, columns, and measures were added or modified, by whom, and when. This is where a renamed column surfaces in days rather than after it has quietly broken a downstream report for three weeks.
* **Orientation shortcuts.** **Top Reports** ranks your most-viewed reports with viewer counts, and **Favorite Assets** groups your starred assets by type. Both carry Asset Health badges, so you can see immediately whether the things people rely on most are in good shape.
---
# 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.datalogz.io/guides/inventory/inventory-summary.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.