In the admin dashboard, it would be nice if we can add a feature to hide/disable/enable (not just delete) a model.
Reason:
One organization has a private model that they don't want to share with other users or organizations.
Or perhaps, let's provide a convenient way for organizations to access only allowed models via: Groups or organization.
For instance if a news entity will be accessing the UI, it is very impractical for them to see the medical models from a hospital. Also, it is not a good alternative to have a separate UI for them.
Originally created by @oliverbob on GitHub (Jan 10, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/446
Originally assigned to: @tjbck on GitHub.
In the admin dashboard, it would be nice if we can add a feature to hide/disable/enable (not just delete) a model.
Reason:
One organization has a private model that they don't want to share with other users or organizations.
Or perhaps, let's provide a convenient way for organizations to access only allowed models via: Groups or organization.
For instance if a news entity will be accessing the UI, it is very impractical for them to see the medical models from a hospital. Also, it is not a good alternative to have a separate UI for them.
More granular permissions, and user groups would be handy and I'm sure these would make sense to put on the longterm roadmap.
<!-- gh-comment-id:1884765625 -->
@justinh-rahb commented on GitHub (Jan 10, 2024):
More granular permissions, and user groups would be handy and I'm sure these would make sense to put on the longterm roadmap.
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 @oliverbob on GitHub (Jan 10, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/446
Originally assigned to: @tjbck on GitHub.
In the admin dashboard, it would be nice if we can add a feature to hide/disable/enable (not just delete) a model.
Reason:
One organization has a private model that they don't want to share with other users or organizations.
Or perhaps, let's provide a convenient way for organizations to access only allowed models via: Groups or organization.
For instance if a news entity will be accessing the UI, it is very impractical for them to see the medical models from a hospital. Also, it is not a good alternative to have a separate UI for them.
@justinh-rahb commented on GitHub (Jan 10, 2024):
More granular permissions, and user groups would be handy and I'm sure these would make sense to put on the longterm roadmap.
@justinh-rahb commented on GitHub (Jan 18, 2024):
Related #449
@GeoSaffer commented on GitHub (May 5, 2024):
this would be awesome, please add it
@silentoplayz commented on GitHub (Jun 4, 2024):
Related #1096
@tjbck commented on GitHub (Jun 8, 2024):
Closing in favour of #2924