I have searched the existing issues and discussions.
Problem Description
Right now we can only use the globally defined RAG Settings for each knowledge base, but some collections need different settings than others. #9361
Parts of this problem: #12204#7679
Desired Solution you'd like
When creating the knowledge, have a switch to turn on/off individual config and have the same settingspanel as in the settings->documents.
Save the RAG config to the DB and in backend distinguish between individual and default RAG settings via simple DB call if the default is True/False.
Further add a new modal to the knowledge base to edit the rag config again.
Alternatives Considered
No response
Additional Context
I already started working on this and have a running version. Only issue is now as mentioned in #12204 , how it should be handled when the model has multiple knowledge bases.
Originally created by @Maytown on GitHub (May 23, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/14231
### Check Existing Issues
- [x] I have searched the existing issues and discussions.
### Problem Description
Right now we can only use the globally defined RAG Settings for each knowledge base, but some collections need different settings than others. #9361
Parts of this problem: #12204 #7679
### Desired Solution you'd like
When creating the knowledge, have a switch to turn on/off individual config and have the same settingspanel as in the settings->documents.
Save the RAG config to the DB and in backend distinguish between individual and default RAG settings via simple DB call if the default is True/False.
Further add a new modal to the knowledge base to edit the rag config again.
### Alternatives Considered
_No response_
### Additional Context
I already started working on this and have a running version. Only issue is now as mentioned in #12204 , how it should be handled when the model has multiple knowledge bases.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @Maytown on GitHub (May 23, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/14231
Check Existing Issues
Problem Description
Right now we can only use the globally defined RAG Settings for each knowledge base, but some collections need different settings than others. #9361
Parts of this problem: #12204 #7679
Desired Solution you'd like
When creating the knowledge, have a switch to turn on/off individual config and have the same settingspanel as in the settings->documents.
Save the RAG config to the DB and in backend distinguish between individual and default RAG settings via simple DB call if the default is True/False.
Further add a new modal to the knowledge base to edit the rag config again.
Alternatives Considered
No response
Additional Context
I already started working on this and have a running version. Only issue is now as mentioned in #12204 , how it should be handled when the model has multiple knowledge bases.