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
Sharing options for Workspace objects are getting better and better, but one feature is missing: Giving users more control over what is listed in their model selector. There is currently only a global setting for whether a model is hidden or visible, and it can only be set by users with write access.
Desired Solution you'd like
Users should be able to choose which accessible workspace models are listed in the model selector. There should be an entry "Hide" in the meatballs menu for each model selector item and in the meatballs menu on the Worskpace view selector item, even when the user has only READ access to the actual model.
Alternatives Considered
No response
Additional Context
No response
Originally created by @Simon-Stone on GitHub (Jan 15, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/20693
### 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
Sharing options for Workspace objects are getting better and better, but one feature is missing: Giving users more control over what is listed in their model selector. There is currently only a global setting for whether a model is hidden or visible, and it can only be set by users with write access.
### Desired Solution you'd like
Users should be able to choose which accessible workspace models are listed in the model selector. There should be an entry "Hide" in the meatballs menu for each model selector item and in the meatballs menu on the Worskpace view selector item, even when the user has only READ access to the actual model.
### Alternatives Considered
_No response_
### Additional Context
_No response_
To scale the change, user-level sharing can be applied to functions/modesl/prompts/kb etc (anything that supports access control).
It'll be fantasic to have this feature.
<!-- gh-comment-id:3890386730 -->
@silenceroom commented on GitHub (Feb 12, 2026):
Echo this request.
To scale the change, user-level sharing can be applied to functions/modesl/prompts/kb etc (anything that supports access control).
It'll be fantasic to have this feature.
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 @Simon-Stone on GitHub (Jan 15, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/20693
Check Existing Issues
Verify Feature Scope
Problem Description
Sharing options for Workspace objects are getting better and better, but one feature is missing: Giving users more control over what is listed in their model selector. There is currently only a global setting for whether a model is hidden or visible, and it can only be set by users with write access.
Desired Solution you'd like
Users should be able to choose which accessible workspace models are listed in the model selector. There should be an entry "Hide" in the meatballs menu for each model selector item and in the meatballs menu on the Worskpace view selector item, even when the user has only READ access to the actual model.
Alternatives Considered
No response
Additional Context
No response
@silenceroom commented on GitHub (Feb 12, 2026):
Echo this request.
To scale the change, user-level sharing can be applied to functions/modesl/prompts/kb etc (anything that supports access control).
It'll be fantasic to have this feature.
@tjbck commented on GitHub (Mar 25, 2026):
Sidebar Pinned Models should be used here.