Replies: 2 comments
-
To reproduce: If you delete a collection, the items that were in the collection will be unassigned. Cf. https://bitwarden.com/help/about-collections/#manage-a-collection Regarding the issue itself: I think that's expected behavior now that you only will see the items in assigned collections. That used to be different (that you would see all items with access all in the password manager) but Bitwarden changed it, so they'll only show up in the Admin Console. edit: okay, it's seems they still show up as Owner/Admin. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Vaultwarden Support String
Your environment (Generated via diagnostics page)
Config & Details (Generated via diagnostics page)
Show Config & Details
Environment settings which are overridden: DOMAIN, ADMIN_TOKEN
Config:
Vaultwarden Build Version
v1.32.7
Deployment method
Official Container Image
Custom deployment method
No response
Reverse Proxy
apache
Host/Server Operating System
Linux
Operating System Version
Debian 12.8
Clients
Web Vault, Browser Extension, CLI
Client Version
v2024.12.4
Steps To Reproduce
NOTE - It does not appear to be possible to create this situation - the UI prevents you from removing items from all collections, but if the situation already exists, it appears to present issues.
Expected Result
Since this appears to be a situation that isn't supposed to exist, I'm not sure the best solution. Two possibilities:
A) Highlight the entries/flagged in some way in the web UI as "missing collection"
B) Fix web vault behavior so they do show up
C) Transfer ownership out of organization to the user (this seems questionable from a security policy standpoint)
D) Spontaneously create a "Orphaned Items" collection with no users explicitly granted access - and automatically add any item found without a collection into the orphaned items collection. This option seems like the safest one, since it should result in no effective changes in access/etc.
Actual Result
Something about newer web vaults and clients is resulting in "item in an org missing a collection" being lost/inaccessible in new version of code.
Logs
No response
Screenshots or Videos
No response
Additional Context
Beta Was this translation helpful? Give feedback.
All reactions