> For the complete documentation index, see [llms.txt](https://v2.dataos.info/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://v2.dataos.info/consume/v1/evaluate/assets.md).

# Explore assets

Assets show what a Data Product is built from, what it publishes, and how data flows through it. Use the Assets tab to review source datasets, curated outputs, semantic models, metrics, and the relationships between them, before you commit to querying or consuming. A protected (shield) icon in the left panel flags an asset a policy masks or filters, so you can spot governed assets before you rely on them.

From the product page, select **Assets** in the Quick access bar. The left panel groups assets into **Overview**, **Seeds**, **Inputs**, **Outputs**, **Semantics**, and **Metrics**.

![Assets tab showing the holistic view of a Data Product](/files/T037fKbCV8oJQYnPvQ5D)

<table><thead><tr><th width="125.85009765625">Section</th><th>Why it matters</th></tr></thead><tbody><tr><td><a href="/pages/TYbNRdq9JXTdgmbmxHV3">Overview</a></td><td>See how data flows end to end so you can decide what to query before digging into details</td></tr><tr><td><a href="/pages/1Ff5qp3vqvjLBVuIXMA8">Seeds</a></td><td>Check the reference values and lookups that classify and enrich the data</td></tr><tr><td><a href="/pages/aOOlECFGsC8dDM523p0W">Inputs</a></td><td>Trace where the product's data originates and what raw fields it starts from</td></tr><tr><td><a href="/pages/gcz9Drw8eiPBoMGFjhuJ">Outputs</a></td><td>Find the governed datasets you can consume downstream</td></tr><tr><td><a href="/pages/XqbRIK0V838zfygEy5wV">Semantics</a></td><td>Pick business-ready dimensions and measures without learning the underlying tables</td></tr><tr><td><a href="/pages/86QhosHWjS4RGKbKHxaG">Metrics</a></td><td>Reuse governed measures instead of recomputing them</td></tr></tbody></table>

Use assets to answer: what does this read from (Inputs, lineage), what can I consume (Outputs), which fields are available (Semantics), which measures can I reuse (Metrics), and how does a field flow through the product (Overview and lineage).

## Policies

Any Seed, Input, Output, Semantics, or Metrics asset with an access policy shows a **Policies** tab in its detail view, alongside **Columns** and **Dependencies**. It covers two views: **Policies applied for you**, a summary of what resolves to your own access (for example, "3 columns are masked and 1 row filter applied on you," or "Full access"), and **Full policy**, a per-group breakdown of masks and row filters across every group with access. A protected (shield) icon on the asset in the left panel flags that a policy applies before you even open it.


---

# 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://v2.dataos.info/consume/v1/evaluate/assets.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.