github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-07 03:18:23 -05:00
Code Issues 1.3k Packages Projects Releases 126 Wiki Activity

[GH-ISSUE #18076] issue: Standard user permissions not propogated to UI from env vars #18484

New Issue
Closed
opened 2026-04-20 00:43:11 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-20 00:43:11 -05:00
Owner
Copy Link

Originally created by @sspeekenbrink on GitHub (Oct 6, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/18076

Check Existing Issues

  • I have searched for any existing and/or related issues.
  • I have searched for any existing and/or related discussions.
  • I am using the latest version of Open WebUI.

Installation Method

Other

Open WebUI Version

v0.6.32

Ollama Version (if applicable)

Operating System

Ubuntu 24.04

Browser (if applicable)

No response

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

The expected behavior is that the Default User permission view in the webapp aligns with the environment variables passed in the values.yaml file. The permissions are however disabled for the corresponding users in the back-end, so it's just the front-end view.

Actual Behavior

The values in the Edit Default Permissions view stay constant, regardless of the corresponding environment variable value.

Steps to Reproduce

  1. Have a minikube installation present on Ubuntu 24.04
  2. Install open-webui chart version 8.9.0
  3. Set the extraEnvVars in the values.yaml file with for example (persistent config is false):
    - name: ENABLE_PERSISTENT_CONFIG
      value: "False"
    - name: USER_PERMISSIONS_CHAT_CONTROLS
      value: "False"
    - name: USER_PERMISSIONS_CHAT_VALVES
      value: "False"
    - name: USER_PERMISSIONS_CHAT_SYSTEM_PROMPT
      value: "False"
    - name: USER_PERMISSIONS_CHAT_PARAMS
      value: "False"
    - name: USER_PERMISSIONS_CHAT_STT
      value: "False"
    - name: USER_PERMISSIONS_CHAT_TTS
      value: "False"
    - name: USER_PERMISSIONS_CHAT_CALL
      value: "False"
    - name: USER_PERMISSIONS_CHAT_MULTIPLE_MODELS
      value: "False"
    - name: USER_PERMISSIONS_FEATURES_WEB_SEARCH
      value: "False"
    - name: USER_PERMISSIONS_FEATURES_IMAGE_GENERATION
      value: "False"
    - name: USER_PERMISSIONS_FEATURES_CODE_INTERPRETER
      value: "False"
    - name: USER_PERMISSIONS_CHAT_EXPORT
      value: "False"
    - name: USER_PERMISSIONS_FEATURES_NOTES
      value: "False"
  1. Upgrade the helm chart
  2. See Default permissions (applies to all users with the "user role" view and see that the boxes have not been updated

Logs & Screenshots

In the image, the values can be seen enabled, even though they're disabled in the back-end (tested with a regular user as well).
Image

Defaulted container "open-webui" out of: open-webui, copy-app-data (init)
INFO  [alembic.runtime.migration] Context impl PostgresqlImpl.
INFO  [alembic.runtime.migration] Will assume transactional DDL.
WARNI [open_webui.env] 

WARNING: CORS_ALLOW_ORIGIN IS SET TO '*' - NOT RECOMMENDED FOR PRODUCTION DEPLOYMENTS.

INFO  [open_webui.env] VECTOR_DB: chroma
INFO  [open_webui.env] Embedding model set: sentence-transformers/all-MiniLM-L6-v2
WARNI [langchain_community.utils.user_agent] USER_AGENT environment variable not set, consider setting it to identify your requests.

 ██████╗ ██████╗ ███████╗███╗   ██╗    ██╗    ██╗███████╗██████╗ ██╗   ██╗██╗
██╔═══██╗██╔══██╗██╔════╝████╗  ██║    ██║    ██║██╔════╝██╔══██╗██║   ██║██║
██║   ██║██████╔╝█████╗  ██╔██╗ ██║    ██║ █╗ ██║█████╗  ██████╔╝██║   ██║██║
██║   ██║██╔═══╝ ██╔══╝  ██║╚██╗██║    ██║███╗██║██╔══╝  ██╔══██╗██║   ██║██║
╚██████╔╝██║     ███████╗██║ ╚████║    ╚███╔███╔╝███████╗██████╔╝╚██████╔╝██║
 ╚═════╝ ╚═╝     ╚══════╝╚═╝  ╚═══╝     ╚══╝╚══╝ ╚══════╝╚═════╝  ╚═════╝ ╚═╝


v0.6.32 - building the best AI user interface.

https://github.com/open-webui/open-webui

Fetching 30 files: 100% 30/30 [00:00<00:00, 304670.99it/s]
INFO:     Started server process [1]
INFO:     Waiting for application startup.

Furthermore, no browser logs are of interest that point to this issue.

Additional Information

No response

Originally created by @sspeekenbrink on GitHub (Oct 6, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/18076 ### 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 am using the latest version of Open WebUI. ### Installation Method Other ### Open WebUI Version v0.6.32 ### Ollama Version (if applicable) - ### Operating System Ubuntu 24.04 ### Browser (if applicable) _No response_ ### 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 The expected behavior is that the Default User permission view in the webapp aligns with the environment variables passed in the `values.yaml` file. The permissions are however disabled for the corresponding users in the back-end, so it's just the front-end view. ### Actual Behavior The values in the `Edit Default Permissions` view stay constant, regardless of the corresponding environment variable value. ### Steps to Reproduce 1. Have a minikube installation present on Ubuntu 24.04 2. Install open-webui chart version 8.9.0 3. Set the `extraEnvVars` in the `values.yaml` file with for example (persistent config is false): ``` - name: ENABLE_PERSISTENT_CONFIG value: "False" - name: USER_PERMISSIONS_CHAT_CONTROLS value: "False" - name: USER_PERMISSIONS_CHAT_VALVES value: "False" - name: USER_PERMISSIONS_CHAT_SYSTEM_PROMPT value: "False" - name: USER_PERMISSIONS_CHAT_PARAMS value: "False" - name: USER_PERMISSIONS_CHAT_STT value: "False" - name: USER_PERMISSIONS_CHAT_TTS value: "False" - name: USER_PERMISSIONS_CHAT_CALL value: "False" - name: USER_PERMISSIONS_CHAT_MULTIPLE_MODELS value: "False" - name: USER_PERMISSIONS_FEATURES_WEB_SEARCH value: "False" - name: USER_PERMISSIONS_FEATURES_IMAGE_GENERATION value: "False" - name: USER_PERMISSIONS_FEATURES_CODE_INTERPRETER value: "False" - name: USER_PERMISSIONS_CHAT_EXPORT value: "False" - name: USER_PERMISSIONS_FEATURES_NOTES value: "False" ``` 4. Upgrade the helm chart 5. See `Default permissions (applies to all users with the "user role"` view and see that the boxes have not been updated ### Logs & Screenshots In the image, the values can be seen enabled, even though they're disabled in the back-end (tested with a regular user as well). <img width="848" height="606" alt="Image" src="https://github.com/user-attachments/assets/6984c715-2b71-496d-bb15-defb33f941e8" /> ``` Defaulted container "open-webui" out of: open-webui, copy-app-data (init) INFO [alembic.runtime.migration] Context impl PostgresqlImpl. INFO [alembic.runtime.migration] Will assume transactional DDL. WARNI [open_webui.env] WARNING: CORS_ALLOW_ORIGIN IS SET TO '*' - NOT RECOMMENDED FOR PRODUCTION DEPLOYMENTS. INFO [open_webui.env] VECTOR_DB: chroma INFO [open_webui.env] Embedding model set: sentence-transformers/all-MiniLM-L6-v2 WARNI [langchain_community.utils.user_agent] USER_AGENT environment variable not set, consider setting it to identify your requests. ██████╗ ██████╗ ███████╗███╗ ██╗ ██╗ ██╗███████╗██████╗ ██╗ ██╗██╗ ██╔═══██╗██╔══██╗██╔════╝████╗ ██║ ██║ ██║██╔════╝██╔══██╗██║ ██║██║ ██║ ██║██████╔╝█████╗ ██╔██╗ ██║ ██║ █╗ ██║█████╗ ██████╔╝██║ ██║██║ ██║ ██║██╔═══╝ ██╔══╝ ██║╚██╗██║ ██║███╗██║██╔══╝ ██╔══██╗██║ ██║██║ ╚██████╔╝██║ ███████╗██║ ╚████║ ╚███╔███╔╝███████╗██████╔╝╚██████╔╝██║ ╚═════╝ ╚═╝ ╚══════╝╚═╝ ╚═══╝ ╚══╝╚══╝ ╚══════╝╚═════╝ ╚═════╝ ╚═╝ v0.6.32 - building the best AI user interface. https://github.com/open-webui/open-webui Fetching 30 files: 100% 30/30 [00:00<00:00, 304670.99it/s] INFO: Started server process [1] INFO: Waiting for application startup. ``` Furthermore, no browser logs are of interest that point to this issue. ### Additional Information _No response_
GiteaMirror added the bug label 2026-04-20 00:43:11 -05:00
GiteaMirror commented 2026-04-20 00:43:13 -05:00
Author
Owner
Copy Link

@Classic298 commented on GitHub (Oct 6, 2025):

please check the dev branch should be fixed there

and please search for duplicate issues this is now the third duplicate

<!-- gh-comment-id:3370685577 --> @Classic298 commented on GitHub (Oct 6, 2025): please check the `dev` branch should be fixed there and please search for duplicate issues this is now the third duplicate
GiteaMirror commented 2026-04-20 00:43:13 -05:00
Author
Owner
Copy Link

@sspeekenbrink commented on GitHub (Oct 6, 2025):

Apologies, I checked the open issues as I assumed this wasn't fixed yet and didn't see it happening there. Thanks for the quick reply!

<!-- gh-comment-id:3370736822 --> @sspeekenbrink commented on GitHub (Oct 6, 2025): Apologies, I checked the open issues as I assumed this wasn't fixed yet and didn't see it happening there. Thanks for the quick reply!
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#18484
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?