github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-08 04:16:03 -05:00
Code Issues 1.3k Packages Projects Releases 126 Wiki Activity

[GH-ISSUE #16588] issue: Public knowledge is not visible in the /knowledge page but it is in chat prompt #17966

New Issue
Closed
opened 2026-04-19 23:52:03 -05:00 by GiteaMirror · 6 comments
GiteaMirror commented 2026-04-19 23:52:03 -05:00
Owner
Copy Link

Originally created by @jsweetzer-ea on GitHub (Aug 13, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/16588

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

0.6.23

Ollama Version (if applicable)

No response

Operating System

AWS Linux

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

Knowledge is set to Public by a user and then visible in the Knowledge section of Workspace by all users

Actual Behavior

Public knowledge is not visible in the UI but is visible in the chat by using the hash # command

Steps to Reproduce

Create a knowledge collection
Set to public
Login as another user
Check for knowledge collection in Workspace
Check for knowledge in chat prompt

Logs & Screenshots

Image Image Image

Additional Information

No response

Originally created by @jsweetzer-ea on GitHub (Aug 13, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/16588 ### 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 0.6.23 ### Ollama Version (if applicable) _No response_ ### Operating System AWS Linux ### 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 Knowledge is set to Public by a user and then visible in the Knowledge section of Workspace by all users ### Actual Behavior Public knowledge is not visible in the UI but is visible in the chat by using the hash # command ### Steps to Reproduce Create a knowledge collection Set to public Login as another user Check for knowledge collection in Workspace Check for knowledge in chat prompt ### Logs & Screenshots <img width="642" height="415" alt="Image" src="https://github.com/user-attachments/assets/0bfe7139-79e5-4d58-afbb-eadccafde6ad" /> <img width="727" height="312" alt="Image" src="https://github.com/user-attachments/assets/ba507a51-f0ac-46e2-8474-dba70fc0900b" /> <img width="1052" height="623" alt="Image" src="https://github.com/user-attachments/assets/37dc84a8-ac64-4f41-97d7-a93eb41b082a" /> ### Additional Information _No response_
GiteaMirror added the bug label 2026-04-19 23:52:03 -05:00
GiteaMirror commented 2026-04-19 23:52:05 -05:00
Author
Owner
Copy Link

@Classic298 commented on GitHub (Aug 13, 2025):

Intended behavior

Knowledge should only be visible in the workspace area if the user has write permission to it

<!-- gh-comment-id:3184810703 --> @Classic298 commented on GitHub (Aug 13, 2025): Intended behavior Knowledge should only be visible in the workspace area if the user has write permission to it
GiteaMirror commented 2026-04-19 23:52:06 -05:00
Author
Owner
Copy Link

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

I don't see an option to specify write permission only access (it is either private / group or public)?

Further, how does a user who has read-only (which I assumed this would be as the user is not the creator) ascertain they have access in the first place? They have to look in the chat UI instead of in the Knowledge page?

The user should be able to see they have "read only" permission.

Edit: Docs don't mention anything about read/write?
https://docs.openwebui.com/features/workspace/knowledge/

<!-- gh-comment-id:3184903331 --> @jsweetzer-ea commented on GitHub (Aug 13, 2025): I don't see an option to specify write permission only access (it is either private / group or public)? Further, how does a user who has read-only (which I assumed this would be as the user is not the creator) ascertain they have access in the first place? They have to look in the chat UI instead of in the Knowledge page? The user should be able to see they have "read only" permission. Edit: Docs don't mention anything about read/write? https://docs.openwebui.com/features/workspace/knowledge/
GiteaMirror commented 2026-04-19 23:52:06 -05:00
Author
Owner
Copy Link

@Classic298 commented on GitHub (Aug 13, 2025):

@jsweetzer-ea publicly available models cannot be set with write permission as a security precausion to not give everyone write permissions to the prompt or knowledge or model.

you'd have to share it with individual groups and give those groups write permission

And yes, you cannot share it with individual groups AND publicly at the same time.
This is a duplicate issue.

<!-- gh-comment-id:3185502651 --> @Classic298 commented on GitHub (Aug 13, 2025): @jsweetzer-ea publicly available models cannot be set with write permission as a security precausion to not give everyone write permissions to the prompt or knowledge or model. you'd have to share it with individual groups and give those groups write permission And yes, you cannot share it with individual groups AND publicly at the same time. This is a duplicate issue.
GiteaMirror commented 2026-04-19 23:52:07 -05:00
Author
Owner
Copy Link

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

Which issue does it duplicate?

I think we are talking at cross-purposes. Providing write access to models/prompts/knowledge is a separate topic to the UX of how a user discovers Public shared knowledge.

Public models are clearly available in the model dropdown on the chat page. It is however not intuitive that a user who cannot see any Knowledge listed on their workspace page would know to look for it by entering the # command in the chat. How are they to know?

@tjbck interested in your take please

Thanks again

<!-- gh-comment-id:3185875082 --> @jsweetzer-ea commented on GitHub (Aug 13, 2025): Which issue does it duplicate? I think we are talking at cross-purposes. Providing write access to models/prompts/knowledge is a separate topic to the UX of how a user discovers Public shared knowledge. Public models are clearly available in the model dropdown on the chat page. It is however not intuitive that a user who cannot see any Knowledge listed on their workspace page would know to look for it by entering the # command in the chat. How are they to know? @tjbck interested in your take please Thanks again
GiteaMirror commented 2026-04-19 23:52:07 -05:00
Author
Owner
Copy Link

@Classic298 commented on GitHub (Aug 13, 2025):

Yeah there are many individual issues and/or discussions for both topics we are discussing here.

<!-- gh-comment-id:3185883231 --> @Classic298 commented on GitHub (Aug 13, 2025): Yeah there are many individual issues and/or discussions for both topics we are discussing here.
GiteaMirror commented 2026-04-19 23:52:08 -05:00
Author
Owner
Copy Link

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

I didn't check Discussions, my mistake - I've found the relevant one and PR. Will pickup there.

<!-- gh-comment-id:3185914686 --> @jsweetzer-ea commented on GitHub (Aug 13, 2025): I didn't check Discussions, my mistake - I've found the relevant one and PR. Will pickup there.
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#17966
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?