> 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/bi-360/global-inventory.md).
# Global Inventory
The **Global Inventory** is the single list of every BI asset across all your connected tools: reports, dashboards, datasets, models, apps, and folders, no matter where they were created. For each asset you see where it lives, who owns it, and whether it is healthy.
**What you use it for:**
* Eliminate blind spots across BI tools.
* Identify unused, stale, or orphaned assets.
* Improve governance, ownership, and accountability.
* Support cost and license optimization.
* Build a trusted foundation for cleanup and optimization initiatives.
{% hint style="info" %}
Global Inventory is built for breadth. For a deep dive into a single asset, with lineage, usage analytics, and alerts, use your team's Inventory.
{% 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 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/bi-360/global-inventory.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.