[GH-ISSUE #22205] feat: tags as groups for tools/models for better access control #35189

New Issue

GiteaMirror · 2026-04-25T09:25:42-05:00

GiteaMirror commented

2026-04-25 09:25:42 -05:00

Originally created by @blinkyboi on GitHub (Mar 4, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/22205

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

Admins can group users into custom "groups" and individually add said group to whatever resource.
Admins also have the ability to add "tags" that will group resources together for accessibility.

My suggestion requests the ability for more control over allowing individual users and/or "groups" to access resources under the "tags".

For example: when working with ollama connections (local vs external) and have models being loaded/pulled from both, they get labeled with 'Local' and 'External' and all models separated under each label. What if I only want a certain group of users to access 'External' models?

Desired Solution you'd like

Configure per-user or per-group access to a number of tags and resources under those tags
Tags become saved and visible (maybe in their own 'Tags' page) under "groups" in admin menu.
Tags cannot be created outside the dedicated area in admin menu (similar behavior to user groups)
Typing in the tag field triggers a search through existing tags for assignment
Applies to tools, connections and anything taggable.

Alternatives Considered

N/A.

Additional Context

Highlighted in blue are the "tags" I'm referring to. When clicked in this context, models under the tag would show up (after adding the tag to the model in workspace or admin menu > models).
In my case, I want to allow certain groups and users to access "Gemini" or "GLM" or any given tag and not others (for my use case, the resource would be private which enables some to use those resources without making resource public.

Originally created by @blinkyboi on GitHub (Mar 4, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/22205 ### 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 - Admins can group users into custom "groups" and individually add said group to whatever resource. - Admins also have the ability to add "tags" that will group resources together for accessibility. My **suggestion requests** the ability for more control over allowing individual users and/or "groups" to access resources under the "tags". For example: when working with ollama connections (local vs external) and have models being loaded/pulled from both, they get labeled with 'Local' and 'External' and all models separated under each label. What if I only want a certain group of users to access 'External' models? ### Desired Solution you'd like - Configure per-user or per-group access to a number of tags and resources under those tags - Tags become saved and visible (maybe in their own 'Tags' page) under "groups" in admin menu. - Tags cannot be created outside the dedicated area in admin menu (similar behavior to user groups) - Typing in the tag field triggers a search through existing tags for assignment - Applies to tools, connections and anything taggable. ### Alternatives Considered N/A. ### Additional Context Highlighted in blue are the "tags" I'm referring to. When clicked in this context, models under the tag would show up (after adding the tag to the model in workspace or admin menu > models). In my case, I want to allow certain groups and users to access "Gemini" or "GLM" or any given tag and not others (for my use case, the resource would be private which enables some to use those resources without making resource public. <img width="1080" height="2400" alt="Image" src="https://github.com/user-attachments/assets/529e6ef3-3cc8-48cc-b11b-ed90cd3a9b85" />

GiteaMirror closed this issue

2026-04-25 09:25:42 -05:00

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/open-webui#35189