[GH-ISSUE #18180] feat: The knowledge base feature hopes to allow other accounts to collaboratively manage the knowledge base that is set to public. #34055

New Issue

GiteaMirror · 2026-04-25T07:57:55-05:00

GiteaMirror commented

2026-04-25 07:57:55 -05:00

Originally created by @yamazakitouma on GitHub (Oct 9, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/18180

Check Existing Issues

I have searched the existing issues and discussions.

Problem Description

In the knowledge base function, when A creates a knowledge base and sets it to "public" (open to all users), B can only use the knowledge base for query tasks in the chat conversation and cannot directly maintain the knowledge base.

Desired Solution you'd like

I hope to set it as a public knowledge base that all users can maintain and manage.

Alternatives Considered

When the knowledge base is set to "public," it is hoped that the interface will provide permission options, including choices for "read" and "write." When the selection is "write," all users are allowed to manage and maintain the knowledge base.

Additional Context

No response

Originally created by @yamazakitouma on GitHub (Oct 9, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/18180 ### Check Existing Issues - [x] I have searched the existing issues and discussions. ### Problem Description In the knowledge base function, when A creates a knowledge base and sets it to "public" (open to all users), B can only use the knowledge base for query tasks in the chat conversation and cannot directly maintain the knowledge base. ### Desired Solution you'd like I hope to set it as a public knowledge base that all users can maintain and manage. ### Alternatives Considered When the knowledge base is set to "public," it is hoped that the interface will provide permission options, including choices for "read" and "write." When the selection is "write," all users are allowed to manage and maintain the knowledge base. ### Additional Context _No response_

GiteaMirror closed this issue

2026-04-25 07:57:55 -05:00

GiteaMirror commented

2026-04-25 07:57:56 -05:00

@silentoplayz commented on GitHub (Oct 9, 2025):

I know this goes against what you're explicitly asking for in your feature request, but I will let you in on some information.

If you set the visibility from Public to Private instead, you could then select any usergroup(s) in which the permission option can be changed between Read and Write access. When set to Write access, all users of the specified usergroup(s) will be able to manage and maintain the knowledge-base (this even applies for catastrophic actions, such as giving usergroup(s) with access to the knowledge collection the ability to delete what they've been provided access to).

@silentoplayz commented on GitHub (Oct 9, 2025): I know this goes against what you're explicitly asking for in your feature request, but I will let you in on some information. If you set the visibility from `Public` to `Private` instead, you could then select any usergroup(s) in which the permission option can be changed between `Read` and `Write` access. When set to `Write` access, all users of the specified usergroup(s) will be able to manage and maintain the knowledge-base (this even applies for catastrophic actions, such as giving usergroup(s) with access to the knowledge collection the ability to delete what they've been provided access to). <img width="513" height="256" alt="Image" src="https://github.com/user-attachments/assets/d313639a-765f-45a5-ae2f-bb29e1f491d4" />

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/open-webui#34055