The signed embed contract must protect governed drill-downs without blocking legitimate analysis.
External viewers need live detail under their own permissions, while customer administrators need access decisions they can audit.
Who you’d be doing this for
“My regional lead clicked into a chart and asked why she could see another region's numbers.”
Vida Sahin · Business Intelligence Manager
Runs embedded operational dashboards for regional leaders who need governed access to current performance data.
What is at stake
Some embedded viewers can reach restricted detail after drilling into a chart. You must weigh a permanent token cutover against proof that every viewer’s access remains governed.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- interactive drill-downs vs. per-viewer governance
- customer migration timing vs. verified access evidence
- shared token contracts vs. individualized permissions
- authorized exploration vs. conservative release scope
Why Databricks
AI/BI dashboards depend on Unity Catalog permissions to keep embedded data useful for each viewer without exposing governed rows or columns.
Written with these in mind
Not your kind of problem? 107 more at Databricks, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.