I have searched the existing issues and discussions.
Problem Description
We found that many new users are overwhelmed by some complex options and features, like e.g. workspace tools and chat control menu. In any case you need to explain and document all these features, which is overwhelming for deployers.
The only currently available solution is to deactivate all these features for everyone, which doesn't satisfy the "power users".
Desired Solution you'd like
Allow the user to enable "expert mode", which then enables chat control and all the workspace features he is allowed to use. Make it configurable for the admin what the default is and thus avoid breaking the behavior of existing installations.
Maybe the feature could somehow inherit from the group feature, but it is important that the user can toggle this without administrative intervention. (see 2) below)
Alternatives Considered
Deactivate all these features for everyone, which doesn't satisfy the "power users".
Make an expert group with specific permissions. This approach doesn't scale for large deployments. (and currently doesn't hide the chat control menu button).
Originally created by @Ithanil on GitHub (Apr 2, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/12345
### Check Existing Issues
- [x] I have searched the existing issues and discussions.
### Problem Description
We found that many new users are overwhelmed by some complex options and features, like e.g. workspace tools and chat control menu. In any case you need to explain and document all these features, which is overwhelming for deployers.
The only currently available solution is to deactivate all these features for everyone, which doesn't satisfy the "power users".
### Desired Solution you'd like
Allow the user to enable "expert mode", which then enables chat control and all the workspace features he is allowed to use. Make it configurable for the admin what the default is and thus avoid breaking the behavior of existing installations.
Maybe the feature could somehow inherit from the group feature, but it is important that the user can toggle this without administrative intervention. (see 2) below)
### Alternatives Considered
1) Deactivate all these features for everyone, which doesn't satisfy the "power users".
2) Make an expert group with specific permissions. This approach doesn't scale for large deployments. (and currently doesn't hide the chat control menu button).
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 @Ithanil on GitHub (Apr 2, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/12345
Check Existing Issues
Problem Description
We found that many new users are overwhelmed by some complex options and features, like e.g. workspace tools and chat control menu. In any case you need to explain and document all these features, which is overwhelming for deployers.
The only currently available solution is to deactivate all these features for everyone, which doesn't satisfy the "power users".
Desired Solution you'd like
Allow the user to enable "expert mode", which then enables chat control and all the workspace features he is allowed to use. Make it configurable for the admin what the default is and thus avoid breaking the behavior of existing installations.
Maybe the feature could somehow inherit from the group feature, but it is important that the user can toggle this without administrative intervention. (see 2) below)
Alternatives Considered