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
Version 0.9 introduced a chained base model check, meaning that users can no longer use assistants if they don't have read access to the base model used.
Previous behaviour is still desirable, as it facilitates sharing of assistants for others to use and more granular access control when it comes to the model list.
Desired Solution you'd like
env variable or config setting to allow for the bypass of has_base_model_access.
Alternatives Considered
Workarounds have undesirable consequences:
not writing the models into the DB would effectively bypass the check but result in only admins being able to create assistants
setting base models to public and invisible would limit ui access for users and not allow granular access control in the workspace
Additional Context
No response
Originally created by @JIW-roosi on GitHub (May 13, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/24647
### 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
Version 0.9 introduced a chained base model check, meaning that users can no longer use assistants if they don't have read access to the base model used.
Previous behaviour is still desirable, as it facilitates sharing of assistants for others to use and more granular access control when it comes to the model list.
### Desired Solution you'd like
env variable or config setting to allow for the bypass of `has_base_model_access`.
### Alternatives Considered
Workarounds have undesirable consequences:
- not writing the models into the DB would effectively bypass the check but result in only admins being able to create assistants
- setting base models to public and invisible would limit ui access for users and not allow granular access control in the workspace
### Additional Context
_No response_
@owui-terminator[bot] commented on GitHub (May 13, 2026):
🔍Related Issues Found
I found some existing issues that might be related. Please check if any of these are duplicates or contain helpful solutions:
🟣#23948feat: Workspace model access without base model access Directly requests an env/config option to allow workspace models to be used without base model access, which is essentially the same bypass requested here for assistants. by itsHenry35
🟣#24043issue: Public custom models fail if base model connection is restricted Describes public custom models failing when the base model connection is restricted, matching the regression introduced by the chained base model access check. by jotaperez3 · bug
🟣#24175issue: Model access issue with private base models (works with older models, fails with newer ones) Reports that newer models require base model visibility/access for assistants to work, which is the same underlying permission-check behavior this feature request wants to bypass. by Teimetues · bug
💡 If your issue is a duplicate, please close it and add any additional details to the existing issue instead.
This comment was generated automatically. React with 👍 if helpful, 👎 if not.
<!-- gh-comment-id:4438843307 -->
@owui-terminator[bot] commented on GitHub (May 13, 2026):
<!-- terminator-bot:related-issues-reply -->
🔍 **Related Issues Found**
I found some existing issues that might be related. Please check if any of these are duplicates or contain helpful solutions:
1. 🟣 [#23948](https://github.com/open-webui/open-webui/issues/23948) **feat: Workspace model access without base model access**
*Directly requests an env/config option to allow workspace models to be used without base model access, which is essentially the same bypass requested here for assistants.*
*by itsHenry35*
2. 🟣 [#24043](https://github.com/open-webui/open-webui/issues/24043) **issue: Public custom models fail if base model connection is restricted**
*Describes public custom models failing when the base model connection is restricted, matching the regression introduced by the chained base model access check.*
*by jotaperez3 · `bug`*
3. 🟣 [#24175](https://github.com/open-webui/open-webui/issues/24175) **issue: Model access issue with private base models (works with older models, fails with newer ones)**
*Reports that newer models require base model visibility/access for assistants to work, which is the same underlying permission-check behavior this feature request wants to bypass.*
*by Teimetues · `bug`*
---
💡 If your issue is a duplicate, please close it and add any additional details to the existing issue instead.
*This comment was generated automatically.* React with 👍 if helpful, 👎 if not.
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 @JIW-roosi on GitHub (May 13, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/24647
Check Existing Issues
Verify Feature Scope
Problem Description
Version 0.9 introduced a chained base model check, meaning that users can no longer use assistants if they don't have read access to the base model used.
Previous behaviour is still desirable, as it facilitates sharing of assistants for others to use and more granular access control when it comes to the model list.
Desired Solution you'd like
env variable or config setting to allow for the bypass of
has_base_model_access.Alternatives Considered
Workarounds have undesirable consequences:
Additional Context
No response
@owui-terminator[bot] commented on GitHub (May 13, 2026):
🔍 Related Issues Found
I found some existing issues that might be related. Please check if any of these are duplicates or contain helpful solutions:
🟣 #23948 feat: Workspace model access without base model access
Directly requests an env/config option to allow workspace models to be used without base model access, which is essentially the same bypass requested here for assistants.
by itsHenry35
🟣 #24043 issue: Public custom models fail if base model connection is restricted
Describes public custom models failing when the base model connection is restricted, matching the regression introduced by the chained base model access check.
by jotaperez3 ·
bug🟣 #24175 issue: Model access issue with private base models (works with older models, fails with newer ones)
Reports that newer models require base model visibility/access for assistants to work, which is the same underlying permission-check behavior this feature request wants to bypass.
by Teimetues ·
bug💡 If your issue is a duplicate, please close it and add any additional details to the existing issue instead.
This comment was generated automatically. React with 👍 if helpful, 👎 if not.