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

# Column-level lineage in the Catalog

> Trace any column in the Paradime Catalog hop by hop, with edges labelled pass-through, transformed, aggregated, or indirect effects like joins.

*September 3, 2026*

Column-level lineage is now part of the Catalog. On any dbt™ model, source, seed, or snapshot, open the **Columns** tab and click a column: a drawer opens with the lineage graph for that one column, one card per model or source with the columns involved as rows, and edges joining column to column across cards.

* **Every edge says what happened to the value.** Direct edges are labelled Pass-through, Transformed, or Aggregated, and transformed edges are drawn heavier so the places where a value stopped being itself stand out. Indirect edges, where a column decides which rows survive rather than what the value is, are shown muted and labelled Joined, Grouped, Filtered, Sorted, Windowed, or Conditional.
* **Walk the graph without leaving it.** Click a column on any card to refocus the graph on it in place, click a model name to open its catalog page, and set upstream and downstream depth separately (a number of hops, or `+` for everything). Cards at the edge of the current depth can be expanded further in either direction.
* **Honest about what it could not parse.** Each card carries a parse status. A model whose compiled SQL only partially resolved (for example a `SELECT *` without a schema) is marked as such, and a model that could not be parsed falls back to table-level lineage instead of disappearing from the graph.
* **Built for your warehouse.** Compiled SQL is parsed with your warehouse's dialect, so warehouse-specific syntax (BigQuery's backtick identifiers, `EXCEPT`, `STRUCT`, and `UNNEST`, for example) resolves correctly on BigQuery, Snowflake, and Databricks. Parses are cached by content, so a rebuild only re-parses the models that changed.
* **Scoped like the rest of the Catalog.** Lineage is built as a stage of every catalog build, so it follows the environment you are looking at and includes cross-workspace nodes for dbt™ Mesh projects, badged with the workspace they belong to.

Lenses on the drawer narrow the graph further: hide indirect edges to see pure value flow, keep only masked columns when tracing sensitive fields, or drop low-confidence edges. The same graph powers DinoAI's [column-level lineage tool](/products/dino-ai/tools-and-features/column-level-lineage) in the copilot and over MCP.

See [Column-level lineage](/products/data-catalog/lineage/column-level-lineage) for the full walkthrough.

Shipped in Paradime v6.11.0.


## Related topics

- [Changelog](/changelog/overview.md)
- [Column-level lineage](/products/data-catalog/lineage/column-level-lineage.md)
- [Column Level Lineage](/products/dino-ai/tools-and-features/column-level-lineage.md)
- [Column-Level Lineage Diff](/products/bolt/ci-cd/lineage-diff/index.md)
- [Column-Level Lineage Diff for Looker](/products/bolt/ci-cd/lineage-diff/looker.md)