I have searched for any existing and/or related issues.
I have searched for any existing and/or related discussions.
I am using the latest version of Open WebUI.
Installation Method
Docker
Open WebUI Version
v.0.6.34
Ollama Version (if applicable)
No response
Operating System
Ubuntu 24.04
Browser (if applicable)
all browsers
Confirmation
I have read and followed all instructions in README.md.
I am using the latest version of both Open WebUI and Ollama.
I have included the browser console logs.
I have included the Docker container logs.
I have provided every relevant configuration, setting, and environment variable used in my setup.
I have clearly listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
I have documented step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation. My steps:
Start with the initial platform/version/OS and dependencies used,
Specify exact install/launch/configure commands,
List URLs visited, user input (incl. example values/emails/passwords if needed),
Describe all options and toggles enabled or changed,
Include any files or environmental changes,
Identify the expected and actual result at each stage,
Ensure any reasonably skilled user can follow and hit the same issue.
Expected Behavior
MS365 admin cannot create new or modify existing models in Workspace section as base models are not snown.
Actual Behavior
After 4h of trying different things, ive logged in with local admin and the base models could be selected.
The issue is there since v0.6.33
Steps to Reproduce
no details
Logs & Screenshots
no details
Additional Information
no details
Originally created by @Igortos on GitHub (Oct 16, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/18371
### Check Existing Issues
- [x] I have searched for any existing and/or related issues.
- [x] I have searched for any existing and/or related discussions.
- [x] I am using the latest version of Open WebUI.
### Installation Method
Docker
### Open WebUI Version
v.0.6.34
### Ollama Version (if applicable)
_No response_
### Operating System
Ubuntu 24.04
### Browser (if applicable)
all browsers
### Confirmation
- [x] I have read and followed all instructions in `README.md`.
- [x] I am using the latest version of **both** Open WebUI and Ollama.
- [x] I have included the browser console logs.
- [x] I have included the Docker container logs.
- [x] I have **provided every relevant configuration, setting, and environment variable used in my setup.**
- [x] I have clearly **listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup** (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
- [x] I have documented **step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation**. My steps:
- Start with the initial platform/version/OS and dependencies used,
- Specify exact install/launch/configure commands,
- List URLs visited, user input (incl. example values/emails/passwords if needed),
- Describe all options and toggles enabled or changed,
- Include any files or environmental changes,
- Identify the expected and actual result at each stage,
- Ensure any reasonably skilled user can follow and hit the same issue.
### Expected Behavior
MS365 admin cannot create new or modify existing models in Workspace section as base models are not snown.
### Actual Behavior
After 4h of trying different things, ive logged in with local admin and the base models could be selected.
The issue is there since v0.6.33
### Steps to Reproduce
no details
### Logs & Screenshots
no details
### Additional Information
no details
GiteaMirror
added the bug label 2026-05-20 23:58:17 -05:00
steps to reproduce? Did you ensure the admin has access permission to the models?
<!-- gh-comment-id:3412469166 -->
@Classic298 commented on GitHub (Oct 16, 2025):
steps to reproduce? Did you ensure the admin has access permission to the models?
Yes, it is the admin of the organization. For sure he has full control over everything except to see base models in Workspace.
This issue is from v.0.6.33
<!-- gh-comment-id:3412518104 -->
@Igortos commented on GitHub (Oct 16, 2025):
Yes, it is the admin of the organization. For sure he has full control over everything except to see base models in Workspace.
This issue is from v.0.6.33
<img width="689" height="459" alt="Image" src="https://github.com/user-attachments/assets/68f5a67c-6d08-4d62-9a95-786210b3ec0d" />
Unable to reproduce, are you sure the connections are system level as well?
<!-- gh-comment-id:3412607684 -->
@tjbck commented on GitHub (Oct 16, 2025):
Unable to reproduce, are you sure the connections are system level as well?
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 @Igortos on GitHub (Oct 16, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/18371
Check Existing Issues
Installation Method
Docker
Open WebUI Version
v.0.6.34
Ollama Version (if applicable)
No response
Operating System
Ubuntu 24.04
Browser (if applicable)
all browsers
Confirmation
README.md.Expected Behavior
MS365 admin cannot create new or modify existing models in Workspace section as base models are not snown.
Actual Behavior
After 4h of trying different things, ive logged in with local admin and the base models could be selected.
The issue is there since v0.6.33
Steps to Reproduce
no details
Logs & Screenshots
no details
Additional Information
no details
@Classic298 commented on GitHub (Oct 16, 2025):
steps to reproduce? Did you ensure the admin has access permission to the models?
@Igortos commented on GitHub (Oct 16, 2025):
Yes, it is the admin of the organization. For sure he has full control over everything except to see base models in Workspace.
This issue is from v.0.6.33
@Classic298 commented on GitHub (Oct 16, 2025):
@Igortos do you use the variable BYPASS_ADMIN_ACCESS_CONTROL ?
@tjbck commented on GitHub (Oct 16, 2025):
Unable to reproduce, are you sure the connections are system level as well?