mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-03-02 22:57:18 -05:00
Manager role can't move entries to other collection #1217
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
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#1217
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 @IgnazNepumuk on GitHub (Feb 4, 2022).
Subject of the issue
User with 'manager' role, can't edit the entries associated collection. If the user tries to edit the collection (click on the gear, collections) following message appears:
"Collections
There are no collections to list. "
The entry is part of a collection, the user rights are set to "this user can access and modify all items."
Deployment environment
Install method: Docker image
Clients used: web vault
Reverse proxy and version:
MySQL/MariaDB or PostgreSQL version:
Other relevant details:
Steps to reproduce
Expected behaviour
Users with Manager role and access control "this user can access and modify all items." should be able to edit every entry within the organization and be able to move an entry from one collection to another.
Actual behaviour
Users with Manager role and access control "this user can access and modify all items.", are unable to move entries from one collection within the same organization to another collection within the same organization
Troubleshooting data
@BlackDex commented on GitHub (Feb 5, 2022):
This seems to be either by design or a bug in the web vault, which is not maintained by Vaultwarden.
I can reproduce the same on vault.bitwarden.com
@jimmyparr commented on GitHub (Feb 14, 2022):
just run this version of docker
not affected by the bug
docker pull vaultwarden/server:1.23.0