GitHub user worker123-tech created a discussion: Question: How to apply 
per-user theme to embedded dashboards without modifying global dashboard 
configuration?

### Environment

* Superset version: 6.1.0rc1
* Deployment: Docker
* Usage: Embedded dashboards (iframe) inside a custom frontend UI

---

### Problem Description

I am embedding Superset dashboards into my own frontend application.
In my application, users can switch between different UI themes (e.g., light / 
dark / custom brand themes).

---

### Expected Behavior

When a user switches the theme in the frontend UI:

* Only the **current user’s view** of the embedded dashboard should change
* The theme change should be **isolated per user session**
* It should **NOT modify the dashboard globally in Superset**

---

### Current Approach

Currently, I am updating the dashboard configuration via API:

```http
PUT /api/v1/dashboard/{id}
```

For example:

```json
{
  "json_metadata": {
    "color_scheme": "custom_theme"
  }
}
```

---

### Issue

This approach updates the dashboard at the database level, which results in:

* All users seeing the updated theme
* No way to apply different themes per user
* Theme changes are global, not session-based

---

### Key Requirement

I am looking for a way to:

* Apply theme dynamically per user (e.g., via embedding, URL params, or session 
context), theme of dashboard and chart will be  all changed
* Avoid modifying dashboard metadata in the database
* Keep theme changes isolated to individual users

---

### Questions

1. Is there any supported way in Superset to apply themes at the **user/session 
level** instead of globally?
2. Can themes be controlled dynamically when embedding dashboards (e.g., via 
URL parameters or API)?
3. Is there any recommended approach to achieve per-user theming for embedded 
dashboards?

---

### Additional Notes

* The dashboards are embedded via iframe
* Frontend and Superset are under the same domain
* I want to avoid modifying Superset source code if possible

---

Any guidance or recommended best practices would be greatly appreciated.

Thanks!


GitHub link: https://github.com/apache/superset/discussions/38900

----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: 
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to