You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "dosubot[bot] (via GitHub)" <gi...@apache.org> on 2026/05/02 03:19:30 UTC
Re: [D] which version is work both with SUPERSET_APP_ROOT and Security menu [superset]
GitHub user dosubot[bot] edited a comment on the discussion: which version is work both with SUPERSET_APP_ROOT and Security menu
<!-- Answer -->
I found two similar discussions that might be relevant to your issue:
1. [SUPERSET_APP_ROOT in pypi deployment](https://github.com/apache/superset/discussions/33391) - This thread is open and discusses issues with `SUPERSET_APP_ROOT` in deployment scenarios <sup>[[1]](https://github.com/apache/superset/discussions/33391)</sup>.
2. [superset_app_root doesn't work in superset 4.1.2 with nginx](https://github.com/apache/superset/discussions/33229) - This thread is open and specifically addresses problems with `SUPERSET_APP_ROOT` in version 4.1.2 when using nginx <sup>[[2]](https://github.com/apache/superset/discussions/33229)</sup>.
Regarding your question, the `SUPERSET_APP_ROOT` functionality allows the application to run under a non-root path, but it is currently in BETA. This might explain the inconsistencies you're experiencing across different versions <sup>[[3]](https://github.com/apache/superset/blob/master/docs/docs/configuration/configuring-superset.mdx)</sup><sup>[[4]](https://github.com/apache/superset/blob/master/superset/app.py)</sup>. The Security menu is restricted to admin users only, as defined in the `ADMIN_ONLY_VIEW_MENUS` set within the `superset/security/manager.py` file <sup>[[5]](https://github.com/apache/superset/blob/master/superset/security/manager.py)</sup>.
It seems that the issues you're facing might be related to the specific configurations or the BETA status of the `SUPERSET_APP_ROOT` feature. You might want to check the configuration settings and ensure they are correctly set for both functionalities. Additionally, waiting for the official release of version 5.0.0 could potentially resolve these issues, as it might include fixes or improvements for these features.
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=reply-with-mention&utm_term=apache%2Fsuperset).*
---
Docs are dead. Just use [Dosu](https://dosu.dev?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-tagline&utm_term=apache%2Fsuperset).
[](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-feedback&utm_term=apache%2Fsuperset&message_id=dfb7f9f5-83a7-4fa3-bb48-026c2178aaf5) [](https://github.dosu.com/apache/superset?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-ask-repo&utm_term=apache%2Fsuperset) [](https://app.dosu.dev/signup?referrer=openSource&source=github-footer&utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-share-team&utm_term=apache%2Fsuperset)
GitHub link: https://github.com/apache/superset/discussions/33414#discussioncomment-13125437
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org