mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-03-12 01:45:56 -05:00
Organisation User with "Can Manage" permissions cannot access "Edit Access" of Collection #5842
Reference in New Issue
Block a user
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?
Originally created by @yurix73 on GitHub (Feb 18, 2025).
Originally assigned to: @BlackDex on GitHub.
Vaultwarden Support String
Your environment (Generated via diagnostics page)
Config & Details (Generated via diagnostics page)
Show Config & Details
Environment settings which are overridden: ADMIN_TOKEN
Failed HTTP Checks:
Config:
Vaultwarden Build Version
v1.33.2
Deployment method
Official Container Image
Custom deployment method
Vaultwarden behind Nginx Reverse Proxy
Reverse Proxy
nginx/1.22.1
Host/Server Operating System
Linux
Operating System Version
Debian 12 (bookworm)
Clients
Web Vault
Client Version
Chromium Version 133.0.6943.53 (Official Build) (64-bit)
Steps To Reproduce
Expected Result
Because this user has "Can Manage" Permissions I should be able see a Modal to edit who has access to selected Collection.
Actual Result
I get redirected to the login page
Logs
Screenshots or Videos
Additional Context
No response
@BlackDex commented on GitHub (Feb 18, 2025):
We currently do not allow users to be able to manage.
We might need to block that right in some way, but the other issue is, that users then are not able to delete items from collections anymore.
We currently only allow managers or higher to actually manage a collection, and not users.
So, if you want someone to be able to manage specific collections, change the role to
customfor now.@stefan0xC commented on GitHub (Feb 19, 2025):
While checking the changes for the new
web-v2025.2.1I noticed8c339ead19so it seems like we should make possible for Managers@BlackDex commented on GitHub (Feb 19, 2025):
Isn't that more for flexible collections? We do not (yet) support those.
Else we should some how instead of logging them out, provide a Vaultwarden specific warning maybe?
Like,
Vaultwarden does not support this for normal user accountsor something similar?Or, someone would like to fix the whole manage throughout the whole code. But that is a mess from my point of view, mainly because of how collections and groups are linked and the queries which need to be done. I still didn't found the time (or drive) yet to try and fix and refactor that. Also because the SSO PR might have effect on it, and i want to make some other database handling changes before trying to refactor that part of the code if I will do it my self (Doesn't prevent anybody else though).
@stefan0xC commented on GitHub (Feb 20, 2025):
Oh, sorry for the confusion I think I answered to the wrong issue #5592
@BlackDex commented on GitHub (May 19, 2025):
I Think this should be solved via the #5798 PR, i can not reproduce this there.
Also, keep in mind that a Child Collection (or nested collection as they are called at Bitwarden) have there own rights, and nothing is inherited from the parent!