github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-07-11 10:34:13 -05:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

[GH-ISSUE #19551] issue: User Account API Menu Missing in Version 0.6.40 #73525

New Issue
Closed
opened 2026-05-13 05:52:49 -05:00 by GiteaMirror · 7 comments
GiteaMirror commented 2026-05-13 05:52:49 -05:00
Owner
Copy Link

Originally created by @oboeglen on GitHub (Nov 27, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/19551

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.40

Ollama Version (if applicable)

No response

Operating System

Debian 12

Browser (if applicable)

Firefox

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

API that showing key and JWT Token

Actual Behavior

Hello!
I’ve noticed that the API menu under the user account settings has disappeared in version 0.6.40.
I’m unsure if this is an intentional change or a bug.

Could anyone confirm whether they’re also experiencing this issue?

If it’s a known problem, any guidance on how to restore the menu or alternative ways to access API settings would be greatly appreciated.

Steps to Reproduce

1.Log in to the application.
2.Navigate to the user account settings.
3.Check if the API menu (or related options) is visible.

Logs & Screenshots

Non screenshot

Additional Information

No response

Originally created by @oboeglen on GitHub (Nov 27, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/19551 ### 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 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!). - [x] I am using the latest version of Open WebUI. ### Installation Method Docker ### Open WebUI Version v0.6.40 ### Ollama Version (if applicable) _No response_ ### Operating System Debian 12 ### Browser (if applicable) Firefox ### 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 API that showing key and JWT Token ### Actual Behavior Hello! I’ve noticed that the API menu under the user account settings has disappeared in version 0.6.40. I’m unsure if this is an intentional change or a bug. Could anyone confirm whether they’re also experiencing this issue? If it’s a known problem, any guidance on how to restore the menu or alternative ways to access API settings would be greatly appreciated. ### Steps to Reproduce 1.Log in to the application. 2.Navigate to the user account settings. 3.Check if the API menu (or related options) is visible. ### Logs & Screenshots Non screenshot ### Additional Information _No response_
GiteaMirror added the bug label 2026-05-13 05:52:49 -05:00
GiteaMirror commented 2026-05-13 05:52:52 -05:00
Author
Owner
Copy Link

@R-omk commented on GitHub (Nov 27, 2025):

how I fix it :

Admin panel -> Enable API Keys -> ON (... again)

Admin panel -> Users -> Groups -> [my group name] -> Permissions -> API Keys -> ON

<!-- gh-comment-id:3586854781 --> @R-omk commented on GitHub (Nov 27, 2025): how I fix it : Admin panel -> Enable API Keys -> ON (... again) Admin panel -> Users -> Groups -> [my group name] -> Permissions -> API Keys -> ON
GiteaMirror commented 2026-05-13 05:52:53 -05:00
Author
Owner
Copy Link

@oboeglen commented on GitHub (Nov 27, 2025):

Amazing ! Thanks a lot !

how I fix it :

Admin panel -> Enable API Keys -> ON (... again)

Admin panel -> Users -> Groups -> [my group name] -> Permissions -> API Keys -> ON

<!-- gh-comment-id:3586861659 --> @oboeglen commented on GitHub (Nov 27, 2025): Amazing ! Thanks a lot ! > how I fix it : > > Admin panel -> Enable API Keys -> ON (... again) > > Admin panel -> Users -> Groups -> [my group name] -> Permissions -> API Keys -> ON > >
GiteaMirror commented 2026-05-13 05:52:55 -05:00
Author
Owner
Copy Link

@Classic298 commented on GitHub (Nov 27, 2025):

P L E A S E check for duplicate issues and also read the changelog before updating.

<!-- gh-comment-id:3586965017 --> @Classic298 commented on GitHub (Nov 27, 2025): P L E A S E check for duplicate issues and also read the changelog before updating.
GiteaMirror commented 2026-05-13 05:52:55 -05:00
Author
Owner
Copy Link

@gaby commented on GitHub (Dec 6, 2025):

@Classic298 If you don't have groups, API keys never show up again.

The "admin" user is treated different than a "user". So the default perms do not apply to it.

This is a bug.

<!-- gh-comment-id:3620414405 --> @gaby commented on GitHub (Dec 6, 2025): @Classic298 If you don't have groups, API keys never show up again. The "admin" user is treated different than a "user". So the default perms do not apply to it. This is a bug.
GiteaMirror commented 2026-05-13 05:52:57 -05:00
Author
Owner
Copy Link

@Classic298 commented on GitHub (Dec 6, 2025):

@gaby you need to enable the api keys permission in the default user role permission (and of course globally too)

Where is the bug?

<!-- gh-comment-id:3620419364 --> @Classic298 commented on GitHub (Dec 6, 2025): @gaby you need to enable the api keys permission in the default user role permission (and of course globally too) Where is the bug?
GiteaMirror commented 2026-05-13 05:52:57 -05:00
Author
Owner
Copy Link

@gaby commented on GitHub (Dec 6, 2025):

@Classic298 created #19787 default user perms do NOT apply to admins.

<!-- gh-comment-id:3620420453 --> @gaby commented on GitHub (Dec 6, 2025): @Classic298 created #19787 default user perms do NOT apply to admins.
GiteaMirror commented 2026-05-13 05:52:58 -05:00
Author
Owner
Copy Link

@Classic298 commented on GitHub (Dec 6, 2025):

@gaby some default user role perms DO apply to admins, like the api keys feature. To allow for fine granulared permission configuration.

Simply create a group, add the admins to it that should have that permission and enable the api keys permission

Sharing to groups was recently also revamped to make it necessary to specifically add admins to groups if the enable admin bypass is disabled

<!-- gh-comment-id:3620423993 --> @Classic298 commented on GitHub (Dec 6, 2025): @gaby some default user role perms DO apply to admins, like the api keys feature. To allow for fine granulared permission configuration. Simply create a group, add the admins to it that should have that permission and enable the api keys permission Sharing to groups was recently also revamped to make it necessary to specifically add admins to groups if the enable admin bypass is disabled
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#73525
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?