Databricks Dashboards: How Permissions and Refresh Work for Developers
A deep dive into Databricks dashboard permissions, refresh options, and best practices for managing shared and individual data access.

CANADA — Databricks dashboards offer two key permission models—shared and individual data access—that determine how queries are executed and cached for viewers. When publishing a dashboard, developers must choose between 'Share data permission,' which uses a single credential for all queries and caches results centrally, or 'Individual data permission,' where each viewer's queries run with their own credentials, applying row-level security and column masking.
The shared permission model improves performance by caching results for all users but requires careful access control since viewers may see data they lack direct table permissions for. Individual permissions ensure data isolation but come with higher query overhead, as each user triggers separate executions. The publish dialog warns administrators that switching from shared to individual permissions will pause all scheduled refreshes and remove subscribers.
Developers can publish dashboards via the UI or API, with the embed_credentials parameter controlling permission behavior. The UI also offers a beta 'Materialize datasets' option that automatically schedules daily refreshes. For shared dashboards, publishers can designate either a user account or service principal as the credential source, reducing dependency on individual accounts.
Sharing settings provide four access levels—CAN VIEW, CAN RUN, CAN EDIT, and CAN MANAGE—with workspace-agnostic users limited to CAN RUN access. Organizations can enable broad access by setting sharing to 'Anyone in my account can view,' though non-workspace members can't access draft versions. These permission structures help balance data security with collaboration needs in enterprise BI and AI dashboard deployments.
Reported with files from DEV Community.
NewsCritical Check Point Vulnerability CVE-2026-123039 Exploited in PHP2Shell Campaign
Security researchers detail post-exploitation evidence and recovery steps for the exploited Check Point CVE-2026-123039 vulnerability with CVSS 7.8 score.
NewsDeveloper Reveals Method for Scraping App Store Reviews Without Proxies
A Node.js developer shares a technique for extracting international App Store review data in JSON format, enabling sentiment analysis without complex scraping infrastructure.
NewsDatabricks SQL AI Forecast V2 Adds Holiday Support and Covariates
Databricks SQL's ai_forecast function now supports holiday effects and covariates, streamlining time-series forecasting directly within SQL queries.
NewsHow a WordPress LMS Front End Was Rebuilt with React and Cloudflare Pages
A team modernized a WordPress LMS front end using React and Cloudflare Pages while maintaining core functionality like logins and payments.