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

issue: When "Knowledge" is disabled for users, it is still possible to add "Knowledge" to chat Folders #6158

New Issue
Closed
opened 2025-11-11 16:46:20 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-11 16:46:20 -06:00
Owner
Copy Link

Originally created by @jsweetzer-ea on GitHub (Aug 21, 2025).

Check Existing Issues

  • I have searched the existing issues and discussions.
  • I am using the latest version of Open WebUI.

Installation Method

Git Clone

Open WebUI Version

0.6.22

Ollama Version (if applicable)

No response

Operating System

AWS 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

When Default Permissions has Knowledge Access toggled off, no access to Knowledge or adjacent functionality should be permitted

This is incompatible with the UI approach taken in Folders for System Prompt - when chat settings are turned off for users, the related System prompt option is not available in Folders

Actual Behavior

It is still possible to "Add Knowledge" to a chat folder and add files to Folders in the same manner as creating a Knowlegde collection

Steps to Reproduce

Disable Knowledge Access in Admin Settings / Users/ Default Permissions

Login as regular user

Open Chat (+) Folder modal

See Knowledge related UI elements

Logs & Screenshots

Admin:

Image

User:

Image

Additional Information

No response

Originally created by @jsweetzer-ea on GitHub (Aug 21, 2025). ### Check Existing Issues - [x] I have searched the existing issues and discussions. - [x] I am using the latest version of Open WebUI. ### Installation Method Git Clone ### Open WebUI Version 0.6.22 ### Ollama Version (if applicable) _No response_ ### Operating System AWS 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 When Default Permissions has Knowledge Access toggled off, no access to Knowledge or adjacent functionality should be permitted This is incompatible with the UI approach taken in Folders for System Prompt - when chat settings are turned off for users, the related System prompt option is not available in Folders ### Actual Behavior It is still possible to "Add Knowledge" to a chat folder and add files to Folders in the same manner as creating a Knowlegde collection ### Steps to Reproduce Disable Knowledge Access in Admin Settings / Users/ Default Permissions Login as regular user Open Chat (+) Folder modal See Knowledge related UI elements ### Logs & Screenshots Admin: <img width="521" height="186" alt="Image" src="https://github.com/user-attachments/assets/63af411d-eede-45a0-9ce5-7622105ff6bc" /> User: <img width="760" height="320" alt="Image" src="https://github.com/user-attachments/assets/1e02ab06-9885-4098-ae1a-193c6573bfbf" /> ### Additional Information _No response_
GiteaMirror added the bug label 2025-11-11 16:46:20 -06:00
GiteaMirror commented 2025-11-11 16:46:21 -06:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Aug 22, 2025):

Intended behaviour, those mean write access.

@tjbck commented on GitHub (Aug 22, 2025): Intended behaviour, those mean write access.
GiteaMirror commented 2025-11-11 16:46:21 -06:00
Author
Owner
Copy Link

@jsweetzer-ea commented on GitHub (Aug 22, 2025):

I see - but that is also at odds with how the Workspace treats retrieval of otherwise public KBs as mentioned before. Why not simply list them in the Workspace page, if they're interactable elsewhere?

this PR would fix the discrepancy
https://github.com/open-webui/open-webui/pull/15797

@jsweetzer-ea commented on GitHub (Aug 22, 2025): I see - but that is also at odds with how the Workspace treats retrieval of otherwise public KBs as mentioned before. Why not simply list them in the Workspace page, if they're interactable elsewhere? this PR would fix the discrepancy https://github.com/open-webui/open-webui/pull/15797
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#6158
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?