This would be a super useful feature in the CSP/MSP space. We regularly send sensitive information back and forth with clients and it would be very useful to have the capability for them to simply upload or send passwords/files/text to us via request or email.
1 Like
Hello,
Could you please add secure drop for files?
For example:
Alice is a Bitwarden premium user with access to Bitwarden Send.
Bob is not a Bitwarden user.
Alice would like to request documents containing sensitive information from Bob without sending them via email. Alice creates a drop request with a passcode and shares the link with Bob.
Bob can upload a document by clicking on the link, typing in the password, and hitting upload.
Then, Alice should get an email notification that the documents are available.
An example of such a feature is DoD Safe
https://safe.apps.mil/
I just realize this has been discuss albeit differently
3 Likes
I think the spirit of this request though is that you can request information and files securely from others without the other party needing an account.
1 Like
This will be a great addition to BitWarden. hope will receive it soon. Especially as MSPs we will work with clients and there are important and secure information to be shared from the client to us. Like credentials, infrastructure details, etc. In this case, this will be an important feature and great value addition.
Hey @bw-admin, I’m really pleased with the attention this feature request has gotten from the community over the last year. With the roadmap about to be updated for H2, how many votes on this request would you need to get the request added?
There really isn’t any specific requirements, i.e. a feature request gets X-amount of votes and it will be added.
Feature request topics help to show support from the community for a specific feature as well as allow for those members to voice their use case.
Obviously the more popular a feature request is with more votes will be something that the Bitwarden team will look at, but it is not the only thing.
Several factors I would imagine such as business use-case, easy of development, impact to security, and many others play into whether or not a feature is developed and added by the team at Bitwarden.
Though some may become preturbed that the developers are not working to release a specific feature that they might wish for, the team is constantly hard at work to release new and exciting things.
I personally have seen several QoL improvements made over the last year or two and can’t wait to see what the future holds. 
This is a great idea and the process is exactly what I wanted to suggest.
1 Like
This would indeed be a great BitWarden feature, and make life easier.
Is there a feature request for the opposite - the ability to send a link to an existent password entry in the vault to a non-bitwarden user?
Send seems entirely unequipped for this, since I have to manually copy crdentials into it, so if those credentials update, they aren’t reflected in the send, and I don’t want to invite people to my organization if I only want to share one password temporarily with them.
1 Like
@rokejulianlockhart Yes, improved credential sharing is in planning. The relevant Feature Request thread is here:
Not sure to what extent this will support sharing with individuals who are not Bitwarden users, but if you review the linked thread, perhaps you will find some relevant discussion there.
1 Like
934 days since posting the original request, 4.8k views, 21 replies, 40 likes – is there any way we can get this feature into the roadmap @cksapp?
3 Likes
Similar to the “Send” feature, where you can send your password to someone who has that link, I would like to have a similar feature that allows you to generate a link that external users can open and enter their password there so they can securely share their passwords with me as a Bitwarden user.
2 Likes
Has that post been deleted, @grb? It sends me to
It seems the above link to the “Vault Item Sharing” feature request was corrupted somehow. It should work now, or you can try this one:
Just bumping this to add a +1, my organisation too would love this feature.
I will add one of my votes to this – from a private perspective when dealing with businesses such as accounting or other financial.
Some of them are somewhat cavalier about dispensing one’s financial information across the internet. I know I can train some to wait for a secure link before sending to me, if the feature were available. Even where they have a supposedly secure 3rd party portal, there is a lack of diligence in its use.
Also, with non-BW-using scattered family, when exchanging certain information I would prefer BW over Wire so I do not have to remember to delete for all users, or get them to do so after they have sent.
It doesn’t look like Bitwarden see this as a viable feature so I’d love to hear from others what platform they use to securely receive files?
I’m seeing in this thread SendSafely recommended but keen to hear more suggestions.
Given the four comments I read from Bitwarden in this thread, I am not sure why you think they do not “see this as a viable feature” rather than something not on their roadmap yet. It has only 52 votes at time of writing, far fewer than some other requests not yet implemented. Encourage more votes, or help to improve the business case.
SendSafely seems to be another Send, not providing the functionality I believe is requested here. We currently use Wire for files as well as messages, and in some cases encrypt files using either a shared secret or which are sent alongside an OTP-encrypted password for it (I wrote a manager for that). The potential virtues I see in this request are process simplification for inexperienced parties, and no maintenance. I need to think more about whether I can map a realisable process.
Apologies if you misunderstood me – I understand Bitwarden has priorities and a roadmap, the devs aren’t just sitting there with nothing to do.
But clearly this isn’t a viable feature as over 3 years on it’s not on the public roadmap. As you put it, you could also say that the business case hasn’t met the threshold yet – it’s not a viable feature, at least at this time.
From a user’s point of view, I needed a solution 6 years ago, and it’s time for me to iterate the clunky request process I have now and use a SaaS solution to get this done. So farm SendSafely looks to be the best option but I’m super open to other recommendations (your process sounds interesting, but I’d be cautious about taking on the compliance risk).
No problem, especially if it was my misunderstanding :).
It is certainly a viable feature. I had at the back of mind that there is another request with over 500 votes (including mine) not yet implemented, others six years old, so I guess I am already conditioned to some viable changes being slow.
The process I mentioned is strictly family-private so compliance is not a problem nor is it publicly useful. Your need appears to be from business. I understand that immediacy.