Urgent.News

What's breaking now, across hundreds of outlets.

Tech

How Databricks Dashboards Handle Permissions and Refresh

Databricks dashboards run every query with someone's permissions and answer it from one of several caches, and the choices you make when you publish decide which. This guide follows an AI/BI dashboard after it is built: you publish it, share it, schedule it and add subscribers. It explains whose credentials run each query, where the results come from, and how to keep the data fresh. The complete…

Databricks dashboards handle permissions and refresh through a series of steps involving publishing, sharing, scheduling, and subscriber management. When publishing a draft, viewers see the last published version. For drafts, viewers' data permissions always apply, while for published versions, the choice of data permission determines whose credentials run the queries and where the results come from.

There are two data permission options: Share data permission and Individual data permission. Share data permission uses the publisher's credentials for every viewer's queries and stores results in a shared cache. This option is suitable when many people view the same dashboard and you want one shared cache, but it may expose data to people who do not have direct access.

Individual data permission, on the other hand, runs queries using each viewer's own credentials, ensuring they can only see the data they are allowed to see. This option is ideal when each viewer must see only the data they are permitted to access.

Sharing a dashboard determines who can open it and what they can do. Users can be granted CAN VIEW and CAN RUN permissions (the default), CAN EDIT permissions (to edit and publish), or CAN MANAGE permissions (to change permissions and delete the dashboard). With Share data permission, all viewers share one cache and see the same results.

With Individual data permission, each viewer has a per-user cache. When sharing with everyone in the Azure Databricks account, users who do not have access to the workspace are limited to CAN RUN and cannot open the draft.

A schedule is essential for refreshing the dashboard cache. Users can set up a schedule to run the dashboard's queries at regular intervals. The schedule's advanced settings allow users to choose the SQL warehouse for the run and specify whether to use current filter selections. Run now can be used to execute the schedule once without changing its regular cadence.

Subscribers receive a snapshot of the dashboard each time the schedule runs. Email subscribers receive a PDF snapshot with optional CSV, TSV, or Excel data attachments. Up to 100 subscribers can be added to a subscription list, and attachments over 9 MB are not included.

Rewritten by urgent.news; may contain errors — check the original.

Source: dev.to

Read the original at dev.to →

Report a problem with this story

More in Tech

Scraping App Store reviews across countries without proxies (and turning them into a sentiment dataset)

AI disclosure: This article was written with AI assistance (Claude). The code is condensed from a scraper I maintain, and every number in the output sections came from actually running the scripts…

  • Gather App Store reviews from four countries using JSON endpoints
  • Utilize customer-reviews RSS feed and iTunes Lookup API with Node.js fetch
  • Convert reviews into labeled JSONL dataset (positive/neutral/negative)

CVE-2026-123039 Recovery: Webshells, Persistence and Post-Exploitation Evidence

CVE-2026-123039 Recovery: Webshells, Persistence and Post-Exploitation Evidence Installing a fixed Check Point build addresses CVE-2026-123039.

  • Local user can execute commands with root privileges via DynamicCLI daemon.
  • Exploitation requires local execution context like PHP2Shell on Mobile Access portals.
  • Update to R82.20 Take 14 or later to mitigate vulnerability risk.

More from Sunday 22 November →