Dashboards list page: folders, brand modes, richer statuses

The stock Superset dashboards list is a flat table designed for ten dashboards, not six hundred. Our fork rebuilds the page around multi-brand scoping, a curated folder tree and a richer status lifecycle so owners can actually find and govern what they ship.

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.

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

Guided tour

What changes in the dashboards list

Hover or tap a pin to see how each block maps to a real operational ask. Every change answers a question stock Superset simply doesn't ask at scale.

Annotations

Inside a folder

Folder view: card grid with ownership and status on every tile

Opening a folder switches the right pane from a table to a card grid scoped to that folder. Stock Superset has no folder concept — its global thumbnail toggle gives back the same flat list with bigger tiles. Our fork turns each card into a self-contained record with description, owner, status and quick actions.

BaselineApache Superset 4.1 (baseline)No baseline equivalent

No baseline equivalent

Not available in Apache Superset 4.1

Baseline Superset has no folders and no per-card metadata beyond the title. The thumbnail toggle only changes the layout of the same flat list — it does not add ownership, description or status at the card level.

Our forkdrafted.work fork

Inside the card grid

How a folder view is built

Each annotation explains one building block of the card grid. The folder structure and its chips are tailored during Superset configuration so navigation mirrors the way your teams actually think about dashboards.

Annotations

Context

Why this matters

A MODE switcher at the top of the sidebar scopes the whole page to ALL, BRAND-1 or BRAND-2 — the same multi-brand split that drives Home and the dashboard properties modal. Within a brand, curated folders replace endless scrolling: each folder carries a visible dashboard count and stable ordering so teams can ship a navigation map instead of a search-only experience.

The status column stops being a binary Published / Draft label and becomes a lifecycle. Icons on each row cover published, in-edit, and additional states surfaced by the fork (maintenance and deprecated among them). Filters are extended with DOMAIN and a dedicated RESPONSIBLE picker, and the OWNERS column is split from RESPONSIBLE so the one accountable maintainer sits next to the full editor list — consistent with the team-and-role model used everywhere else.

Related features

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