mirror of
https://github.com/open-webui/open-webui.git
synced 2026-07-16 06:03:26 -05:00
[GH-ISSUE #8441] Add ability to disable access to Chat Controls for users #15127
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/open-webui#15127
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @bannert1337 on GitHub (Jan 9, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/8441
Originally assigned to: @tjbck on GitHub.
Is your feature request related to a problem? Please describe.
Currently, all users have access to Chat Controls, which may not be desirable in certain environments where administrators want to restrict access to these controls for specific users or roles.
Describe the solution you'd like
I would like to have a configuration option or permission setting that allows administrators to disable access to Chat Controls for specific users or roles. This could be implemented as a toggle in the user management settings or as a role-based permission.
Describe alternatives you've considered
An alternative could be to hide the Chat Controls UI elements for users who do not have the necessary permissions, but this might not be as effective as completely disabling access.
Additional context
This feature would be particularly useful in enterprise environments where different levels of access control are required for different users or roles.
@tjbck commented on GitHub (Jan 9, 2025):
Agreed, Great suggestion.
@dpk-it commented on GitHub (Jan 9, 2025):
Especially for the ability to pass a system prompt to a model using this interface
@codebath1387 commented on GitHub (Jan 12, 2025):
This would be very helpful to have available as a permission selectable through the admin panel's user permissions along with the ability to administered user access to the memory feature and their system prompt and chat controls in their user settings.
The existing admin configurable user permissions is a good start.
@tjbck commented on GitHub (Jan 16, 2025):
Added to dev!
@bannert1337 commented on GitHub (Jan 16, 2025):
Appreciated!
@Classic298 commented on GitHub (Feb 27, 2025):
Hey guys, this toggle has one issue:
It also disables to user-sided valves, which, as the name and intention of these valves suggest, are intentionally exposed to the user.
Furthermore, user-sided valves are unrelated to a single chat and instead get stored across sessions.
Valves are Tool and Filter specific, but by disabling the Allow Chat Controls, the Valves of Filters and Tools become inaccessible!
Allow Chat Controls should be, as the name clearly suggests, be related to Chat Controls, not Tool Controls or Filter Controls (Valve Controls).
Was this intended? Because, well, it doesn't make much sense since valves are not part of a chat control...
@Classic298 commented on GitHub (Mar 4, 2025):
bump
@Classic298 commented on GitHub (Apr 1, 2025):
Was fixed with 0.6.0! Thanks everyone
@mkagit commented on GitHub (Apr 28, 2025):
And how about an Admin that wants to hide the function/ tools valves from the users? Toggle chat controls won't hide it
@Classic298 commented on GitHub (Apr 28, 2025):
@mkagit Then do not use UserValves, instead only normal Valves, if the user is not intended to see the valves in the first place.