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

[GH-ISSUE #23848] feat: Create new Admin Fields to Restrict Knowledge Base File Upload Count & Size #35617

New Issue
Open
opened 2026-04-25 09:47:18 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-04-25 09:47:18 -05:00
Owner
Copy Link

Originally created by @chejohn on GitHub (Apr 17, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/23848

Check Existing Issues

  • I have searched for all existing open AND closed issues and discussions for similar requests. I have found none that is comparable to my request.

Verify Feature Scope

  • I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions.

Problem Description

When navigating to "Admin Settings > Documents" an admin is able to limit the the number of files and file size a user is able to upload to a chat thread via the "Max Upload Size" and "Max Upload Count" fields; however, the same fields are not available for limiting the file size and number of uploads to a Knowledge Base located in Workspace > Knowledge.

Desired Solution you'd like

Our team would like two fields, potentially named "Knowledge Max Upload Size" and "Knowledge Max Upload Count", within "Admin Setting > Documents" that allows admins to limit the max upload size for a particular file into a knowledge base and a max upload count which limits the number of files a user can upload into a knowledge base.

Alternatives Considered

No response

Additional Context

No response

Originally created by @chejohn on GitHub (Apr 17, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/23848 ### Check Existing Issues - [x] I have searched for all existing **open AND closed** issues and discussions for similar requests. I have found none that is comparable to my request. ### Verify Feature Scope - [x] I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions. ### Problem Description When navigating to "Admin Settings > Documents" an admin is able to limit the the number of files and file size a user is able to upload to a chat thread via the "Max Upload Size" and "Max Upload Count" fields; however, the same fields are not available for limiting the file size and number of uploads to a Knowledge Base located in Workspace > Knowledge. ### Desired Solution you'd like Our team would like two fields, potentially named "Knowledge Max Upload Size" and "Knowledge Max Upload Count", within "Admin Setting > Documents" that allows admins to limit the max upload size for a particular file into a knowledge base and a max upload count which limits the number of files a user can upload into a knowledge base. ### Alternatives Considered _No response_ ### Additional Context _No response_
GiteaMirror commented 2026-04-25 09:47:19 -05:00
Author
Owner
Copy Link

@pr-validator-bot commented on GitHub (Apr 17, 2026):

⚠️ Invalid Issue Title

Hey @chejohn, please provide a descriptive title for your issue. Titles that are empty, very short (under 10 characters), or generic (like "issue:" or "feat:") make it difficult for volunteer contributors to understand and triage issues.

Please update the title to reflect the content of your issue.

⚠️ Missing Issue Title Prefix

@chejohn, your issue title is missing a prefix (e.g., bug:, feat:, docs:).

Please update your issue title to include one of the following prefixes:

  • bug: Bug report or error you've encountered
  • feat: Feature request or enhancement suggestion
  • docs: Documentation issue or improvement request
  • question: Question about usage or functionality
  • help: Request for help or support

Example: bug: Login fails when using special characters in password

<!-- gh-comment-id:4270639500 --> @pr-validator-bot commented on GitHub (Apr 17, 2026): # ⚠️ Invalid Issue Title Hey @chejohn, please provide a descriptive title for your issue. Titles that are empty, very short (under 10 characters), or generic (like "issue:" or "feat:") make it difficult for volunteer contributors to understand and triage issues. Please update the title to reflect the content of your issue. --- # ⚠️ Missing Issue Title Prefix @chejohn, your issue title is missing a prefix (e.g., `bug:`, `feat:`, `docs:`). Please update your issue title to include one of the following prefixes: - **bug**: Bug report or error you've encountered - **feat**: Feature request or enhancement suggestion - **docs**: Documentation issue or improvement request - **question**: Question about usage or functionality - **help**: Request for help or support Example: `bug: Login fails when using special characters in password`
GiteaMirror commented 2026-04-25 09:47:19 -05:00
Author
Owner
Copy Link

@rbx commented on GitHub (Apr 20, 2026):

Yes, this would be very useful.
Besides limits on number of documents and their size, it would also be useful to have a list of things to ignore/not include. To be able to filter out things like /node_modules.

<!-- gh-comment-id:4279728842 --> @rbx commented on GitHub (Apr 20, 2026): Yes, this would be very useful. Besides limits on number of documents and their size, it would also be useful to have a list of things to ignore/not include. To be able to filter out things like `/node_modules`.
GiteaMirror commented 2026-04-25 09:47:20 -05:00
Author
Owner
Copy Link

@rbx commented on GitHub (Apr 21, 2026):

@tjbck I could work on and contribute this feature, if desired. Already have a working prototype.
Would it be better as a global setting or a group permission?
I am leaning towards the latter, but I also see that similar chat limits are only exposed as global settings.

<!-- gh-comment-id:4287360024 --> @rbx commented on GitHub (Apr 21, 2026): @tjbck I could work on and contribute this feature, if desired. Already have a working prototype. Would it be better as a global setting or a group permission? I am leaning towards the latter, but I also see that similar chat limits are only exposed as global settings.
GiteaMirror commented 2026-04-25 09:47:20 -05:00
Author
Owner
Copy Link

@rbx commented on GitHub (Apr 22, 2026):

I made a pr draft here: https://github.com/open-webui/open-webui/pull/23992
Not sure if we need a discussion post if we have this issue already...

<!-- gh-comment-id:4295810932 --> @rbx commented on GitHub (Apr 22, 2026): I made a pr draft here: https://github.com/open-webui/open-webui/pull/23992 Not sure if we need a discussion post if we have this issue already...
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
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#35617
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?