User admin tooling: search, user profile page, and bulk owner reassignment
Baseline Superset ships a single flat table as its entire user administration surface. Our fork turns user management into a real admin tool: a searchable index for 2000+ users, a per-user profile page that lists every dashboard, chart and dataset they own, and a one-modal bulk reassign-owner flow when people move teams or leave.
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 users list
Hover or tap a pin to see how each column maps to a real admin task. Every addition is a direct answer to a question baseline Superset can't answer without opening a database console.
Post-search flow
From the list to the user: profile page and bulk owner reassign
Opening a user continues the admin flow on a dedicated profile page. Every asset they own is listed, filterable and selectable — and one modal re-routes ownership across every selected asset in a single transaction. Neither surface exists in upstream Superset; showing them side-by-side makes the flow obvious.
Opening a user lands on their profile page: a stable identity card (id, username, email, team, login count, created, last login) plus tabs for every dashboard, chart and dataset they own.
Inside the profile page
How the user profile page is built
Each annotation explains one block of the profile. The page is designed to answer the three admin questions 'who is this', 'what do they own' and 'can I act on it' without a context switch.
Inside the modal
How the Change Asset Ownership modal is built
Each annotation explains one piece of the reassignment contract. The modal is intentionally verbose about what it will and won't do — bulk ownership moves survive offboarding, audits, and 'who did this?' months later.
Context
Why this matters
The users index is the first place platform owners land when onboarding, offboarding, or auditing. The baseline list breaks down once you have more than a screenful of users — no filters per column, no team, no login signal. Our fork replaces it with a proper admin index: per-column filters at the top and sortable columns for every piece of user metadata the fork stores.
Click any user and you land on a dedicated user profile page. The left-hand card carries the stable identity (user id, username hash, email, team, login count, created, last login). The right-hand area switches between DASHBOARDS / CHARTS / DATASETS tabs and lists every asset the user owns, with owner avatars, publish state, last-modified date and inline edit. It's the page platform owners actually reach for when someone asks 'what does Lucas own here?'.
The Change Asset Ownership modal closes the loop on offboarding. Multi-select assets on a user's profile, open the modal once, point SOURCE OWNER → TARGET OWNER, and the fork rewrites ownership across every selected asset in one transaction. No SQL script, no one-at-a-time edits, and the confirmation explicitly spells out what's about to change so it can't be triggered by accident.
Related features
Keep exploring the fork
Capabilities that usually ship alongside this one. Package tags tell you where each feature lives in our delivery plans.
