github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-06-03 23:38:13 -05:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

[GH-ISSUE #21655] issue: Chat Controls sub-settings doesn't apply #19548

New Issue
Closed
opened 2026-04-20 02:01:04 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-20 02:01:04 -05:00
Owner
Copy Link

Originally created by @gabriel-lopez on GitHub (Feb 20, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/21655

Check Existing Issues

  • I have searched for any existing and/or related issues.
  • I have searched for any existing and/or related discussions.
  • I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!).
  • I am using the latest version of Open WebUI.

Installation Method

Docker

Open WebUI Version

v0.8.3

Ollama Version (if applicable)

No response

Operating System

macOS

Browser (if applicable)

Chrome

Confirmation

  • I have read and followed all instructions in README.md.
  • I am using the latest version of both Open WebUI and Ollama.
  • I have included the browser console logs.
  • I have included the Docker container logs.
  • I have provided every relevant configuration, setting, and environment variable used in my setup.
  • I have clearly listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
  • I have documented step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation. My steps:
  • Start with the initial platform/version/OS and dependencies used,
  • Specify exact install/launch/configure commands,
  • List URLs visited, user input (incl. example values/emails/passwords if needed),
  • Describe all options and toggles enabled or changed,
  • Include any files or environmental changes,
  • Identify the expected and actual result at each stage,
  • Ensure any reasonably skilled user can follow and hit the same issue.

Expected Behavior

With settings:
Allow Chat Controls -> ON
Allow Chat Valves -> OFF
Allow Chat System Prompt -> ON
Allow Chat Params -> OFF
I expect to be able to only set a chat system prompt under chat controls.

Actual Behavior

Chat Valves and Chat Params still displayed and available to edit to every user. Only Allow Chat Controls set to Off works to make disappear chat params

Steps to Reproduce

Set in default use permission:
Allow Chat Controls -> ON
Allow Chat Valves -> OFF
Allow Chat System Prompt -> ON
Allow Chat Params -> OFF

Access any Chat Control and try to edit settings

Logs & Screenshots

Image Image

Additional Information

I have no group that overrides those settings.

Originally created by @gabriel-lopez on GitHub (Feb 20, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/21655 ### Check Existing Issues - [x] I have searched for any existing and/or related issues. - [x] I have searched for any existing and/or related discussions. - [x] I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!). - [x] I am using the latest version of Open WebUI. ### Installation Method Docker ### Open WebUI Version v0.8.3 ### Ollama Version (if applicable) _No response_ ### Operating System macOS ### Browser (if applicable) Chrome ### Confirmation - [x] I have read and followed all instructions in `README.md`. - [x] I am using the latest version of **both** Open WebUI and Ollama. - [x] I have included the browser console logs. - [x] I have included the Docker container logs. - [x] I have **provided every relevant configuration, setting, and environment variable used in my setup.** - [x] I have clearly **listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup** (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc). - [x] I have documented **step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation**. My steps: - Start with the initial platform/version/OS and dependencies used, - Specify exact install/launch/configure commands, - List URLs visited, user input (incl. example values/emails/passwords if needed), - Describe all options and toggles enabled or changed, - Include any files or environmental changes, - Identify the expected and actual result at each stage, - Ensure any reasonably skilled user can follow and hit the same issue. ### Expected Behavior With settings: Allow Chat Controls -> ON Allow Chat Valves -> OFF Allow Chat System Prompt -> ON Allow Chat Params -> OFF I expect to be able to only set a chat system prompt under chat controls. ### Actual Behavior Chat Valves and Chat Params still displayed and available to edit to every user. Only Allow Chat Controls set to Off works to make disappear chat params ### Steps to Reproduce Set in default use permission: Allow Chat Controls -> ON Allow Chat Valves -> OFF Allow Chat System Prompt -> ON Allow Chat Params -> OFF Access any Chat Control and try to edit settings ### Logs & Screenshots <img width="871" height="528" alt="Image" src="https://github.com/user-attachments/assets/34ef4a16-cd56-4ad5-a967-aadcff1de871" /> <img width="473" height="397" alt="Image" src="https://github.com/user-attachments/assets/5d2ba15a-cce6-46f6-b0f1-2c1f2519045d" /> ### Additional Information I have no group that overrides those settings.
GiteaMirror added the bug label 2026-04-20 02:01:04 -05:00
GiteaMirror commented 2026-04-20 02:01:06 -05:00
Author
Owner
Copy Link

@Classic298 commented on GitHub (Feb 20, 2026):

are you testing this as an admin? the chat control permissions specifically dont apply to admins.

and if you are testing with a user - is the user in a group where these permissions are granted?

<!-- gh-comment-id:3937049438 --> @Classic298 commented on GitHub (Feb 20, 2026): are you testing this as an admin? the chat control permissions specifically dont apply to admins. and if you are testing with a user - is the user in a group where these permissions are granted?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#19548
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?