Skip to content

issue: Public custom model access broken #20048

@lochmaster

Description

@lochmaster

Check Existing Issues

  • I have searched for any existing and/or related issues.
  • I have searched for any existing and/or related discussions.
  • I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!).
  • I am using the latest version of Open WebUI.

Installation Method

Docker

Open WebUI Version

v0.6.41

Ollama Version (if applicable)

0.13.0

Operating System

Windows

Browser (if applicable)

Edge

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

As administrator i have the possibility to enable users to create their own models, knowledge collections and prompts. This can be enabled in the permission tab of corresponding user group:

Image

However, models, collections, and prompts with public access (and likely tools as well—this has not been tested) should not be visible to or editable by users, as they are managed and owned by the administrator. Users should neither see nor be able to modify these public items from within their workspace.

The expected behavior described above currently applies correctly to Knowledge, Prompts, and likely Tools.

Actual Behavior

In the latest version of OWUI, public access models appear in user workspaces and can not only be viewed but also seemingly be edited. Users can click the three-dot menu and select Edit on a public model (note: clicking on the model itself does not display its settings, as it typically does for administrators). Users can make changes, although it appears they are not saved successfully after clicking Save & Update.

This behavior for models does not seem intended and is inconsistent with how access is handled for Knowledge, Prompts, and likely Tools.

Steps to Reproduce

  1. As admin create a custom model and a custom prompt and set their Access to Public
  2. Create a user group that has permission to access Models and Prompts functions inside the user's workspace (see screenshot above).
  3. Log-in as a user which is part of the above created user group.
  4. Check the user's workspace and compare visibility/editability of models with prompts.
    4.1 Public models visible/"editable" --> not expected
    4.2 Public prompts not visible --> expected

Logs & Screenshots

.

Additional Information

It might we worth considering whether users should have a read-only view (without editable text fields, buttons, etc.) of publicly accessible items such as Models, Knowledge, Prompts, or Tools in their workspace to better understand their purpose.

My Podman Container Config:

services:
open-webui:
image: registry./
container_name: open-webui
restart: always
ports:
- ":3000:8080"
volumes:
- open-webui:/app/backend/data
environment:
OAUTH_CLIENT_ID: ""
OAUTH_CLIENT_SECRET: ""
OPENID_PROVIDER_URL: ""
ENABLE_OAUTH_SIGNUP: "true"
OAUTH_PROVIDER_NAME: ""
ENABLE_OAUTH_GROUP_MANAGEMENT: "true"
OAUTH_GROUP_CLAIM: "groups"
OAUTH_SCOPES: "openid email profile"
OPENID_REDIRECT_URI: "/oauth/oidc/callback"
ENABLE_ADMIN_CHAT_ACCESS: "false"
REQUESTS_CA_BUNDLE: ""
CURL_CA_BUNDLE: ""
SSL_CERT_FILE: ""

volumes:
open-webui:
external: true

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions