I have searched the existing issues and discussions.
Problem Description
For example, I have a custom model under a workspace. If the model is private, I can grant write access to one group and read access to another, enabling certain users to update the model. However, if I make the model public, only the admin or the model owner can edit it. This means there is no way to allow a specific group of users to manage the model once it’s public.
Desired Solution you'd like
Currently, there are only two visibility options: public or private. I suggest that even when a model is public, it should still be possible to specify group-level permissions, allowing designated groups to manage or edit the model.
Alternatives Considered
No response
Additional Context
No response
Originally created by @frdeng on GitHub (Jul 23, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/15947
Originally assigned to: @tjbck on GitHub.
### Check Existing Issues
- [x] I have searched the existing issues and discussions.
### Problem Description
For example, I have a custom model under a workspace. If the model is private, I can grant write access to one group and read access to another, enabling certain users to update the model. However, if I make the model public, only the admin or the model owner can edit it. This means there is no way to allow a specific group of users to manage the model once it’s public.
### Desired Solution you'd like
Currently, there are only two visibility options: public or private. I suggest that even when a model is public, it should still be possible to specify group-level permissions, allowing designated groups to manage or edit the model.
### Alternatives Considered
_No response_
### Additional Context
_No response_
Added to this, its weird that when a model is set to public all users can see it in their workspace but the save button just hangs with a 400 exit code. Which is weird behavior, I don't want my users to see the system prompt for a custom model I set to public.
I think a model should be able to be set to public - readonly so that it can be used without it being visible in the workspace next to also being writeable by specific groups. Easiest solution would be to change the public tab to an "Everyone" group and have the current "Public sharing" permission mean that the people can see this Everyone group in their sharing settings.
<!-- gh-comment-id:3660688761 -->
@CorneelSoete commented on GitHub (Dec 16, 2025):
Added to this, its weird that when a model is set to public all users can see it in their workspace but the save button just hangs with a 400 exit code. Which is weird behavior, I don't want my users to see the system prompt for a custom model I set to public.
I think a model should be able to be set to public - readonly so that it can be used without it being visible in the workspace next to also being writeable by specific groups. Easiest solution would be to change the public tab to an "Everyone" group and have the current "Public sharing" permission mean that the people can see this Everyone group in their sharing settings.
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 @frdeng on GitHub (Jul 23, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/15947
Originally assigned to: @tjbck on GitHub.
Check Existing Issues
Problem Description
For example, I have a custom model under a workspace. If the model is private, I can grant write access to one group and read access to another, enabling certain users to update the model. However, if I make the model public, only the admin or the model owner can edit it. This means there is no way to allow a specific group of users to manage the model once it’s public.
Desired Solution you'd like
Currently, there are only two visibility options: public or private. I suggest that even when a model is public, it should still be possible to specify group-level permissions, allowing designated groups to manage or edit the model.
Alternatives Considered
No response
Additional Context
No response
@schaveyt commented on GitHub (Dec 10, 2025):
This is desperately needed please
@CorneelSoete commented on GitHub (Dec 16, 2025):
Added to this, its weird that when a model is set to public all users can see it in their workspace but the save button just hangs with a 400 exit code. Which is weird behavior, I don't want my users to see the system prompt for a custom model I set to public.
I think a model should be able to be set to public - readonly so that it can be used without it being visible in the workspace next to also being writeable by specific groups. Easiest solution would be to change the public tab to an "Everyone" group and have the current "Public sharing" permission mean that the people can see this Everyone group in their sharing settings.
@Classic298 commented on GitHub (Dec 21, 2025):
PR welcome