Dashboard properties: access model rebuilt

Baseline Superset boils dashboard access down to one flat OWNERS select. Our fork turns the Dashboard properties modal into the control surface for the team-and-role model your organization actually uses.

Side-by-side

See the difference

Flip between layouts. Drag the handle to overlay the two experiences, or open either screenshot for a pixel-level look.

Apache Superset 4.1 (baseline)

Drag the divider. Left of the handle = baseline, right = fork.

Guided tour

What changes in the properties modal

Hover or tap a pin to see how each field maps to an organizational concept. Every change is a direct answer to a real operational ask.

drafted.work fork

Follow-up modal

SELECT TEAMS OR ROLES — the picker that doesn't exist upstream

Clicking SELECT TEAMS OR ROLES opens a dedicated picker. Stock Superset has no equivalent — it ships a single plain OWNERS search. Our fork offers a full picker scoped to your org structure, from departments down to individual users.

Our forkdrafted.work fork

Inside the picker

How the picker is built

Each annotation explains one building block of the modal. The picker is tailored during Superset configuration so its filters and labels match the department structure and vocabulary your org already uses.

drafted.work fork

Context

Why this matters

Description becomes a required field, so every dashboard ships with context — not just a title. A multi-brand DOMAIN tag marks which product line the dashboard belongs to and flows downstream into Home, search and access scoping.

Access splits into two explicit lists: who can edit and who can view. Both accept teams and individual users. A dedicated RESPONSIBLE slot names the one chief maintainer accountable for the dashboard — while legacy multi-owner behavior stays in place for edit rights in parallel.

Related features

Capabilities that usually ship alongside this one. Package tags tell you where each feature lives in our delivery plans.