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

[GH-ISSUE #22904] issue: Read/Write permission toggle not clickable for base models in Admin Panel #19838

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

Originally created by @Lyhtande on GitHub (Mar 20, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/22904

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.10

Ollama Version (if applicable)

No response

Operating System

Ubuntu 22.04.5 LTS

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

When editing a base model (e.g. gpt-4.1-mini) in the Admin Panel > Settings > Models, the access control dialog should allow toggling between READ and WRITE permissions for assigned groups and users — the same way it works for Knowledge Bases.

Actual Behavior

The access control dialog for base models in the Admin Panel only shows a READ badge next to assigned groups and users. The badge is not clickable and cannot be toggled to WRITE.

This only affects base models managed in the Admin Panel — not custom workspace models.

The fact that the badge explicitly says "READ" (rather than just showing access: yes/no) strongly suggests a WRITE option should exist but is currently non-functional.

Steps to Reproduce

  1. Log in as admin.
  2. Navigate to Admin Panel > Settings > Models.
  3. Click on any base model (e.g. gpt-4.1-mini).
  4. Set visibility to Private.
  5. Click on the access control / permissions area.
  6. Add a group or user.
  7. Observe that the permission badge shows READ and is not clickable/toggleable to WRITE.

For comparison:

  • Open Workspace > Knowledge, edit a knowledge base, and add a group — the READ badge is clickable and toggles to WRITE as expected.

Logs & Screenshots

Image

Additional Information

Related Issues

  • #8847 — Discussion from 2025 where users reported the same behavior. It was reportedly fixed, but the issue appears to have resurfaced.
  • #19461 — Regression in v0.6.38 where models shared with write permission were no longer visible in workspace (closed/fixed, but potentially related).
Originally created by @Lyhtande on GitHub (Mar 20, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/22904 ### 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.10 ### Ollama Version (if applicable) _No response_ ### Operating System Ubuntu 22.04.5 LTS ### 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 When editing a **base model** (e.g. `gpt-4.1-mini`) in the **Admin Panel > Settings > Models**, the access control dialog should allow toggling between **READ** and **WRITE** permissions for assigned groups and users — the same way it works for Knowledge Bases. ### Actual Behavior The access control dialog for base models in the Admin Panel only shows a **READ** badge next to assigned groups and users. The badge is **not clickable** and cannot be toggled to WRITE. This only affects base models managed in the Admin Panel — **not** custom workspace models. The fact that the badge explicitly says "READ" (rather than just showing access: yes/no) strongly suggests a WRITE option should exist but is currently non-functional. ### Steps to Reproduce 1. Log in as admin. 2. Navigate to **Admin Panel > Settings > Models**. 3. Click on any base model (e.g. `gpt-4.1-mini`). 4. Set visibility to **Private**. 5. Click on the access control / permissions area. 6. Add a group or user. 7. Observe that the permission badge shows **READ** and is not clickable/toggleable to **WRITE**. For comparison: - Open **Workspace > Knowledge**, edit a knowledge base, and add a group — the READ badge **is** clickable and toggles to WRITE as expected. ### Logs & Screenshots <img width="965" height="500" alt="Image" src="https://github.com/user-attachments/assets/0f0b1002-ded9-4654-9fab-1d3cec62164c" /> ### Additional Information ### Related Issues - #8847 — Discussion from 2025 where users reported the same behavior. It was reportedly fixed, but the issue appears to have resurfaced. - #19461 — Regression in v0.6.38 where models shared with write permission were no longer visible in workspace (closed/fixed, but potentially related).
GiteaMirror added the bug label 2026-04-20 02:20:46 -05:00
GiteaMirror commented 2026-04-20 02:20:48 -05:00
Author
Owner
Copy Link

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

No it should not be togglable, so the current behaviour is correct and intended

Why?
Because "Write" has no use here.

Giving a user write access is pointless.
It doesn't do anything.
The user cant go to the admin panel and edit the model, so the write access is pointless.

And admins always have write access to all models anyways

So the access control here is limited to no permission or read permission.

In workspace, users can go to workspace and edit models. So THERE, the write permission is possible.

<!-- gh-comment-id:4099819783 --> @Classic298 commented on GitHub (Mar 20, 2026): No it should not be togglable, so the current behaviour is correct and intended Why? Because "Write" has no use here. Giving a user write access is pointless. It doesn't do anything. The user cant go to the admin panel and edit the model, so the write access is pointless. And admins always have write access to all models anyways So the access control here is limited to no permission or read permission. --- In workspace, users can go to workspace and edit models. So THERE, the write permission is possible.
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#19838
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?