github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-07-16 23:21:44 -05:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

[GH-ISSUE #20124] issue: Private Knowledge Collection Multiple Access Rules Breaks Visibility #138820

New Issue
Closed
opened 2026-05-25 11:42:42 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-05-25 11:42:42 -05:00
Owner
Copy Link

Originally created by @brianhillnovus on GitHub (Dec 22, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/20124

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

Ollama Version (if applicable)

No response

Operating System

Ubuntu

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

After Knowledge Collection overhaul, users with Read-Only access to KC's should be able to view them in the Workspaces > Knowledge page.

Actual Behavior

If a KC has more than one access rule defined, users cannot see the KC, either from the Workpaces > Knowledge page, or when in chat pressing # to display a list of KC's to attach to the chat.

Steps to Reproduce

  1. Create 2 test groups.
  2. Create a test user and add them to the 2 test groups.
  3. Create a Private test Knowledge Collection.
  4. Configure the Access rules so that only one of the test groups can access it. Read or Write, doesn't matter.
  5. In a new browser session (private browser or different browser) login as the test user.
  6. Go to Workspaces > Knowledge. You should see the test KC.
  7. Modify the Access for the test KC and add the 2nd test group to it. Again, read or write, doesn't matter.
  8. In the other browser session refresh the Workspaces > Knowledge page, the KC you could see before disappears, even though the user has access to it through both test groups.
  9. Removing either of the test groups from the Access permissions restores visibility.

Any KC that has multiple Access groups defined becomes invisible to any user with the "User" role in both the Workspaces > Knowledge page, and in Chat when using # to find KC's to attach. Users with the "Admin" role can see all the KC's still.

Logs & Screenshots

I'm not sure what logs to attach as there are no errors being reported. This appears to be a mis-configuration of the permissions after the overhaul of the Knowledge system.

Additional Information

No response

Originally created by @brianhillnovus on GitHub (Dec 22, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/20124 ### 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.6.43 ### Ollama Version (if applicable) _No response_ ### Operating System Ubuntu ### 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 After Knowledge Collection overhaul, users with Read-Only access to KC's should be able to view them in the Workspaces > Knowledge page. ### Actual Behavior If a KC has more than one access rule defined, users cannot see the KC, either from the Workpaces > Knowledge page, or when in chat pressing # to display a list of KC's to attach to the chat. ### Steps to Reproduce 1. Create 2 test groups. 2. Create a test user and add them to the 2 test groups. 3. Create a Private test Knowledge Collection. 4. Configure the Access rules so that only one of the test groups can access it. Read or Write, doesn't matter. 5. In a new browser session (private browser or different browser) login as the test user. 6. Go to Workspaces > Knowledge. You should see the test KC. 7. Modify the Access for the test KC and add the 2nd test group to it. Again, read or write, doesn't matter. 8. In the other browser session refresh the Workspaces > Knowledge page, the KC you could see before disappears, even though the user has access to it through both test groups. 9. Removing either of the test groups from the Access permissions restores visibility. Any KC that has multiple Access groups defined becomes invisible to any user with the "User" role in both the Workspaces > Knowledge page, and in Chat when using # to find KC's to attach. Users with the "Admin" role can see all the KC's still. ### Logs & Screenshots I'm not sure what logs to attach as there are no errors being reported. This appears to be a mis-configuration of the permissions after the overhaul of the Knowledge system. ### Additional Information _No response_
GiteaMirror added the bug label 2026-05-25 11:42:42 -05:00
GiteaMirror commented 2026-05-25 11:42:46 -05:00
Author
Owner
Copy Link

@owui-terminator[bot] commented on GitHub (Dec 22, 2025):

🔍 Similar Issues Found

I found some existing issues that might be related to this one. Please check if any of these are duplicates or contain helpful solutions:

  1. #19752 issue: minor UI Bug: knowledge sharing
    by mahenning • Dec 04, 2025 • bug

  2. #20019 issue:
    by j63440490 • Dec 17, 2025 • bug

  3. #19864 issue:
    by Haervwe • Dec 10, 2025 • bug

  4. #20048 issue: Public custom model access broken
    by lochmaster • Dec 19, 2025 • bug

  5. #20092 issue:
    by VideoRyan • Dec 22, 2025 • bug

Show 5 more related issues

  1. #19777 issue:
    by Yaute7 • Dec 05, 2025 • bug

  2. #19861 issue:
    by QuitHub • Dec 10, 2025 • bug

  3. #19877 issue:
    by dotmobo • Dec 11, 2025 • bug

  4. #19563 issue:
    by naruto7g • Nov 28, 2025 • bug

  5. #19211 issue:
    by Byrnes9 • Nov 16, 2025 • bug

💡 Tips:

  • If this is a duplicate, please consider closing this issue and adding any additional details to the existing one
  • If you found a solution in any of these issues, please share it here to help others

This comment was generated automatically by a bot. Please react with a 👍 if this comment was helpful, or a 👎 if it was not.

<!-- gh-comment-id:3683710571 --> @owui-terminator[bot] commented on GitHub (Dec 22, 2025): 🔍 **Similar Issues Found** I found some existing issues that might be related to this one. Please check if any of these are duplicates or contain helpful solutions: 1. [#19752](https://github.com/open-webui/open-webui/issues/19752) **issue: minor UI Bug: knowledge sharing** *by mahenning • Dec 04, 2025 • `bug`* 2. [#20019](https://github.com/open-webui/open-webui/issues/20019) **issue:** *by j63440490 • Dec 17, 2025 • `bug`* 3. [#19864](https://github.com/open-webui/open-webui/issues/19864) **issue:** *by Haervwe • Dec 10, 2025 • `bug`* 4. [#20048](https://github.com/open-webui/open-webui/issues/20048) **issue: Public custom model access broken** *by lochmaster • Dec 19, 2025 • `bug`* 5. [#20092](https://github.com/open-webui/open-webui/issues/20092) **issue:** *by VideoRyan • Dec 22, 2025 • `bug`* <details> <summary>Show 5 more related issues</summary> 6. [#19777](https://github.com/open-webui/open-webui/issues/19777) **issue:** *by Yaute7 • Dec 05, 2025 • `bug`* 7. [#19861](https://github.com/open-webui/open-webui/issues/19861) **issue:** *by QuitHub • Dec 10, 2025 • `bug`* 8. [#19877](https://github.com/open-webui/open-webui/issues/19877) **issue:** *by dotmobo • Dec 11, 2025 • `bug`* 9. [#19563](https://github.com/open-webui/open-webui/issues/19563) **issue:** *by naruto7g • Nov 28, 2025 • `bug`* 10. [#19211](https://github.com/open-webui/open-webui/issues/19211) **issue:** *by Byrnes9 • Nov 16, 2025 • `bug`* </details> --- 💡 **Tips:** - If this is a duplicate, please consider closing this issue and adding any additional details to the existing one - If you found a solution in any of these issues, please share it here to help others *This comment was generated automatically by a bot.* Please react with a 👍 if this comment was helpful, or a 👎 if it was not.
GiteaMirror commented 2026-05-25 11:42:47 -05:00
Author
Owner
Copy Link

@Classic298 commented on GitHub (Dec 30, 2025):

Duplicate/Related to: https://github.com/open-webui/open-webui/issues/20229

<!-- gh-comment-id:3699232133 --> @Classic298 commented on GitHub (Dec 30, 2025): Duplicate/Related to: https://github.com/open-webui/open-webui/issues/20229
GiteaMirror commented 2026-05-25 11:42:48 -05:00
Author
Owner
Copy Link

@Classic298 commented on GitHub (Dec 30, 2025):

Fixed by https://github.com/open-webui/open-webui/pull/20241

<!-- gh-comment-id:3699234769 --> @Classic298 commented on GitHub (Dec 30, 2025): Fixed by https://github.com/open-webui/open-webui/pull/20241
GiteaMirror commented 2026-05-25 11:42:50 -05:00
Author
Owner
Copy Link

@Classic298 commented on GitHub (Dec 30, 2025):

fixed by 61e25dc2dc

<!-- gh-comment-id:3699531200 --> @Classic298 commented on GitHub (Dec 30, 2025): fixed by https://github.com/open-webui/open-webui/commit/61e25dc2dce9c12dcb5b88a6b814060c4338e67b
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#138820
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?