Any way to navigate from Dashboard A to Dashboard B other than Markdown in Superset 6.0.0?

[anandita0102]

Hi everyone,

I'm using Apache Superset 6.0.0 (self-hosted) and I'm looking for ways to navigate from one dashboard to another.

I've already tried the Markdown component method — adding a Markdown chart with a hyperlink to the target dashboard URL — and it works fine. But I'd like to explore if there are any other built-in or recommended approaches available in 6.0.0.

What I've already tried:

• ✅ Markdown component with a static hyperlink to Dashboard B — works, but it's not interactive or context-aware

What I'm looking for:

1. Any chart-level interaction (click, right-click context menu) that can redirect a user to another dashboard
2. A way to pass filter context from Dashboard A to Dashboard B via URL parameters or permalinks
3. Any native feature or feature flag in 6.0.0 that supports dashboard-to-dashboard navigation

What I've looked into but am unsure about:

• DRILL_BY and DRILL_TO_DETAIL feature flags — these seem to open modals rather than navigate to another dashboard
• Permalink / filter state API (POST /api/v1/dashboard/<id>/filter_state) — can this be used to construct a link from Dashboard A that opens Dashboard B with pre-applied filters?
• Cross-filtering — appears to only work within the same dashboard, not across dashboards

I have searched existing discussions and didn't find a solution specific to version 6.0.0. Any guidance, examples, or pointers to relevant PRs would be really helpful!

Thanks in advance

[dosubot[bot]]

Hi @anandita0102! I'm Dosu and I’m helping the superset team.

There's no native "click-to-navigate-to-another-dashboard" feature in Superset, but beyond the Markdown approach you've already tried, here are the other options available:

1. URL Parameters with Native Filters

You can construct dashboard URLs that pre-apply filter values using native filter URL parameters. The two key parameters are:

• native_filters_key — a stored key reference to filter configuration
• native_filters — direct rison-encoded filter state

This lets you build a link from Dashboard A that opens Dashboard B with specific filters already applied [1]. You'd still embed these links in Markdown or elsewhere, but the filter context carries over. Recent fixes (May 2026) improved reliability of URL parameter preservation in multi-tab scenarios [2].

2. Permalink API

The /api/v1/dashboard/{id}/permalink endpoint creates stable URLs that preserve:

• dataMask (filter state)
• activeTabs (which tabs are open)
• anchor (scroll to a specific component)

You could programmatically generate permalink URLs from Dashboard A that open Dashboard B with pre-applied filters — this is more robust than manually constructing native filter URL params.

3. Regarding Drill By / Drill to Detail

You're correct — both DRILL_BY and DRILL_TO_DETAIL are enabled by default since Superset 4.0 [3], but they open modals for in-place exploration rather than navigating to another dashboard. They won't help with cross-dashboard navigation.

4. Cross-Filtering

Also correct — cross-filtering only works within a single dashboard, not across dashboards.

What's not available (yet):

• There's no chart-level click action that directly redirects to another dashboard. A "Drill to Dashboard" feature (e.g., clicking a map point to navigate to a filtered dashboard) has been discussed but isn't available in a released version yet [4].

Practical recommendation: Your best bet for context-aware navigation is combining the Markdown hyperlink approach with native filter URL parameters or permalink URLs. This gives you the "pass filter context from Dashboard A to Dashboard B" behavior you're looking for — it's just not triggered by a chart click, but rather through a pre-constructed link.

To reply, just mention @dosu.

---

Docs are dead. Just use Dosu.

[anandita0102]

I'm exploring dashboard-to-dashboard navigation in Apache Superset 6.0.
I was able to interlink dashboards using a Text/Markdown component and also observed that Superset preserves dashboard filter state using native_filters_key.
My use case is:

• Dashboard A and Dashboard B have the same native filters (e.g., userid, region, etc.).
• A user selects filters on Dashboard A.
• When navigating to Dashboard B, I would like the currently selected filters of Dashboard A to be automatically applied on Dashboard B as well.

For example:

Dashboard A
userid = abc
region = North

↓ Navigate

Dashboard B
userid =  abc
region = North

Is there any native way to achieve this in Superset (6.0)?
Any guidance or recommended approach would be appreciated.
Thanks!

[dosubot[bot]]

There's no built-in "share filter state across dashboards" feature in Superset, but here's what I found about how the mechanisms work and what your options are:

Why native_filters_key won't work cross-dashboard: The key is scoped to a specific dashboard — the cache lookup uses cache_key(resource_id, key) where resource_id is the dashboard ID [1]. So the same key on Dashboard A and Dashboard B would reference different (or non-existent) entries. The Permalink API is similarly dashboard-bound [2].

Your best option: the native_filters URL parameter (rison-encoded)

Superset still supports a native_filters URL parameter that encodes filter state directly in the URL [3]. When Dashboard B loads with this parameter, it decodes the rison and applies it as the dataMask [4]. This is portable between dashboards because it's not tied to server-side storage.

The key requirement: The native filter IDs must match between Dashboard A and Dashboard B. If both dashboards define the same filters (e.g., userid, region) and those filters have the same filter component IDs, then a rison-encoded URL parameter from Dashboard A will apply correctly on Dashboard B.

Practical approach:

1. In your Markdown link on Dashboard A, construct the Dashboard B URL with ?native_filters=<rison_encoded_state>
2. The rison value should encode the dataMask object with filter values keyed by filter ID

However, there's a catch — this requires either:

• Manually ensuring filter IDs match (e.g., by editing dashboard JSON metadata to align filter UUIDs), or
• Building a small middleware/script that reads Dashboard A's current filter state and maps it to Dashboard B's filter IDs

Alternative API-based approach:

1. Read filter state from Dashboard A via GET /api/v1/dashboard/{A_id}/filter_state/{key} [5]
2. Create a new filter state entry for Dashboard B via POST /api/v1/dashboard/{B_id}/filter_state
3. Use the returned key in your Dashboard B URL as ?native_filters_key=<new_key>

This requires custom programmatic logic but gives you clean URLs.

Bottom line: Superset doesn't natively propagate filter state across dashboards automatically. The native_filters rison parameter is the closest thing to a portable solution, but it requires matching filter IDs between dashboards. If your filters have different IDs (which is the default when created independently), you'd need to either align them manually or build a mapping layer.

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.