@jshapiro Welcome to the forum!
As your post falls under the general request for a different / more simple mechanism of “Vault Item Sharing” than the current one, I moved your post into this corresponding feature request.
Hey, since Bitwarden Sends are often used to share credentials with other parties that don’t have Bitwarden, it would be nice if the frontend would allow to create a Bitwarden Send directly from an entry / credential, eliminating the need to go back and forth copy and pasting username, password, uri - by adding an option like „Share with Bitwarden Send“ next to duplicate, delete, …
Since this is just a „dumb“ UI extension it shouldn’t be too hard to implement.
There seems to have been such a feature request before, but its been merged and the merged one is no longer available (Add Bitwarden Sent to Credentials Sharing options)
@activivan Welcome to the forum!
I moved your post into the existing feature request on the same topic. (you can vote on feature requests when you reach the next “trust level” – just spend some time on the forum…)
1 Like
An option to easily share a password from a vault item with one click via a link would be great.
I usually need to copy the credentials into the text field inside Bitwarden to send them, which is a bit of manual work that I think could be automated. Also, adding an option to share multiple items at once would be extremely convenient.
@NigelXheri I moved your post into the existing feature request on the same topic.
Is this feature being worked on? Where is it on the road map after so many years?
@passabilities I think this is the latest update.
We really need something that makes it easier to send items in our vault with persons who aren’t part of our families or organizations. I think if the recipient doesn’t have a Bitwarden account on their own - then the current one-off clunky send file or text is ok.
However, if both parties have a Bitwarden account, then it would be a nice feature of those that are at least paying customers to be able to send items (login, card, notes, etc.) to that user securely and far easier than is now available.
3 Likes
Or maybe an option to “send item to Bitwarden Send” with all the item information of the item. In Bitwarden Send we can remove all the information we don’t want to send, fix the formatting, set the options, etc. before sharing it.
1 Like
We definitelly need a feature that would allow to send directly from an item context menu
I don’t care how it’s done, if it’s like @linuxero said (all the text then erase what we don’t want) or like @spork (in the copy dropdown, like a “send password”, “send username” or “send all fields”), we need this.
I think the main problem for bitwarden team is to include “send” feature within bitwarden extension, because right now these are two different things if I recall correctly.
After doing that, it would be pretty easy to send a vault item to the send feature.
It would be helpful for users to be able to share passwords/credentials directly with each other. Currently the only ways to do this are by sending via SecureSend and the receiver save the credentials manually in their vault OR creating a collection with only those two people. The former isn’t a very “closed-loop” clean way to do it and the latter would potentially require the creation and management of hundred of collections.
1 Like
@zac.henderson Welcome to the forum!
Though you posted in the “Ask the Community” section of the forum, as your post already sounded like a request, I moved it into the existing feature request on the same topic.
Add a password send option in password at my vault. This is for security purposes and convenience for user. User want to share password must copy password to send and share it, make a risk to clipboard attack and complex
1 Like
Does this existing request match what you are suggesting? If so, we can move your vote to it.
This would be the ticket!
It’s silly we can’t just right click send 
2 Likes
Summary
Add a “Share via Send” action to the vault item context menu that opens the Send composer pre-filled with the item’s credentials. Pure UI-layer feature on top of the existing Send primitive: no new server endpoints, no new crypto, no new
permission model.
Problem
Sharing a single credential one-time with someone outside your Org is friction-heavy today:
- Organizations/Collections are the wrong tool for a one-time share with a non-Bitwarden user (forces collection creation, requires the recipient to be a Bitwarden member, and pollutes the org structure).
- Send is the right tool. It’s encrypted, ephemeral, and the recipient doesn’t need an account, but using it for a credential currently requires the user to manually copy each field (username, password, URL, notes) into a text Send.
That’s tedious and error-prone, and people end up sending plaintext over Slack/email instead.
This gap has been raised repeatedly: Send a password from vault, and several merged/closed threads with similar asks. None propose a tightly-scoped UI-only solution.
Proposed UX
- On a vault item’s detail or context menu, add a “Share via Send” action (alongside Edit, Clone, Move to Org, etc.).
- Clicking it opens the existing Send composer pre-filled:
- Type: Text
- Name: (editable)
- Content: structured plaintext with username, password, URI, and notes (configurable; see below)
- Defaults: Maximum access count = 1, Deletion date = 1 day, password-protect prompt enabled
- User reviews, optionally adds a password or adjusts expiration, clicks Save, and gets the standard Send link to share out-of-band.
No data leaves the client until the user explicitly creates the Send.
Security defaults (intentionally conservative)
- TOTP secret excluded by default. Sharing a TOTP seed grants ongoing access via the regenerating code, which is qualitatively different from sharing a password. Users would have to opt in per-share.
- Custom fields excluded by default. Same reasoning: fields may contain backup codes, recovery keys, etc.
- Single-view + 1-day expiration as default Send settings (overridable per-share).
- Password protection prompt surfaced (not forced) on save.
- Optionally a Server-side Org policy: “Disable Share via Send for org-owned items”. Gives admins an opt-out.
Scope boundaries (what this is NOT)
- Not a replacement for Vault Item Sharing. That ask is about persistent shared state between two Bitwarden accounts. This is one-time, ephemeral, recipient-agnostic.
- Not a new sharing primitive. It’s a pre-fill UX on top of the Send composer that already exists.
- No server changes. Send API is already public; this is purely client-side composition in bitwarden/clients.
Open questions for staff
- Is the security posture acceptable as proposed, or are there objections to credentials flowing into Send via UI affordance vs. manual copy/paste? (The data path is identical; the only difference is convenience.)
- Should this be gated behind an existing policy, a new policy, or no policy?
- Is there appetite for a community PR on this if scope and defaults are agreed?
Happy to scope a draft PR in bitwarden/clients if there’s interest, but per CONTRIBUTING I’m flagging the proposal here first.
@babyhuey Welcome to the forum!
I’ve moved your post into the existing feature request on the same topic.
Just FYI, this is a Community forum. Your post may or may not be read by a Bitwarden employee. – If you want to contribute, the right place to start is: How to contribute to the Bitwarden codebase · bitwarden · Discussion #4723 · GitHub (and your “questions for staff” are also probably best discussed on GitHub directly)