github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-06 10:58:17 -05:00
Code Issues 1.2k Packages Projects Releases 126 Wiki Activity

[GH-ISSUE #20170] feat: Group-Based Model Access Control #57777

New Issue
Closed
opened 2026-05-05 21:35:17 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-05-05 21:35:17 -05:00
Owner
Copy Link

Originally created by @jptube153-source on GitHub (Dec 25, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/20170

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

It seems that the current model access control only allows settings for public or private.

Desired Solution you'd like

It would be very useful to have the option to define access scope by group (or individual user).

Alternatives Considered

For example, advanced model features could be shared only with users who require them, through group-based settings.
We kindly ask for your positive consideration of this enhancement.

Additional Context

No response

Originally created by @jptube153-source on GitHub (Dec 25, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/20170 ### 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 It seems that the current model access control only allows settings for public or private. ### Desired Solution you'd like It would be very useful to have the option to define access scope by group (or individual user). ### Alternatives Considered For example, advanced model features could be shared only with users who require them, through group-based settings. We kindly ask for your positive consideration of this enhancement. ### Additional Context _No response_
GiteaMirror commented 2026-05-05 21:35:18 -05:00
Author
Owner
Copy Link

@owui-terminator[bot] commented on GitHub (Dec 25, 2025):

🔍 Similar Issues Found

I found some existing issues that might be related to this one. Please check if any of these are duplicates or contain helpful solutions:

  1. #19817 feat: Ability to specify different task models for different tasks and user groups
    by Mikikrus • Dec 08, 2025

  2. #20028 feat:
    by digin1 • Dec 18, 2025

  3. #15947 feat: Allow non-admin user to edit resources under workspace with public visibility
    by frdeng • Jul 23, 2025

  4. #14132 feat: allow group assignment for public models
    by grzegorzwilki • May 21, 2025

  5. #7104 enh: toggle option for group users to make models public
    by tkg61 • Nov 20, 2024

Show 5 more related issues

  1. #6400 feature request: user groups + filter models per user group
    by RocketRider • Oct 25, 2024

  2. #10033 feat: Support changing all models' visibility at once
    by TibixDev • Feb 14, 2025

  3. #7085 Add Model Control Feature in Group Editing Interface
    by JoelShepard • Nov 20, 2024

  4. #446 feat: granular permissions, and user groups
    by oliverbob • Jan 10, 2024 • enhancement, good first issue

  5. #4809 FEAT: Document Groups for Enhanced Access Control
    by RobinBially • Aug 22, 2024

💡 Tips:

  • If this is a duplicate, please consider closing this issue and adding any additional details to the existing one
  • If you found a solution in any of these issues, please share it here to help others

This comment was generated automatically by a bot. Please react with a 👍 if this comment was helpful, or a 👎 if it was not.

<!-- gh-comment-id:3691422243 --> @owui-terminator[bot] commented on GitHub (Dec 25, 2025): 🔍 **Similar Issues Found** I found some existing issues that might be related to this one. Please check if any of these are duplicates or contain helpful solutions: 1. [#19817](https://github.com/open-webui/open-webui/issues/19817) **feat: Ability to specify different task models for different tasks and user groups** *by Mikikrus • Dec 08, 2025* 2. [#20028](https://github.com/open-webui/open-webui/issues/20028) **feat:** *by digin1 • Dec 18, 2025* 3. [#15947](https://github.com/open-webui/open-webui/issues/15947) **feat: Allow non-admin user to edit resources under workspace with public visibility** *by frdeng • Jul 23, 2025* 4. [#14132](https://github.com/open-webui/open-webui/issues/14132) **feat: allow group assignment for public models** *by grzegorzwilki • May 21, 2025* 5. [#7104](https://github.com/open-webui/open-webui/issues/7104) **enh: toggle option for group users to make models public** *by tkg61 • Nov 20, 2024* <details> <summary>Show 5 more related issues</summary> 6. [#6400](https://github.com/open-webui/open-webui/issues/6400) **feature request: user groups + filter models per user group** *by RocketRider • Oct 25, 2024* 7. [#10033](https://github.com/open-webui/open-webui/issues/10033) **feat: Support changing all models' visibility at once** *by TibixDev • Feb 14, 2025* 8. [#7085](https://github.com/open-webui/open-webui/issues/7085) **Add Model Control Feature in Group Editing Interface** *by JoelShepard • Nov 20, 2024* 9. [#446](https://github.com/open-webui/open-webui/issues/446) **feat: granular permissions, and user groups** *by oliverbob • Jan 10, 2024 • `enhancement`, `good first issue`* 10. [#4809](https://github.com/open-webui/open-webui/issues/4809) **FEAT: Document Groups for Enhanced Access Control** *by RobinBially • Aug 22, 2024* </details> --- 💡 **Tips:** - If this is a duplicate, please consider closing this issue and adding any additional details to the existing one - If you found a solution in any of these issues, please share it here to help others *This comment was generated automatically by a bot.* Please react with a 👍 if this comment was helpful, or a 👎 if it was not.
GiteaMirror commented 2026-05-05 21:35:20 -05:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Dec 26, 2025):

This feature has been a part of Open WebUI for a very long time.

<!-- gh-comment-id:3692941518 --> @tjbck commented on GitHub (Dec 26, 2025): This feature has been a part of Open WebUI for a very long time.
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#57777
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?