Originally created by @bazzz1512 on GitHub (Oct 6, 2025).
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
Have a minikube installation present on Ubuntu 24.04
Install open-webui chart version 8.9.0
Set the extraEnvVars in the values.yaml file with for example (persistent config is false):
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).
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 @bazzz1512 on GitHub (Oct 6, 2025).
### 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 2025-11-11 17:00:40 -06:00
and please search for duplicate issues this is now the third duplicate
@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
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!
@bazzz1512 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!
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 @bazzz1512 on GitHub (Oct 6, 2025).
Check Existing Issues
Installation Method
Other
Open WebUI Version
v0.6.32
Ollama Version (if applicable)
Operating System
Ubuntu 24.04
Browser (if applicable)
No response
Confirmation
README.md.Expected Behavior
The expected behavior is that the Default User permission view in the webapp aligns with the environment variables passed in the
values.yamlfile. 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 Permissionsview stay constant, regardless of the corresponding environment variable value.Steps to Reproduce
extraEnvVarsin thevalues.yamlfile with for example (persistent config is false):Default permissions (applies to all users with the "user role"view and see that the boxes have not been updatedLogs & 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).

Furthermore, no browser logs are of interest that point to this issue.
Additional Information
No response
@Classic298 commented on GitHub (Oct 6, 2025):
please check the
devbranch should be fixed thereand please search for duplicate issues this is now the third duplicate
@bazzz1512 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!