How Databricks Dashboards Handle Permissions, Caching and Refresh

Databricks AI/BI dashboards run each query under either the publisher's or the viewer's credentials, and the publish settings determine which applies. Results are served from a dashboard cache or a query result cache first, so the SQL warehouse only starts when those caches cannot answer. Shared permissions give all viewers a single cache and identical results, while individual permissions create a separate cache per user. Viewers always see the most recently published version, with draft edits staying hidden until republished. Because the shared option can expose data to people without direct table access, administrators should check the audience before publishing.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)
Log in to join the discussion and vote.
Log in