> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dqlabs.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Asset Detail

> In-depth view of a single asset

<script type="application/ld+json">
  {`{
            "@context": "https://schema.org",
            "@type": "TechArticle",
            "headline": "Asset Detail",
            "description": "In-depth view of a single asset",
            "url": "https://docs.dqlabs.ai/architecture/asset-details",
            "publisher": {
              "@type": "Organization",
              "name": "DQLabs Inc",
              "logo": "https://media.brand.dev/332adc35-5bc4-4d2b-bf78-256aa4a5e414.svg"
            }
            }`}
</script>

Detailed Overview of Asset

Click any asset in the list to open its detail view. Whether you're tracing a single column or mapping an entire pipeline, Prizm treats every object in your data stack — tables, models, dashboards, pipelines, and beyond — as a unified **asset**, searchable and inspectable from one place. The asset type taxonomy gives consistent meaning across platforms, while the detail tabs (Overview, Entities, Metric, Usage, Lineage, Audit, Documentation, Conversation) give you every lens you need: health, structure, quality, usage, dependencies, history, and context. Together, this makes the Assets page the single source of truth for understanding what data you have, how trustworthy it is, and how it all connects.

The detail view provides the following tabs whenever it is applicable along with any other custom tab the user creates.

<CardGroup cols={2}>
  <Card title="Overview" icon="gauge-high" href="/architecture/asset">
    A summary of key metrics, recent alerts, and asset information at a glance. Start here to assess the current health of an asset.
  </Card>

  <Card title="Entities (child objects)" icon="table" href="/architecture/entities">
    A summary of an asset's child objects (e.g. Attribute under Table, Schema under Database) with  relevant information for assessing   structure.
  </Card>

  <Card title="Metric" icon="circle-check" href="/architecture/metric">
    Time-series charts and current values for all data observability and data quality metrics configured on the asset, such as completeness, uniqueness, volume and freshness.
  </Card>

  <Card title="Usage" icon="screen-users" href="/architecture/usage">
    Query activity, performance, and cost metrics for the asset, with a detailed query log showing the upstream sources and downstream consumers so you can trace the blast radius of an issue.
  </Card>
</CardGroup>

<CardGroup cols={2}>
  <Card title="Lineage" icon="sitemap" href="/architecture/lineage">
    An interactive lineage graph showing the upstream sources and downstream consumers of the asset, so you can trace the blast radius of a data quality issue.
  </Card>

  <Card title="Audit" icon="line-columns" href="/architecture/log/asset-audit">
    Chronological log of who did what and when on the asset (views, edits, and other actions), useful for tracking activity and governance.
  </Card>

  <Card title="Documentation" icon="book-open" href="/architecture/documentation">
    Free-form documentation attached to the asset — descriptions, usage notes, and links — to help your team understand the data.
  </Card>

  <Card title="Conversation" icon="rocketchat" href="/architecture/conversation">
    A discussion space for the asset where users can start topics, ask questions, and engage with likes/dislikes and bookmarks for team collaboration.
  </Card>
</CardGroup>

The Assets page provides a single, consistent entry point for discovering and managing every object in your data ecosystem — regardless of source platform. The asset type taxonomy ensures consistent classification across systems, while the detail tabs (Overview, Entities, Metric, Usage, Lineage, Audit, Documentation, Conversation) give users the specific information needed to assess an asset's health, structure, quality, usage patterns, dependencies, change history, and business context. Together, these capabilities make the Assets page the central reference point for understanding what data exists, how reliable it is, and how it connects to the rest of the data ecosystem.
