Skip to main content
dbt exposures document which downstream tools and dashboards depend on your dbt models. Omni can generate exposures from your published dashboards and push them to your dbt repository, giving your data engineering team visibility into how models are consumed.

​
What exposures include

When you push exposures from Omni, each published dashboard generates an exposure file containing:
  • The dashboard name and URL
  • The dbt models that the dashboard depends on
  • Metadata about the exposure (owner, type)
Exposure files are created in the models/omni_exposures/ directory of your dbt repository.

​
Requirements

To follow the steps in this guide, you’ll need:
  • An Omni connection with a configured dbt integration
  • Connection Admin permissions for the connection in Omni
  • Write access on the deploy key used to connect dbt to Omni. See deploy key setup for more information.

​
Pushing exposures to dbt

1

Open the dbt settings

  1. In Omni, navigate to Settings > Connections and select your connection.
  2. In the connection’s settings, click the dbt tab.
2

Push exposures

Click Push exposures to dbt. Omni will generate exposure YAML files and push them to your repository.
3

Complete the pull request

Review and merge the pull request in your Git provider.

​
Scope and limitations

  • Published dashboards only — Exposures are generated from published (shared) dashboards. Private dashboards and workbooks are not included.
  • No automated scheduling — Exposure pushes are manual. There is currently no API endpoint or scheduled option for automated exposure sync.
  • File location — Exposures are pushed to models/omni_exposures/ in your repository. The file path is not currently customizable.
  • Exposure names — Omni generates exposure names from dashboard titles. If a dashboard title contains special characters or emoji, the resulting exposure name may trigger dbt deprecation warnings about invalid naming conventions.

​
Next steps

  • Create and edit dbt models — Author new dbt models from Omni queries or edit existing models and push changes back to your dbt repository.