Exposures name the dashboards and apps that depend on your DAG

Exposures record that a dashboard, notebook, analysis, ML pipeline, or application depends on specific dbt resources. Manual exposures live under an exposures key in YAML; automatic downstream exposures for supported integrations appear in Catalog and behave like manual ones without YAML files.

Data teams use them to select and test only what feeds a critical consumer surface, and to give non-producers a dedicated docs page with owner, maturity, URL, and dependency context. Types organize those uses in the documentation site.

Linking consumer systems back to models, sources, and metrics makes downstream meaning explicit in the graph: shared definitions include not only how data is built but where it is relied upon.