Hide/remove the "Charts" section in landing page for certain users

[georgeteena]

Hi,

I have a multi-tenancy enabled Superset installation. For some external user dashboards, I need to give dashboard view only access. For such users, is it possible to hide/disable the "Charts" widget/section in the landing page?
Does this require front end changes?

Thanks,
Teena

@dosu

[dosubot[bot]]

Hi Teena,

There's currently no built-in configuration or role-based setting to hide the Charts section from the landing page for specific users. The only section that currently respects permissions is Saved Queries, which hides itself if the user lacks can_read on that resource [1].

A community PR (#33946) has been submitted to hide the Charts section based on can_write permissions, but it's still awaiting review [2].

Best workaround today — bypass the welcome page entirely by redirecting users to /dashboard/list/ using FLASK_APP_MUTATOR in your superset_config.py [3]:

from flask_appbuilder import expose, IndexView
from flask import g, redirect

class SupersetDashboardIndexView(IndexView):
    @expose('/')
    def index(self):
        if not g.user:
            return redirect('/login')
        return redirect('/dashboard/list/')

def mutate_app(app):
    from superset.extensions import appbuilder
    appbuilder.indexview = SupersetDashboardIndexView
    return app

FLASK_APP_MUTATOR = mutate_app

You could make this conditional per role if you check g.user.roles before deciding where to redirect.

Other options:

• The welcome page has a 'welcome.main.replacement' extension point [4] that could theoretically replace the entire main content area with a custom implementation, though documentation on this is limited.
• SIP-198 / Issue #37016 proposes full homepage customization (toggleable widgets, role-based layouts, etc.), but it's still a proposal [5].
• Direct frontend modifications to superset-frontend/src/pages/Home/index.tsx [6] would work but are not recommended since you'd need to maintain a fork and deal with merge conflicts on upgrades.

So to answer your question directly — yes, selectively hiding the Charts section today would require either frontend changes or using the redirect workaround above to avoid the welcome page altogether.

To reply, just mention @dosu.

---

Docs are dead. Just use Dosu.

[georgeteena]

@dosu

Code review comment - appbuilder.indexview cannot be overridden like above — FAB registers routes at init time, so post-init mutation has no effect. The before_request hook is the correct mechanism for runtime redirects.

What worked:

DASHBOARD_ONLY_ROLES = {"role-1", "role-2"}

def is_dashboard_only_user():
    if not g.user or g.user.is_anonymous:
        return False
    user_role_names = {role.name for role in g.user.roles}
    return bool(user_role_names & DASHBOARD_ONLY_ROLES)

def flask_app_mutator(app):
    @app.before_request
    def redirect_welcome_page():
        # List of welcome page paths to intercept
        welcome_paths = [
            "/",
            "/superset/welcome/",
            "/superset/welcome",
            "/welcome/",
            "/welcome",
        ]

        if request.path in welcome_paths:
            if hasattr(g, "user") and g.user and not g.user.is_anonymous:
                if is_dashboard_only_user():
                    logger.info(f"Redirecting user '{g.user.username}' from {request.path} " "to /dashboard/list/")
                    return redirect("/dashboard/list/")
        return None

    return app

[dosubot[bot]]

Great catch — you're right that appbuilder.indexview can't be reliably overridden via FLASK_APP_MUTATOR since FAB registers its routes at init time. The before_request hook is the correct approach for runtime redirects.

Thanks for sharing the working solution! The role-based check with DASHBOARD_ONLY_ROLES is a clean pattern, and intercepting all the welcome page path variants ensures nothing slips through. This should be very helpful for Teena and anyone else with a similar multi-tenancy setup.

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.