Originally created by @tigran123 on GitHub (Sep 16, 2025).
Check Existing Issues
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
Pip Install
Open WebUI Version
0.6.28
Ollama Version (if applicable)
0.11.10
Operating System
Ubuntu Linux 22.04.5
Browser (if applicable)
Chrome 138.0.7204.168
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
Users in the USER role should see the models from the external API endpoints, created by the users in the ADMIN role.
Actual Behavior
Users in the USER role do not see the models from the external API endpoints, created by the users in the ADMIN role. And they cannot create new connections either.
Steps to Reproduce
In the fresh install create the first user -- it will have ADMIN role
Point to some OpenAI-compatible API endpoint, e.g. I used Groq
Observe that lots of external models are visible in the model selector
Create a new user in the USER role
Signout from the ADMIN role user
Sign in as USER role user
Observe that no models are visible in the model selector
Now signout and sign in again as ADMIN
Change the USER role to ADMIN
Signout and sign in as that new user (which is now ADMIN)
Observe that all models are now visible
Logs & Screenshots
Additional Information
No response
Originally created by @tigran123 on GitHub (Sep 16, 2025).
### 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
Pip Install
### Open WebUI Version
0.6.28
### Ollama Version (if applicable)
0.11.10
### Operating System
Ubuntu Linux 22.04.5
### Browser (if applicable)
Chrome 138.0.7204.168
### 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
Users in the `USER` role should see the models from the external API endpoints, created by the users in the `ADMIN` role.
### Actual Behavior
Users in the `USER` role do not see the models from the external API endpoints, created by the users in the `ADMIN` role. And they cannot create new connections either.
### Steps to Reproduce
1. In the fresh install create the first user -- it will have `ADMIN` role
2. Point to some OpenAI-compatible API endpoint, e.g. I used Groq
3. Observe that lots of external models are visible in the model selector
4. Create a new user in the `USER` role
5. Signout from the `ADMIN` role user
6. Sign in as `USER` role user
7. Observe that no models are visible in the model selector
8. Now signout and sign in again as `ADMIN`
9. Change the `USER` role to `ADMIN`
10. Signout and sign in as that new user (which is now `ADMIN`)
11. Observe that all models are now visible
### Logs & Screenshots
<img width="1114" height="564" alt="Image" src="https://github.com/user-attachments/assets/a75e4e3c-14ae-4fc3-93eb-e0c32164b730" />
### Additional Information
_No response_
GiteaMirror
added the bug label 2025-11-11 16:54:34 -06:00
I realise, of course, that plainly making them see the connection is NOT a proper solution, because those connection settings contain API key, which may cause money to be spent. But surely there must be a way for USER role users to create their own external connections?
@tigran123 commented on GitHub (Sep 16, 2025):
I realise, of course, that plainly making them see the connection is NOT a proper solution, because those connection settings contain API key, which may cause money to be spent. But surely there must be a way for `USER` role users to create their own external connections?
The new model is private by default; you need to change its visibility to public
This is the "Edit Connection" dialog. I do not see any way to change the visibility or in fact any such setting as "visibility". And we are talking about the whole provider, not just one specific model.
@tigran123 commented on GitHub (Sep 16, 2025):
> The new model is private by default; you need to change its visibility to public
<img width="712" height="712" alt="Image" src="https://github.com/user-attachments/assets/c82aca5a-5290-460b-ac08-f8d90a906ee6" />
This is the "Edit Connection" dialog. I do not see any way to change the visibility or in fact any such setting as "visibility". And we are talking about the whole provider, not just one specific model.
Ah.... understood! In the tab "Models" there is a setting "Visibility" and it can be changed from "Private" to "Public". Ok, I will test it and if it works will close this issue. Thank you!
@tigran123 commented on GitHub (Sep 16, 2025):
Ah.... understood! In the tab "Models" there is a setting "Visibility" and it can be changed from "Private" to "Public". Ok, I will test it and if it works will close this issue. Thank you!
Tested: there is still a bug in there. As ADMIN I have made four models Public: gpt-oss-120b/20b and llama4 (scout/maverick), but when I logged in with USER role I see SIX models in the list: the above four plus two duplicates of the gpt-oss ones, see screenshot below:
@tigran123 commented on GitHub (Sep 16, 2025):
Tested: there is still a bug in there. As `ADMIN` I have made four models `Public`: gpt-oss-120b/20b and llama4 (scout/maverick), but when I logged in with `USER` role I see SIX models in the list: the above four plus two duplicates of the gpt-oss ones, see screenshot below:
<img width="732" height="478" alt="Image" src="https://github.com/user-attachments/assets/4cf5f1ec-c2be-4f6b-be2a-aad90857daa0" />
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 @tigran123 on GitHub (Sep 16, 2025).
Check Existing Issues
Installation Method
Pip Install
Open WebUI Version
0.6.28
Ollama Version (if applicable)
0.11.10
Operating System
Ubuntu Linux 22.04.5
Browser (if applicable)
Chrome 138.0.7204.168
Confirmation
README.md.Expected Behavior
Users in the
USERrole should see the models from the external API endpoints, created by the users in theADMINrole.Actual Behavior
Users in the
USERrole do not see the models from the external API endpoints, created by the users in theADMINrole. And they cannot create new connections either.Steps to Reproduce
ADMINroleUSERroleADMINrole userUSERrole userADMINUSERrole toADMINADMIN)Logs & Screenshots
Additional Information
No response
@tigran123 commented on GitHub (Sep 16, 2025):
I realise, of course, that plainly making them see the connection is NOT a proper solution, because those connection settings contain API key, which may cause money to be spent. But surely there must be a way for
USERrole users to create their own external connections?@EntropyYue commented on GitHub (Sep 16, 2025):
The new model is private by default; you need to change its visibility to public
@tigran123 commented on GitHub (Sep 16, 2025):
This is the "Edit Connection" dialog. I do not see any way to change the visibility or in fact any such setting as "visibility". And we are talking about the whole provider, not just one specific model.
@tigran123 commented on GitHub (Sep 16, 2025):
Ah.... understood! In the tab "Models" there is a setting "Visibility" and it can be changed from "Private" to "Public". Ok, I will test it and if it works will close this issue. Thank you!
@tigran123 commented on GitHub (Sep 16, 2025):
Tested: there is still a bug in there. As
ADMINI have made four modelsPublic: gpt-oss-120b/20b and llama4 (scout/maverick), but when I logged in withUSERrole I see SIX models in the list: the above four plus two duplicates of the gpt-oss ones, see screenshot below: