TL/DR…
So, 7 years later after the first post, and still Vault Item sharing (username/Password) with others is still the same cumbersome process of creating a collection, transferring ownership, inviting user…etc. What is it going to take to get Bitwarden to completely revamp the vault item sharing process and making it a one click option like the Send option? This is soooo cumbersome to try and teach to a user! My teaching staff doesn’t use it, and they write down logins to give substitutes because this process is too complicated.
Is this even on the Bitwarden radar for work? If so, When…maybe before the eighth year of this post?
In the spirit of transparency, this item is not being actively developed. There is a prerequisite engineering effort around item-level encryption (which would enable vault item sharing), which is still in progress and requires careful migration of self-hosted customers to follow this new encryption scheme. We absolutely see the need as we want to expand our general sharing capabilities, which also includes making it easy to spin up collections when sharing items with one other person. We’ll provide more updates once item-level encryption has completed migration for the entire Bitwarden base and if this work does get picked up.
Given the way the UI for BW is designed, hell, I’d even settle for a “copy username AND password” to clipboard (with some kind of separator character) option so I could at least copy the info, open a standard BW Send and then paste that combo in…
Thanks! We’re looking into making extension actions more consistent and so this would be very natural to include in that design work. Will let you know when we have an update here
Perhaps “all fields” could place a json export to the clipboard for the selected item(s) that could then be pasted/imported back into my vault or another vault.
This may have benefits if the recipient is a Bitwarden user (and if they are aware of the ability to import by pasting JSON- or CSV-formatted text), but for sharing with a non-Bitwarden user, cleaning up the JSON to make it legible would probably be more work than separately copying the username and password and pasting into the Send.
The json export as well as the ability to copy multiple fields could be config options so that those that have zero use for this don’t have to even look at it…
What I would envision as a simple solution would be to have ‘Vault Item’ as an option added to the send tool. So click on send to enter that, and in th selection, have text, file, and ‘Vault Item’ as options, then pop up a item picker to select the vault item to share, and for added security, limit the number of vault items that can be shared to a small number ( like less than 5) so no one can accidentally share every password they have.
+1, having to make an organizations to share entries with 1-2 people is just too much, it is not an organization, we need a better implementation, bitwarden team, please…
all of the alternatives have this separated from “corporate” like features such as organizations
I agree with the proposal. It is often very necessary to share one element with someone and receive all field updates on it. And sometimes it is not a shared folder that is needed, but the ability to share one specific element.
For some reason I’m not able to cast a vote for this feature, but would like to express my support for it. Often I need to send full logins to others and this was a feature in previous password managers I have used. Thanks for the consideration.
You are new forum user and have only spent 2 minutes in the forum (thus far); your voting privileges are not unlocked until your status has been promoted from “new user” to “basic user”, which involves participating in the forum (e.g., by reading topics of interest to you) for a little bit longer.
In some systems, it is necessary to create a temporary password when creating an account. In our old Vault, the admin creates an element as shared it with the user. Afterwards he was disconnecting himself from the element.
This procedure doesn’t need any other service. Just the vault.
It sure would be nice if the Send feature was an option for each password vault record. It would create a new Send based on that record. You could tweak it however you like from there, but using an existing record as the basis for Send would sure streamline the whole process.
