mirror of
https://github.com/open-webui/open-webui.git
synced 2026-08-01 03:17:20 -05:00
[GH-ISSUE #22491] issue: Open Terminal, Edit Terminal Connection, Add Access, not showing logged in user #106718
Reference in New Issue
Block a user
Originally created by @toralux on GitHub (Mar 9, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/22491
Check Existing Issues
Installation Method
Docker
Open WebUI Version
v0.8.10
Ollama Version (if applicable)
No response
Operating System
Docker container
Browser (if applicable)
Chrome 145
Confirmation
README.md.Expected Behavior
In "Admin Panel, Integrations, Open Terminal, Edit Terminal Connection, Add Access", when I search for "
Anders Johansen" the dialog is expected to show the two registered users matching that search pattern - including the currently logged in user "Tor Anders Johansen", but only one of these users show up in the Web UI dialog as if the currently logged in user is filtered away.Actual Behavior
Steps to Reproduce
Inn "Add User", search for "
Anders Johansen" (matching my list of registered users).What Web UI in Chrome shows
UI (showing 1 user only, one expected user is missing):
What REST-api results in Chrome shows
REST API (returning 2 users as expected)
HTTP GET api/v1/users/search?page=1&query=anders+johansen&order_by=name&direction=asc
Logs & Screenshots
Screenshot of the UI and API-response together
Two users from REST-api.tiff
Additional Information
Could it be because the two users share the exact same display name? (One is the first/initial admin user, the second is later on registered using Oauth 2.0 and an identity provider, and both users share the same display name).
@toralux commented on GitHub (Mar 9, 2026):
I have done some investigation. It looks like the problem is that the currently logged in user (Tor Anders Johansen) is filtered out from the list, cannot select the logged in user.
The root cause is this line in MemberSelector.svelte:
$_user is the Svelte store for the currently logged-in user (imported from $lib/stores).
The {#if user?.id !== $_user?.id} condition explicitly excludes the logged-in user from the search results list.
This is a common and intentional design choice in many apps: you typically don't let someone grant access to themselves (since they already have it implicitly as owner/creator), or to avoid self-sharing loops in permissions.
Is this by design or is this a bug? I would expect that I can select the currently logged in user as well?
@tjbck commented on GitHub (Mar 11, 2026):
Addressed in dev!