GitHub user RyanAccuWebCloud added a comment to the discussion: Best Way to Attach Dashboard RBAC Roles Automatically in Superset
Hey, great question. Automatically assigning the Gamma role to all dashboards in Apache Superset isn’t something Superset does natively without some scripting, but there’s a clean, config-driven approach that keeps things maintainable and upgrade-safe. The first thing I’d look at is enabling Dashboard RBAC. You can do this directly in your superset_config.py by setting the DASHBOARD_RBAC flag to True under the FEATURE_FLAGS dictionary. This tells Superset to respect role assignments at the dashboard level instead of just globally. Once that’s in place, your role management becomes more flexible and controlled through configuration rather than code. Next, make use of the superset init command. It’s mainly designed to sync roles and permissions...especially useful after upgrades...but it’s also handy for keeping your RBAC setup consistent across environments. If you integrate this step into your deployment or automation pipeline, it ensures roles like Gamma always have the correct permissions without manual reconfiguration. If you’re running Superset in a managed environment like AccuWeb Cloud, it’s even easier to manage these configs. You just point the SUPERSET_CONFIG_PATH environment variable to your custom config file, and your feature flags and security settings get picked up automatically on deployment. That means less manual tweaking and more predictable behavior across instances. One thing to keep in mind: the Gamma role is intentionally limited for security reasons. Granting it access to all dashboards is a big permission jump, and those users will still need access to the underlying datasets for dashboards to display data properly. So, be mindful of what you’re opening up. Does this align with how you’re currently managing your Superset roles and permissions? GitHub link: https://github.com/apache/superset/discussions/35570#discussioncomment-14626670 ---- 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]
