github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-07 03:18:23 -05:00
Code Issues 1.3k Packages Projects Releases 126 Wiki Activity

[GH-ISSUE #17144] issue: Adding users to a group via the intended API endpoint does not work #33713

New Issue
Closed
opened 2026-04-25 07:36:01 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-25 07:36:01 -05:00
Owner
Copy Link

Originally created by @DirkRemmers on GitHub (Sep 2, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/17144

Check Existing Issues

  • I have searched the existing issues and discussions.
  • I am using the latest version of Open WebUI.

Installation Method

Docker

Open WebUI Version

v0.6.22

Ollama Version (if applicable)

No response

Operating System

Debian

Browser (if applicable)

No response

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

When using the following API endpoint: POST /api/v1/groups/id/{group_id}/users/add, the user that is specified in the data should be added to the group.

Actual Behavior

Instead, when I use the following api endpoint: POST /api/v1/groups/id/{group_id}/users/add, the user that is specified in the data is not added to the group.

Steps to Reproduce

To reproduce:

  1. get a user from the database (GET/api/v1/users/) and get the id (user_id)
  2. get a group from the database (GET /api/v1/groups/) and get the id (group_id)
  3. try to add the user the group to the knowledge collection (POST /api/v1/groups/id/{group_id}/users/add with data = {"user_ids"=[user_id]})
  4. get the group again (GET /api/v1/groups/id/{group_id}) and see that the user is not added

Logs & Screenshots

Additional Information

I don't believe this is the intended behaviour, so I guess this should be fixed?

For anyone experiencing an issue here as well, there is method that does work. Instead of using the dedicated endpoint (POST /api/v1/groups/id/{group_id}/users/add), you can instead use the /api/v1/groups/id/{group_id}/update" endpoint. In here, you can add the user_id to the existing users_ids of the group, and pass that to the data required to update the group.
WARNING: you have to define ALL users with this method, since it will use data["user_ids"] as the new "source of truth"

Cheers,
Dirk

Originally created by @DirkRemmers on GitHub (Sep 2, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/17144 ### Check Existing Issues - [x] I have searched the existing issues and discussions. - [x] I am using the latest version of Open WebUI. ### Installation Method Docker ### Open WebUI Version v0.6.22 ### Ollama Version (if applicable) _No response_ ### Operating System Debian ### Browser (if applicable) _No response_ ### 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 When using the following API endpoint: `POST /api/v1/groups/id/{group_id}/users/add`, the user that is specified in the `data` should be added to the group. ### Actual Behavior Instead, when I use the following api endpoint: `POST /api/v1/groups/id/{group_id}/users/add`, the user that is specified in the `data` is not added to the group. ### Steps to Reproduce To reproduce: 1. get a user from the database (`GET/api/v1/users/`) and get the id (user_id) 2. get a group from the database (`GET /api/v1/groups/`) and get the id (group_id) 3. try to add the user the group to the knowledge collection (`POST /api/v1/groups/id/{group_id}/users/add` with `data = {"user_ids"=[user_id]}`) 4. get the group again (`GET /api/v1/groups/id/{group_id}`) and see that the user is not added ### Logs & Screenshots - ### Additional Information I don't believe this is the intended behaviour, so I guess this should be fixed? For anyone experiencing an issue here as well, there is method that does work. Instead of using the dedicated endpoint (`POST /api/v1/groups/id/{group_id}/users/add`), you can instead use the `/api/v1/groups/id/{group_id}/update"` endpoint. In here, you can add the user_id to the existing users_ids of the group, and pass that to the `data` required to update the group. WARNING: you have to define ALL users with this method, since it will use `data["user_ids"]` as the new "source of truth" Cheers, Dirk
GiteaMirror added the bug label 2026-04-25 07:36:01 -05:00
GiteaMirror commented 2026-04-25 07:36:03 -05:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Sep 2, 2025):

0.6.22 is not the latest version.

<!-- gh-comment-id:3246202159 --> @tjbck commented on GitHub (Sep 2, 2025): 0.6.22 is not the latest version.
GiteaMirror commented 2026-04-25 07:36:03 -05:00
Author
Owner
Copy Link

@DirkRemmers commented on GitHub (Sep 3, 2025):

Ah appologies for this one! Thanks for the quick response!

<!-- gh-comment-id:3247949339 --> @DirkRemmers commented on GitHub (Sep 3, 2025): Ah appologies for this one! Thanks for the quick response!
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#33713
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?