mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-26 01:35:54 +03:00
[GH-ISSUE #6121] Cannot save Access to collections to an Admin user 1.34.3 #2348
Labels
No labels
SSO
Third party
better for forum
bug
bug
documentation
duplicate
enhancement
future Vault
future Vault
future Vault
good first issue
help wanted
low priority
notes
pull-request
question
troubleshooting
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/vaultwarden#2348
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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 @DaveSophoServices on GitHub (Jul 31, 2025).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/6121
Prerequisites
Vaultwarden Support String
Config & Details (Generated via diagnostics page)
Show Config & Details
Environment settings which are overridden: DOMAIN, SIGNUPS_ALLOWED, ORG_CREATION_USERS, ADMIN_TOKEN
Config:
Vaultwarden Build Version
1.34.3
Deployment method
Official Container Image
Custom deployment method
No response
Reverse Proxy
nginx 1.22.1
Host/Server Operating System
Linux
Operating System Version
Debian GNU/Linux 12
Clients
Browser Extension, Web Vault
Client Version
2025.7.0
Steps To Reproduce
Expected Result
User should be saved with access to that collection.
Actual Result
the collection is not associated with that user. It doesn't appear in the line with the user details.
Clicking the user again shows the user is not associated with the collection
Logs
Screenshots or Videos
No response
Additional Context
This was noticed a few weeks ago, and we investigated it today.
@BlackDex commented on GitHub (Jul 31, 2025):
Admins and owners have access by default to all collections, and therefore not stored like that.
Only managers and users are currently stored.
@DaveSophoServices commented on GitHub (Jul 31, 2025):
That makes sense, however, for the web browser plugin, it now shows all relevant passwords from all collections as potentials for auto-fill, whereas it used to just show the collections that were assigned to the particular admin. Is this a regular use case - or do people generally run an admin user and a regular user (like not running as root all the time)?
@BlackDex commented on GitHub (Jul 31, 2025):
We do not yet have this fine grained control yet. A lot of changes need to be done.
Regarding admin and user and how people use it,i have no clue.
@DaveSophoServices commented on GitHub (Jul 31, 2025):
Thank you @BlackDex, "it's a feature, not a bug" :-)