github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-06 10:58:17 -05:00
Code Issues 1.3k Packages Projects Releases 126 Wiki Activity

[GH-ISSUE #17182] issue: Chat folders remember knowledge despite revoked permission for user group #18198

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

Originally created by @wdepree on GitHub (Sep 3, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/17182

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

Ollama Version (if applicable)

No response

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

When revoking permission for a specific knowledge folder for a certain group, one would expect that if that knowledge folder was previously added as knowledge to a conversation folder, it would also be removed. However, this is not the case.

Actual Behavior

The knowledge remains available in the conversation folder and only disappears upon manual removal by the user.

Steps to Reproduce

  1. Grant group permission to access a specific knowledge folder ("Folder A") in Workspace (sceenshot 1).
  2. A member of that group creates a conversation folder and adds Folder A as a knowledge source (screenshot 2).
  3. The admin removes the group’s permission to Folder A (screenshot 3).
  4. The person loses direct access to Folder A (screenshot 4), but it remains accessible through the conversation folder because it was added earlier (screenshot 5).

Logs & Screenshots

Image Image Image Image Image

Additional Information

No response

Originally created by @wdepree on GitHub (Sep 3, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/17182 ### 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.26 ### Ollama Version (if applicable) _No response_ ### 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 When revoking permission for a specific knowledge folder for a certain group, one would expect that if that knowledge folder was previously added as knowledge to a conversation folder, it would also be removed. However, this is not the case. ### Actual Behavior The knowledge remains available in the conversation folder and only disappears upon manual removal by the user. ### Steps to Reproduce 1. Grant group permission to access a specific knowledge folder ("Folder A") in Workspace (sceenshot 1). 2. A member of that group creates a conversation folder and adds Folder A as a knowledge source (screenshot 2). 3. The admin removes the group’s permission to Folder A (screenshot 3). 4. The person loses direct access to Folder A (screenshot 4), but it remains accessible through the conversation folder because it was added earlier (screenshot 5). ### Logs & Screenshots <img width="1454" height="1148" alt="Image" src="https://github.com/user-attachments/assets/1db36e4a-6840-43d7-b435-d77a80eec9c8" /> <img width="1452" height="1083" alt="Image" src="https://github.com/user-attachments/assets/e8c916a4-e669-4b54-9e2f-1f40d6cd7dcb" /> <img width="1453" height="1072" alt="Image" src="https://github.com/user-attachments/assets/3a3a4afb-1e7e-4c99-93bf-8111735f5096" /> <img width="1343" height="708" alt="Image" src="https://github.com/user-attachments/assets/b3fdaaf3-dd8a-408d-813f-a8a68969b29b" /> <img width="1017" height="643" alt="Image" src="https://github.com/user-attachments/assets/29167b5e-ed19-4fb4-b8c4-a456afa3e839" /> ### Additional Information _No response_
GiteaMirror added the bug label 2026-04-20 00:24:40 -05:00
GiteaMirror commented 2026-04-20 00:24:41 -05:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Sep 6, 2025):

Addressed with 40e40d1ddd in dev!

<!-- gh-comment-id:3263215314 --> @tjbck commented on GitHub (Sep 6, 2025): Addressed with 40e40d1dddf9ca937e99af41c8ca038dbc93a7e6 in dev!
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#18198
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?