mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2025-12-11 09:13:02 +03:00
Manager Role can create a (nest) collection outside from the one he is assigned #309
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 @joao-paixao on GitHub.
Vaultwarden Support String
Your environment (Generated via diagnostics page)
Config (Generated via diagnostics page)
Show Running Config
Environment settings which are overridden: DOMAIN, SIGNUPS_ALLOWED, ADMIN_TOKEN
Vaultwarden Build Version
1.32.5
Deployment method
Official Container Image
Custom deployment method
No response
Reverse Proxy
no
Host/Server Operating System
Linux
Operating System Version
Ubuntu 24.04.1 LTS
Clients
Web Vault
Client Version
2024.6.2c
Steps To Reproduce
Create a user with manager role.
Give the user access to a collection.
Login as manager user
Create a new collection (a nested collection)
Go to
Nest Collection UnderSelect
No collectionand ClickSaveExpected Result
Manager is assign to collection
SubCollection 1, he should only be allowed to create a new collection under the collection assigned.Vault (Can't Create)
├── Collection 1 (Can't create)
│ └── SubCollection 1 (Can create)
├── Collection 2 (Can't create)
└── Unassigned
Actual Result
Manager is assign to collection
SubCollection 1, he is allowed to create a new collection not under the collection assigned.Vault (Can Create)
├── Collection 1 (Can't create)
│ └── SubCollection 1 (Can create)
├── Collection 2 (Can't create)
└── Unassigned
Logs
No response
Screenshots or Videos
No response
Additional Context
No response
@BlackDex commented on GitHub:
Again, that seems like a client side (Bitwarden managed) item. Which is not under this projects control. And since we can't see a difference between nested or none nested collections we can't fix that on the server side.
@joao-paixao commented on GitHub:
If i have a user with
Managerrole and assign to the collectionDevelopment.What i would expect is that only the
Development(or other collection assigned to him) would appear as an option in theNest Collection Underoption.But in fact he can simply self-assign to a new collection, which is fine, only if that new collection would remain nested under one of the assigned.
Example:

It would be fine to create a new collection under
DevelopmentorOtherCollection.But i don't understand why it exists the option
No collection, making then possible to create a new collection NOT under one of the assigned to him.@joao-paixao commented on GitHub:
Ok, since this is a situation that cannot be controlled by you, I have nothing more to add.
Thank you and you can close the issue.
@BlackDex commented on GitHub:
I'm not totally sure what you mean here, if you could provide a more detailed steps to follow, maybe with some screenshots, that might help to clarify it
Vaultwarden can't see or know if a collection is nested or not.
That information is not shared or visible to the server.
For Vaultwarden it is just another collection with its own uuid, name and rights.
A manager (without access all directly or via group) can only access assigned collections and, as far as i know only nest under an assigned collection.
If that currently is not the case, then it probably is a bug in the client, and not something we can fix on the server side as we do not know if it is nested or not.
I do have a PR open to update the web-vault to a newer version which might solve your issue.