Last updated: November 17, 2026
This page lists the changes in v6.1.x that may need action from you when your workspace moves from v6.0 to v6.1.x. It only covers changes you need to prepare for. For all other changes, see the Preset changelog.
We update this page as new v6.1.x releases ship, and remove entries once they no longer need action. Each entry shows the v6.1.x release we verified it on. To see which version your workspace runs, open Settings in the top-right menu and scroll to the bottom of the list: the version appears under About (for example, "Version: 6.1.0.13").
Summary
| Change | Who is affected | What to do |
|---|---|---|
| "Owners" is now "Editors" | Anyone who manages owners through the API | Move scripts to editors and subject IDs. Never send user IDs in editors |
| Draft dashboards open only for their editors | Teams who share links to Draft dashboards | Publish dashboards that others need to open |
| Dashboard link structure updated | Users with bookmarked dashboard URLs | Save the updated dashboard URL |
{{ from_dttm }} and {{ to_dttm }} removed |
Virtual datasets and custom SQL that use these Jinja variables | Replace them with get_time_filter() before upgrading |
Custom CSS: some .ant-* class names changed |
Dashboards with custom CSS that targets .ant-* classes |
Update the class names in your CSS |
| Custom CSS: chart tiles have a default border, corners and shadow | Dashboards with custom CSS that styles chart tiles | Use a more specific selector for chart tile styles |
"Owners" is now "Editors"
What changed
Owners are now called editors. An editor has the same rights an owner had on the asset.
In the app:
- Dashboard and chart properties show an Editors field instead of Owners.
- Dashboard, chart and alert lists have an Editor filter and an Editors column.
- Alerts and reports use the same Editors field.
In the API:
- Dashboards, charts, datasets and alerts/reports have an
editorsfield. It holds subject IDs, not user IDs. - Every user has a subject ID, and it is usually a different number from their user ID. Look it up with
GET /api/v1/security/subject/, filtering onuser_id:
GET /api/v1/security/subject/?q=(filters:!((col:user_id,opr:eq,value:<user_id>))) - To list the subjects you can assign, use
GET /api/v1/dashboard/related/editors(or/chart/,/report/). - To change editors, send
editorswith subject IDs, for examplePUT /api/v1/dashboard/<id>with{"editors": [<subject_id>, ...]}.
The owners field still works, but is deprecated
The legacy owners field (user IDs) and related/owners still work on dashboards, charts, datasets and alerts/reports, so existing scripts keep working. They are deprecated: move to editors, which is the standard going forward.
- There is no removal date.
ownersstays supported until further notice. - Send either
ownersoreditors, not both. Sending both in one request returns 400 "Use either owners (user IDs) or editors (subject IDs)."
editorsIf a script only renames owners to editors but keeps sending user ID values, the request succeeds (HTTP 200), and the editors become whoever holds those subject IDs, which can be different people.
Convert user IDs to subject IDs before sending them in editors. Until a script has been migrated, keep it sending user IDs in owners.
MCP
- MCP responses don't include owners or editors. This is by design, for privacy.
- The
editorfilter in MCP list tools takes a user ID (you can find one with thefind_userstool), while the API'seditorsfield and filter take a subject ID. They are different IDs, so the same number can mean different people. Don't reuse IDs between the two.
Who is affected: anyone with scripts, integrations or MCP workflows that read or set owners.
What to do before upgrading
- Find scripts and integrations that read or set owners, including any that use
ownersorrelated/owners. - Move them to
editors, converting user IDs to subject IDs. - Check that nothing sends user IDs in
editors.
Status: Permanent change. owners remains available as a deprecated field.
Draft dashboards open only for their editors
What changed
In v6.0, a user with access to a dashboard's data could open a Draft dashboard through a direct link, even if they were not an owner and it didn't appear in their dashboard list.
In v6.1.x, a user who isn't an editor of a Draft dashboard gets a "Page not found" (404) page when opening its link, even if they have access to its data. Editors open it as before.
Who is affected: teams who share links to Draft dashboards, for example with users in the Dashboard Viewer role.
What to do
- Publish dashboards that other people need to open.
- Or add those people as editors of the Draft dashboard. What being an editor allows depends on the user's workspace role:
- Viewer, Dashboard Viewer and Dashboard Interactor: they can open the dashboard, but they still can't edit it.
- Other workspace roles: they can open the dashboard and edit it.
Status: Expected behavior in v6.1.x.
Dashboard link structure updated
What changed
Dashboard links now use the format /dashboard/<id>/. Older links in the format /superset/dashboard/<id>/ redirect to the new format, so they keep working, and the same rule applies to them.
The old structure continues to work and redirects to the new structure automatically, until further notice.
Who is affected: users accessing dashboards via a saved/bookmarked link.
What to do
Update the saved URL to the new structure.
Migrating from from_dttm / to_dttm
What changed
The {{ from_dttm }} and {{ to_dttm }} Jinja variables were deprecated in Superset 5.0 and are no longer available as of v6.1.x. If a virtual dataset or custom SQL still uses them, the text {{ from_dttm }} is sent to the database unchanged and the query fails.
Who is affected: anyone with virtual datasets or custom SQL (for example in charts) that use {{ from_dttm }} or {{ to_dttm }}.
What to do before upgrading
Replace them with get_time_filter():
-- Before
WHERE dttm >= '{{ from_dttm }}' AND dttm < '{{ to_dttm }}'
-- After
{% set tf = get_time_filter("dttm", default="Last week") %}
WHERE dttm >= {{ tf.from_expr }} AND dttm < {{ tf.to_expr }}
- Pass the name of the time column your chart filters on (
"dttm"in the example). from_exprandto_exprare complete SQL expressions, so don't wrap them in quotes.- If no time range is applied and no default is set, they render as
None. Either set a default, or wrap each condition in{% if tf.from_expr %} … {% endif %}.
Status: Permanent change.
Custom CSS: some .ant-* class names changed
What changed
The Preset interface is built with the Ant Design component library. In v6.1.x, Ant Design was upgraded from v5 to v6, and v6 renamed several of its internal CSS classes.
Dashboard CSS is still applied as before. But any rule whose selector uses an old .ant-* class name no longer matches anything, so that style silently stops applying. The rest of your CSS keeps working.
The renames most likely to affect dashboards:
| v6.0 (Ant Design v5) | v6.1.x (Ant Design v6) | Where it appears |
|---|---|---|
.ant-tabs-content-holder |
.ant-tabs-body-holder |
Dashboard tabs: area below the tab bar |
.ant-tabs-content |
.ant-tabs-body |
Dashboard tabs: wrapper around the tab panes |
.ant-tabs-tabpane |
.ant-tabs-content |
Dashboard tabs: a single tab pane |
.ant-select-selector |
.ant-select-content |
Dropdowns, such as native filter selects |
.ant-select-selection-placeholder |
.ant-select-placeholder |
Dropdown placeholder text |
.ant-select-arrow |
.ant-select-suffix |
Dropdown arrow |
.ant-tooltip-inner |
.ant-tooltip-container |
Tooltips |
.ant-popover-inner |
.ant-popover-container |
Popovers |
.ant-steps-item-tail |
.ant-steps-item-rail |
Step indicators |
For the complete list, see the Ant Design v6 migration guide.
.ant-tabs-content now means a different element.ant-tabs-content exists in both versions, but it targets a different element. In v6.0 it is the wrapper around all tab panes. In v6.1.x it is a single tab pane. A rule that uses it keeps applying, but to a different element, so check how it looks after upgrading.
.ant-select-content covers only the text areaIn v6.0, .ant-select-selector covers the whole dropdown box. In v6.1.x, .ant-select-content covers only the text area, not the arrow. A background color set on .ant-select-content doesn't fill the whole box.
Superset's own dashboard classes did not change, for example .dashboard-component-chart-holder, .dragdroppable-row, .dragdroppable-column, .grid-content, .dashboard-header, .header-title and .dashboard-component-tabs.
Who is affected: dashboards with custom CSS (added with Edit CSS or from a CSS template) that targets .ant-* classes.
What to do
-
Search your dashboard CSS for
.ant-. -
Replace each old class name with its new name from the table above.
-
To keep one stylesheet working on both v6.0 and v6.1.x while you upgrade, list the old and new names together:
/* Area below the dashboard tab bar, in v6.0 and v6.1.x */ .ant-tabs-content-holder, .ant-tabs-body-holder { background-color: #fff3cd; } /* A single tab pane, in v6.0 and v6.1.x */ .ant-tabs-tabpane, .ant-tabs-body > .ant-tabs-content { padding: 12px; } -
Some components, such as dropdowns, have built-in styles that are more specific than a single class, in both v6.0 and v6.1.x. If a rule with the correct class name still doesn't apply, add
!importantor use a more specific selector:/* Native filter dropdown placeholder, in v6.0 and v6.1.x */ .ant-select-selection-placeholder, .ant-select-placeholder { color: #d32f2f !important; font-weight: 700 !important; } -
Where possible, use Superset's dashboard classes instead of
.ant-*classes. Ant Design's internal class names can change again in future library upgrades.
Right-click the element and choose Inspect in your browser. If your rule doesn't appear in the Styles panel at all, its selector no longer matches, which usually means a class was renamed. If it appears crossed out, a more specific built-in rule is overriding it (see the next section).
Status: Permanent change.
Custom CSS: chart tiles have a default border, corners and shadow
What changed
In v6.1.x, each chart tile on a dashboard (.dashboard-component-chart-holder) has a built-in border, rounded corners, a light shadow and a background color. In v6.0, the tile only had a background color, with no border.
Dashboards look slightly different even without custom CSS: chart tiles now show a thin border.
These built-in styles use a more specific selector than a single class. So a rule like this worked in v6.0 but is overridden in v6.1.x:
/* Worked in v6.0. Overridden in v6.1.x */
.dashboard-component-chart-holder {
border: 2px solid #1565c0;
border-radius: 12px;
}
Rules that already use a more specific selector, such as .grid-content .dragdroppable-row .dashboard-component-chart-holder, still apply.
Who is affected: dashboards with custom CSS that sets border, border-radius, box-shadow or background-color on chart tiles with a single-class selector.
What to do
Make the selector more specific. This works in both v6.0 and v6.1.x:
div.grid-container .dashboard-component-chart-holder,
div.grid-container .dashboard-component-chart-holder.fade-out {
border: 2px solid #1565c0;
border-radius: 12px;
box-shadow: none;
}
- The second selector is needed to override the default shadow.
- To remove the new default border instead, set
border: none;with the same selectors. - Adding
!importantto each declaration also works, but a more specific selector is easier to maintain.
Status: Expected behavior in v6.1.x