GitHub user dosubot[bot] added a comment to the discussion: no options such as creating users and roles in the Settings menu
<!-- Answer --> If your config and admin role are correct but user/role management options are still missing, here are the most common causes and checks: - Make sure the frontend assets are fully built and loaded. In Docker Compose, the UI can be incomplete if the `superset_node` container hasn't finished building assets—wait for Webpack to hit 100% and check for errors in that container. Incomplete or failed builds are a frequent cause of missing menu items and blank screens ([source](https://github.com/apache/superset/issues/11171), [source](https://github.com/apache/superset/issues/25144)). - Check the browser console for frontend errors or warnings when opening the Settings menu. Asset or JS errors can prevent UI elements from rendering. - Review the Superset server logs for errors or warnings about permissions, menu rendering, or asset loading. - Run `superset init` and `superset db upgrade` in the container to resync roles and permissions after any config or version changes ([source](https://github.com/apache/superset/discussions/34044), [source](https://github.com/apache/superset/issues/34467)). - If you use a non-default metadata backend (like MySQL/MariaDB), make sure the required driver (e.g., `mysqlclient`) is installed in your Docker image. Missing drivers can cause incomplete migrations and permission sync issues ([source](https://github.com/apache/superset/issues/33672)). - Check for permission naming inconsistencies in your metadata DB (e.g., in the `ab_view_menu` table). Typos or casing mismatches can break menu visibility for admin users ([source](https://github.com/apache/superset/issues/33672)). - If you recently changed authentication types (e.g., switched to LDAP), reinitialize roles and permissions with `superset init` ([source](https://github.com/apache/superset/discussions/32427)). - If all else fails, stop Superset, remove Docker volumes (`docker compose down -v`), and start fresh to rule out persistent state or migration issues ([source](https://github.com/apache/superset/issues/34467)). Let me know if you see any errors in the browser console or logs, or if you need help checking the DB for permission inconsistencies. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/5510e082-c786-48a3-984f-a302bac33662?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/5510e082-c786-48a3-984f-a302bac33662?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/5510e082-c786-48a3-984f-a302bac33662?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/5510e082-c786-48a3-984f-a302bac33662?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/5510e082-c786-48a3-984f-a302bac33662?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/5510e082-c786-48a3-984f-a302bac33662?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/5510e082-c786-48a3-984f-a302bac33662?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github)& nbsp;[](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/discussions/35099) GitHub link: https://github.com/apache/superset/discussions/35099#discussioncomment-14369162 ---- This is an automatically sent email for notifications@superset.apache.org. To unsubscribe, please send an email to: notifications-unsubscr...@superset.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For additional commands, e-mail: notifications-h...@superset.apache.org
