I have searched for all existing open AND closed issues and discussions for similar requests. I have found none that is comparable to my request.
Verify Feature Scope
I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions.
Problem Description
We are currently adapting open webui for a customer to meet their business criteria and design guidelines (yes, they have an enterprise license). We identified some features that are not needed for the customer and where therefore disabled/deleted in the codebase.
Splash screen
User menu in sidebar
Notes feature
Temporary chat feature
Desired Solution you'd like
It would be great if these features could be disabled by using configuration parameters. Would you be willing to accept a PR with these changes guarded by feature flags / environment variables?
Alternatives Considered
No response
Additional Context
No response
Originally created by @domachine on GitHub (Feb 6, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/21206
### Check Existing Issues
- [x] I have searched for all existing **open AND closed** issues and discussions for similar requests. I have found none that is comparable to my request.
### Verify Feature Scope
- [x] I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions.
### Problem Description
We are currently adapting open webui for a customer to meet their business criteria and design guidelines (yes, they have an enterprise license). We identified some features that are not needed for the customer and where therefore disabled/deleted in the codebase.
- Splash screen
- User menu in sidebar
- Notes feature
- Temporary chat feature
### Desired Solution you'd like
It would be great if these features could be disabled by using configuration parameters. Would you be willing to accept a PR with these changes guarded by feature flags / environment variables?
### Alternatives Considered
_No response_
### Additional Context
_No response_
FYI you can already disable Notes via "General" settings as well as permissions and temporary chat via permissions.
<!-- gh-comment-id:3859139950 -->
@Ithanil commented on GitHub (Feb 6, 2026):
FYI you can already disable Notes via "General" settings as well as permissions and temporary chat via permissions.
You can just... disable Notes, temporary chats and some parts of the user menu.
Splash screen? You mean the loading-splash screen is .. not wanted?
And since you (implying a consultant) are helping a customer (with an enterprise license as you said - which comes with support) with this - maybe you should read the docs and find out how to disable Notes and temporary chats there. It is all in the docs.
We have the discord server with a very helpful AI bot which knows the entire docs AND all issues and all discussions and knows even more than what is in the docs
We have the discussions
Why would you open an ISSUE to ask a question? Discussions are for Q&A
I have searched for all existing open AND closed issues and discussions for similar requests. I have found none that is comparable to my request.
You even ticked this requirement but clearly you did not use the search
I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions.
And you also agreed to this, which clearly states during the issue-opening-form that the issues are ONLY for trivial feature requests or actual issues aka bugs.
<!-- gh-comment-id:3859521159 -->
@Classic298 commented on GitHub (Feb 6, 2026):
You can just... disable Notes, temporary chats and some parts of the user menu.
Splash screen? You mean the loading-splash screen is .. not wanted?
And since you (implying a consultant) are helping a customer (with an enterprise license as you said - which comes with support) with this - maybe you should read the docs and find out how to disable Notes and temporary chats there. It is all in the docs.
- We have the docs [Notes](https://docs.openwebui.com/features/notes) [More Notes](https://docs.openwebui.com/getting-started/env-configuration#enable_notes) [And more notes](https://docs.openwebui.com/getting-started/env-configuration#user_permissions_features_notes) [And more notes](https://docs.openwebui.com/getting-started/env-configuration#user_permissions_notes_allow_public_sharing) [And temporary chat](https://docs.openwebui.com/getting-started/env-configuration#user_permissions_chat_temporary)
- We have the discord server with a very helpful AI bot which knows the entire docs AND all issues and all discussions and knows even more than what is in the docs
- We have the discussions
Why would you open an ISSUE to ask a question? Discussions are for Q&A
> I have searched for all existing open AND closed issues and discussions for similar requests. I have found none that is comparable to my request.
You even ticked this requirement but clearly you did not use the search
> I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions.
And you also agreed to this, which clearly states during the issue-opening-form that the issues are ONLY for trivial feature requests or actual issues aka bugs.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @domachine on GitHub (Feb 6, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/21206
Check Existing Issues
Verify Feature Scope
Problem Description
We are currently adapting open webui for a customer to meet their business criteria and design guidelines (yes, they have an enterprise license). We identified some features that are not needed for the customer and where therefore disabled/deleted in the codebase.
Desired Solution you'd like
It would be great if these features could be disabled by using configuration parameters. Would you be willing to accept a PR with these changes guarded by feature flags / environment variables?
Alternatives Considered
No response
Additional Context
No response
@Ithanil commented on GitHub (Feb 6, 2026):
FYI you can already disable Notes via "General" settings as well as permissions and temporary chat via permissions.
@Classic298 commented on GitHub (Feb 6, 2026):
You can just... disable Notes, temporary chats and some parts of the user menu.
Splash screen? You mean the loading-splash screen is .. not wanted?
And since you (implying a consultant) are helping a customer (with an enterprise license as you said - which comes with support) with this - maybe you should read the docs and find out how to disable Notes and temporary chats there. It is all in the docs.
Why would you open an ISSUE to ask a question? Discussions are for Q&A
You even ticked this requirement but clearly you did not use the search
And you also agreed to this, which clearly states during the issue-opening-form that the issues are ONLY for trivial feature requests or actual issues aka bugs.