Skip to main content

Crawl Databricks AI/BI dashboards

Connect docs via MCP
Private Preview

Databricks AI/BI dashboard support is in private preview and is enabled per tenant. The Import AI/BI Dashboards and Enable Dashboard Lineage options stay hidden in the workflow setup until the feature is enabled for your tenant. To request access, raise a support request.

Atlan can discover and catalog Databricks AI/BI dashboards, also known as Lakeview dashboards. Once crawled, each dashboard appears in Atlan as a Dashboard asset alongside your other Databricks assets, and you can extract lineage from the dashboard to the Unity Catalog tables and columns it reads.

Dashboard metadata comes from the Databricks Lakeview REST API, not from Unity Catalog system tables. This means dashboard crawling requires the System Tables extraction method and depends on workspace-level access controls rather than catalog grants.

Prerequisites

Before crawling dashboards, make sure you have:

Permissions required

In addition to the standard Databricks connector permissions, the Atlan service account requires:

  • CAN VIEW on every dashboard you want to catalog, or on the workspace folders that contain them. Granting CAN VIEW at the workspace level covers all current and future dashboards without per-dashboard grants.
  • CAN MANAGE on a dashboard if you want Atlan to populate its owners. This is optional—see Dashboard owners.

For the full privilege breakdown, see Permissions for Databricks AI/BI dashboards. If dashboards are missing after crawling, see Why are some dashboards missing after crawling?.

Configure crawler

To configure the crawler for dashboards:

  1. Follow the standard Crawl Databricks steps.
  2. For the extraction method, select System Tables. The Import AI/BI Dashboards option isn't available with the REST API or JDBC methods.
  3. Turn on Import AI/BI Dashboards.
  4. Run the workflow.

After the workflow completes, Dashboard assets appear in Atlan under the crawled connection.

Not supported with cross-workspace extraction

Atlan skips the dashboard crawl when cross-workspace extraction is turned on. You can turn on both options, but the workflow succeeds without producing any dashboards. Run a single-workspace crawl to catalog dashboards.

Turn off dashboard crawling

If you turn off Import AI/BI Dashboards after a crawl has already published dashboards, the next run removes those dashboards from Atlan. The crawler stops extracting them, so they're absent from the snapshot Atlan compares against the previous run, and Atlan archives them.

Turning the option back on re-crawls your dashboards, and they reappear with their metadata on the next run.

Lineage isn't restored by the crawl alone

Re-enabling the option restores dashboard assets, but not their lineage. Run the lineage and usage workflow with Enable Dashboard Lineage turned on to rebuild lineage.

Dashboard owners

Atlan sets a dashboard's owners from the users granted CAN MANAGE on it. Group and service principal grants are skipped, because an owner is a person.

Reading these grants requires CAN MANAGE on the dashboard. If the service account doesn't have it, Atlan catalogs the dashboard without owners rather than failing the crawl—so a dashboard with no owners in Atlan usually means the service account couldn't read its permissions.

What Atlan crawls

For each dashboard, Atlan catalogs:

PropertyDescription
NameThe dashboard's display name in Databricks
PathWorkspace path of the dashboard, including its file name
Workspace IDIdentifier of the workspace containing the dashboard
Warehouse IDIdentifier of the SQL warehouse backing the dashboard
Lifecycle stateWhether the dashboard is active or trashed
Genie space enabledWhether the dashboard has an associated Genie space
Source URLDirect link to the published dashboard in Databricks

See also