Is your feature request related to a problem? Please describe.
In the current system, workflows are managed globally, which creates several challenges:
I cannot provide my users with admin access to modify workflows because it would impact all users globally.
If two users need to run image generation simultaneously with different workflows, the system cannot accommodate this, leading to conflicts.
Managing workflows on behalf of individual users is time-consuming and impractical, especially when coordinating usage to avoid interruptions.
Describe the solution you'd like
Introduce a feature to manage workflows at a per-user or per-group level:
Allow admins to save and configure multiple workflows, similar to how different models are managed.
Assign specific workflows to user groups, selecting a default workflow for them.
Enable end users to select from the workflows assigned to them without affecting other users or requiring admin intervention.
Describe alternatives you've considered
Currently, I don't see viable alternatives to address these challenges, but I am open to exploring other potential solutions.
Originally created by @edurenye on GitHub (Jan 12, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/8491
**Is your feature request related to a problem? Please describe.**
In the current system, workflows are managed globally, which creates several challenges:
* I cannot provide my users with admin access to modify workflows because it would impact all users globally.
* If two users need to run image generation simultaneously with different workflows, the system cannot accommodate this, leading to conflicts.
* Managing workflows on behalf of individual users is time-consuming and impractical, especially when coordinating usage to avoid interruptions.
**Describe the solution you'd like**
Introduce a feature to manage workflows at a per-user or per-group level:
* Allow admins to save and configure multiple workflows, similar to how different models are managed.
* Assign specific workflows to user groups, selecting a default workflow for them.
* Enable end users to select from the workflows assigned to them without affecting other users or requiring admin intervention.
**Describe alternatives you've considered**
Currently, I don't see viable alternatives to address these challenges, but I am open to exploring other potential solutions.
Would be even better to do this in a more global image model selection not just workflows, so you can have multiple image providers enabled at the same time. I imagine users with enough permissions should be able to select the model they want to use inside the Chat controls in the top right corner of the screen. What do you think?
<!-- gh-comment-id:2622861660 -->
@edurenye commented on GitHub (Jan 29, 2025):
Would be even better to do this in a more global image model selection not just workflows, so you can have multiple image providers enabled at the same time. I imagine users with enough permissions should be able to select the model they want to use inside the Chat controls in the top right corner of the screen. What do you think?
I'd also suggest that it might be useful to go even more granular than user/group and have workflows for each model that is created in a workspace, offering the opportunity to dedicate specific models for different types of generative workflows.
<!-- gh-comment-id:2667313582 -->
@j05hau commented on GitHub (Feb 19, 2025):
This.
I'd also suggest that it might be useful to go even more granular than user/group and have workflows for each model that is created in a workspace, offering the opportunity to dedicate specific models for different types of generative workflows.
I just realized that I forgot to check the access permission, will fix it when I have time.
You could take a look at it, I have uploaded screenshots in the PR (I fixed the upload workflow from a file that is missing in the screenshots in my branch), or test my branch.
I'll open a discussion around it.
<!-- gh-comment-id:2668176208 -->
@edurenye commented on GitHub (Feb 19, 2025):
@j05hau you can with the branch that I created for the PR https://github.com/open-webui/open-webui/pull/9712
I'm actually keeping it up to date and improving it in my branch: https://github.com/edurenye/open-webui/tree/multiple-image-model-wrappers
I just realized that I forgot to check the access permission, will fix it when I have time.
You could take a look at it, I have uploaded screenshots in the PR (I fixed the upload workflow from a file that is missing in the screenshots in my branch), or test my branch.
I'll open a discussion around it.
<!-- gh-comment-id:2668196295 -->
@edurenye commented on GitHub (Feb 19, 2025):
Here is the discussion: https://github.com/open-webui/open-webui/discussions/10344
I fixed the access checks and updated the branch with the last release (v0.5.16).
<!-- gh-comment-id:2674634302 -->
@edurenye commented on GitHub (Feb 21, 2025):
I fixed the access checks and updated the branch with the last release (v0.5.16).
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 @edurenye on GitHub (Jan 12, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/8491
Is your feature request related to a problem? Please describe.
In the current system, workflows are managed globally, which creates several challenges:
Describe the solution you'd like
Introduce a feature to manage workflows at a per-user or per-group level:
Describe alternatives you've considered
Currently, I don't see viable alternatives to address these challenges, but I am open to exploring other potential solutions.
@edurenye commented on GitHub (Jan 29, 2025):
Would be even better to do this in a more global image model selection not just workflows, so you can have multiple image providers enabled at the same time. I imagine users with enough permissions should be able to select the model they want to use inside the Chat controls in the top right corner of the screen. What do you think?
@j05hau commented on GitHub (Feb 19, 2025):
This.
I'd also suggest that it might be useful to go even more granular than user/group and have workflows for each model that is created in a workspace, offering the opportunity to dedicate specific models for different types of generative workflows.
@edurenye commented on GitHub (Feb 19, 2025):
@j05hau you can with the branch that I created for the PR https://github.com/open-webui/open-webui/pull/9712
I'm actually keeping it up to date and improving it in my branch: https://github.com/edurenye/open-webui/tree/multiple-image-model-wrappers
I just realized that I forgot to check the access permission, will fix it when I have time.
You could take a look at it, I have uploaded screenshots in the PR (I fixed the upload workflow from a file that is missing in the screenshots in my branch), or test my branch.
I'll open a discussion around it.
@edurenye commented on GitHub (Feb 19, 2025):
Here is the discussion: https://github.com/open-webui/open-webui/discussions/10344
@edurenye commented on GitHub (Feb 21, 2025):
I fixed the access checks and updated the branch with the last release (v0.5.16).
@j05hau commented on GitHub (Feb 22, 2025):
You're doing god's work. Thanks, I'll give it a geezer when I can!