issue: USER_PERMISSIONS_CHAT_CONTROLS not being honored #6103

Closed
opened 2025-11-11 16:45:00 -06:00 by GiteaMirror · 2 comments
Owner

Originally created by @y4shg on GitHub (Aug 15, 2025).

Check Existing Issues

  • I have searched the existing issues and discussions.
  • I am using the latest version of Open WebUI.

Installation Method

Docker

Open WebUI Version

v0.6.22

Ollama Version (if applicable)

v0.11.4

Operating System

Ubuntu 24.04

Browser (if applicable)

Chrome 139.0.7258.127/128

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

USER_PERMISSIONS_CHAT_CONTROLS when set to false is to hide/disable the viewing of system prompt and other chat controls.

Actual Behavior

USER_PERMISSIONS_CHAT_CONTROLS is set to False, but Standard User is still able to open settings and change system prompt.

Steps to Reproduce

  1. Start with clean Ubuntu 24.04 Install
  2. Install docker via docker documentation
  3. Start Docker
  4. Start ollama in docker
  5. clone openwebui to home directory
  6. add to docker compose, USER_PERMISSIONS_CHAT_CONTROLS and set to False
  7. enable signups for open-webui
  8. use default env config variables
  9. run docker compose file after edits.
  10. open chrome browser in incognito
  11. go to http://localhost:8080/ and login/create with admin vovxb@vovxb.com
  12. go to admin Panel > users > create new user
  13. create new user with name vovxb@gmail.com in SIGN UP not in admin panel
  14. go to users > Edit Default Permissions, then set all toggles to off.
  15. save
  16. approve pending user
  17. open new incognito window separately
  18. log in with user vovxb@gmail.com
  19. click profile in bottom left corner
  20. click settings
  21. change system prompt to say "you are a helpful assistant. User name is john Bob"
  22. click save
  23. type to chatbot
  24. "hello, what's my name?"
  25. chatbot responds "Hello, your name is John Bob"### Logs & Screenshots
2025-08-15 05:19:51.803 | INFO     | uvicorn.protocols.http.httptools_impl:send:476 - 97.70.83.24:0 - "GET /_app/version.json HTTP/1.1" 200
2025-08-15 05:19:55.433 | INFO     | uvicorn.protocols.http.httptools_impl:send:476 - 97.70.83.24:0 - "GET /static/favicon.png HTTP/1.1" 304
2025-08-15 05:19:55.451 | INFO     | uvicorn.protocols.http.httptools_impl:send:476 - 97.70.83.24:0 - "GET /ollama/api/version HTTP/1.1" 200
2025-08-15 05:19:55.452 | INFO     | uvicorn.protocols.http.httptools_impl:send:476 - 97.70.83.24:0 - "GET /static/favicon.png HTTP/1.1" 200
2025-08-15 05:19:55.472 | INFO     | uvicorn.protocols.http.httptools_impl:send:476 - 97.70.83.24:0 - "GET /api/v1/users/user/settings HTTP/1.1" 200

Additional Information

have tried on multiple computers, same result. no errors or warnings or anything related pop up in Logs for openwebui

Originally created by @y4shg on GitHub (Aug 15, 2025). ### Check Existing Issues - [x] I have searched the existing issues and discussions. - [x] I am using the latest version of Open WebUI. ### Installation Method Docker ### Open WebUI Version v0.6.22 ### Ollama Version (if applicable) v0.11.4 ### Operating System Ubuntu 24.04 ### Browser (if applicable) Chrome 139.0.7258.127/128 ### 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 USER_PERMISSIONS_CHAT_CONTROLS when set to false is to hide/disable the viewing of system prompt and other chat controls. ### Actual Behavior USER_PERMISSIONS_CHAT_CONTROLS is set to False, but Standard User is still able to open settings and change system prompt. ### Steps to Reproduce 1. Start with clean Ubuntu 24.04 Install 2. Install docker via docker documentation 3. Start Docker 4. Start ollama in docker 5. clone openwebui to home directory 6. add to docker compose, USER_PERMISSIONS_CHAT_CONTROLS and set to False 7. enable signups for open-webui 8. use default env config variables 9. run docker compose file after edits. 10. open chrome browser in incognito 11. go to http://localhost:8080/ and login/create with admin vovxb@vovxb.com 12. go to admin Panel > users > create new user 13. create new user with name vovxb@gmail.com in SIGN UP not in admin panel 14. go to users > Edit Default Permissions, then set all toggles to off. 15. save 16. approve pending user 17. open new incognito window separately 18. log in with user vovxb@gmail.com 19. click profile in bottom left corner 20. click settings 21. change system prompt to say "you are a helpful assistant. User name is john Bob" 22. click save 23. type to chatbot 24. "hello, what's my name?" 25. chatbot responds "Hello, your name is John Bob"### Logs & Screenshots ``` 2025-08-15 05:19:51.803 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 97.70.83.24:0 - "GET /_app/version.json HTTP/1.1" 200 2025-08-15 05:19:55.433 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 97.70.83.24:0 - "GET /static/favicon.png HTTP/1.1" 304 2025-08-15 05:19:55.451 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 97.70.83.24:0 - "GET /ollama/api/version HTTP/1.1" 200 2025-08-15 05:19:55.452 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 97.70.83.24:0 - "GET /static/favicon.png HTTP/1.1" 200 2025-08-15 05:19:55.472 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 97.70.83.24:0 - "GET /api/v1/users/user/settings HTTP/1.1" 200 ``` ### Additional Information have tried on multiple computers, same result. no errors or warnings or anything related pop up in Logs for openwebui
GiteaMirror added the bug label 2025-11-11 16:45:00 -06:00
Author
Owner

@y4shg commented on GitHub (Aug 15, 2025):

I have forgot to mention, This only happens if a user signs up through the sign up screen, waits in pending status, then gets approved. After that the user able to access system prompt. But if the admin directly adds the user through the admin panel such result does not happen and the user is unable to access system prompt.

@y4shg commented on GitHub (Aug 15, 2025): I have forgot to mention, This only happens if a user signs up through the sign up screen, waits in pending status, then gets approved. After that the user able to access system prompt. But if the admin directly adds the user through the admin panel such result does not happen and the user is unable to access system prompt.
Author
Owner

@tjbck commented on GitHub (Aug 17, 2025):

Unable to reproduce, keep us updated.

@tjbck commented on GitHub (Aug 17, 2025): Unable to reproduce, keep us updated.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#6103