mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2025-12-10 17:23:04 +03:00
Assigned Collections not visible under Members #263
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 @piitch 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
Config:
Vaultwarden Build Version
1.32.7
Deployment method
Official Container Image
Custom deployment method
No response
Reverse Proxy
NPM v2.12.2
Host/Server Operating System
Linux
Operating System Version
Ubuntu 24.04
Clients
Web Vault
Client Version
No response
Steps To Reproduce
Expected Result
List of Collections where the User is assigned to
Actual Result
No Collections shown
Logs
Screenshots or Videos
No response
Additional Context
No response
@piitch commented on GitHub:
Thanks a lot for the fast replies, i think we can close this bug, cause it never was one ;)
@BlackDex commented on GitHub:
Indeed.
And probably in the
testingtagged containers it will probably be fixed.@piitch commented on GitHub:
The User which i wanted to check is an Admin, ah okay I see. When i check an admins assigned collections im getting no info because an admin could assign every collection to himself?
Thanks alot for the fast reply
@BlackDex commented on GitHub:
If this is an owner or admin with access-all, that is normal.
Also, tryout the
testingtagged images which were build yesterday, those use a newer web-vault version and have several fixes regarding collections and manage roles.I do suggest to create a backup of the database just in case, but creating regular backups is always wise.