The admin user will see the models and the api key will work, but normal users won't see it at all. How to deploy it in a way that users can simply log in and have models available to them?
Actual Behavior
User logs in,
no models appear at all
Steps to Reproduce
Open webui. Log as admin. Models appear.
Log as user. No models. Worse, as unsetting the "direct connections" on the admin ui, users can't even have their own - just an empty open webui.
Logs & Screenshots
Admin view:
Normal user view:
Additional Information
No response
Originally created by @surak on GitHub (Apr 24, 2025).
### Check Existing Issues
- [x] I have searched the existing issues and discussions.
- [x] I am using the latest version of Open WebUI.
### Installation Method
Pip Install
### Open WebUI Version
v0.6.5
### Ollama Version (if applicable)
_No response_
### Operating System
Ubuntu 20.04
### Browser (if applicable)
all
### 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 listed steps to reproduce the bug in detail.
### Expected Behavior
Launch open-webui with
```bash
ENABLE_LOGIN_FORM="True" \
WEBUI_AUTH=true \
ENABLE_SIGNUP="True" \
CUSTOM_NAME="Blablador" \
DEFAULT_MODELS="alias-fast" \
ENABLE_OPENAI_API="True" \
OPENAI_API_BASE_URL="https://api.helmholtz-blablador.fz-juelich.de/v1/" \
OPENAI_API_KEY="MY_KEYj" \
open-webui serve --port 31100
```
The admin user will see the models and the api key will work, but normal users won't see it at all. How to deploy it in a way that users can simply log in and have models available to them?
### Actual Behavior
User logs in,
no models appear at all
### Steps to Reproduce
Open webui. Log as admin. Models appear.
Log as user. No models. Worse, as unsetting the "direct connections" on the admin ui, users can't even have their own - just an empty open webui.
### Logs & Screenshots
Admin view:
<img width="457" alt="Image" src="https://github.com/user-attachments/assets/aa74af1b-cd2a-40d3-a485-01436d4a8dd0" />
Normal user view:
<img width="473" alt="Image" src="https://github.com/user-attachments/assets/3e0b1a04-f162-4871-ba07-c1485ed6090b" />
### Additional Information
_No response_
GiteaMirror
added the bug label 2025-11-11 16:07:56 -06:00
@soundworker-com commented on GitHub (Apr 24, 2025):
Have you set the visibility of the models to public or made them accessible to a user group that the user is a member of? You can check in admin settings -> models by clicking on the pencil symbol next to the model toggle.
@soundworker-com commented on GitHub (Apr 24, 2025):
Have you set the visibility of the models to public or made them accessible to a user group that the user is a member of? You can check in admin settings -> models by clicking on the pencil symbol next to the model toggle.
Intended behaviour, all models are private by default. PLEASE read our docs first.
It's pretty offensive to assume I haven't.
Even now knowing that this is the case, it's not easy to find this on the documentation. The search for "model" or "models" returns nothing on this regard, neither does "visibility", "private", or "model access control"
I understand that this is possible with the variable BYPASS_MODEL_ACCESS_CONTROL - which doesn't seem easy to find unless one goes over the whole documentation.
There are discussions discussions here on GitHub about this, so it's not clear [ open-webui/discussions/12770, open-webui/discussions/11335 ].
If BYPASS_MODEL_ACCESS_CONTROL is the correct way of dealing with this, I am more than happy to submit a pull request with clarification on the documentation. Just let me know.
@surak commented on GitHub (Apr 25, 2025):
> Intended behaviour, all models are private by default. PLEASE read our docs first.
It's pretty offensive to assume I haven't.
Even now knowing that this is the case, it's not easy to find this on the documentation. The search for "model" or "models" returns nothing on this regard, neither does "visibility", "private", or "model access control"
I understand that this is possible with the variable `BYPASS_MODEL_ACCESS_CONTROL` - which doesn't seem easy to find unless one goes over the whole documentation.
There are discussions discussions here on GitHub about this, so it's not clear [ open-webui/discussions/12770, open-webui/discussions/11335 ].
If `BYPASS_MODEL_ACCESS_CONTROL` is the correct way of dealing with this, I am more than happy to submit a pull request with clarification on the documentation. Just let me know.
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 @surak on GitHub (Apr 24, 2025).
Check Existing Issues
Installation Method
Pip Install
Open WebUI Version
v0.6.5
Ollama Version (if applicable)
No response
Operating System
Ubuntu 20.04
Browser (if applicable)
all
Confirmation
README.md.Expected Behavior
Launch open-webui with
The admin user will see the models and the api key will work, but normal users won't see it at all. How to deploy it in a way that users can simply log in and have models available to them?
Actual Behavior
User logs in,
no models appear at all
Steps to Reproduce
Open webui. Log as admin. Models appear.
Log as user. No models. Worse, as unsetting the "direct connections" on the admin ui, users can't even have their own - just an empty open webui.
Logs & Screenshots
Admin view:

Normal user view:

Additional Information
No response
@soundworker-com commented on GitHub (Apr 24, 2025):
Have you set the visibility of the models to public or made them accessible to a user group that the user is a member of? You can check in admin settings -> models by clicking on the pencil symbol next to the model toggle.
@tjbck commented on GitHub (Apr 25, 2025):
Intended behaviour, all models are private by default. PLEASE read our docs first.
@tjbck commented on GitHub (Apr 25, 2025):
Intended behaviour, all models are private by default. PLEASE read our docs first.
@surak commented on GitHub (Apr 25, 2025):
It's pretty offensive to assume I haven't.
Even now knowing that this is the case, it's not easy to find this on the documentation. The search for "model" or "models" returns nothing on this regard, neither does "visibility", "private", or "model access control"
I understand that this is possible with the variable
BYPASS_MODEL_ACCESS_CONTROL- which doesn't seem easy to find unless one goes over the whole documentation.There are discussions discussions here on GitHub about this, so it's not clear [ open-webui/discussions/12770, open-webui/discussions/11335 ].
If
BYPASS_MODEL_ACCESS_CONTROLis the correct way of dealing with this, I am more than happy to submit a pull request with clarification on the documentation. Just let me know.