Onboarding: join-team modal, requests, and confirmation

Baseline Apache Superset has no team catalog, no access-request queue, and no path from first login to the right team and permissions. The fork adds a modal on Home, a multi-step Access tab wizard (role, team matching, new-team request), a confirmation screen, and a My requests list.

Side-by-side

See the difference

This capability has no Apache Superset 4.1 equivalent — there's nothing to slide against. Open the fork screenshot for a pixel-level look.

BaselineApache Superset 4.1 (baseline)No baseline equivalent

No baseline equivalent

Not available in Apache Superset 4.1

Stock Superset has no team onboarding, Access workflow, or request inbox. Platform owners usually add wikis, forms, and spreadsheets outside the product — there is no surface where role, team choice, permission intent, and ticket status live in the same session.

Our forkDrafted fork

Guided tour

First-run join-team modal on Home

Each pin marks a clear fork difference from baseline Superset. The modal brings into the product the flow IT usually handles outside the UI.

Access wizard

Four steps to land on a team

The Access tab connects steps that upstream lacks: matching, a fixed role, pairing with a team, and a request modal with meaningful permission sets.

Multi-step flow

Step 1Team matching by role

Step 1 explains how teams will be suggested and sets paths: to an existing team or to a request when nothing matches.

Step 2Role in the company

Step 2 ties the user to a specific company role. This is typically integrated with corporate directories.

Step 3Recommendations plus search

Step 3 combines recommendations from the role already entered with manual search tabs and a path to create a new team when search is exhausted.

Step 4When the team is not in the list

Creating a new team opens a modal: name, dashboard intent, and permission sets with clear role descriptions.

After submission

Confirmation and request list

Our fork keeps analysts inside the product for the full flow of obtaining team access.

Multi-step flow

Step 1Submission confirmation and path to requests

The success screen confirms that the request is recorded and will be reviewed.

Step 2My requests table with statuses and filter

A full request table with sorting by status.

Context

Why this matters

The journey starts on Home with an explicit join-team modal: clear copy, a primary action, and a deferred exit so navigation is never blocked indefinitely.

The Access tab walks through steps: how teams are suggested, collecting a structured company role for routing, recommendations plus search by name or colleague, then a new-team request modal with permission templates and an explanation alongside. Each screen is one commitment in the process instead of a chain of emails and corporate chat messages.

Related features

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