1
0
mirror of https://github.com/bitwarden/help synced 2025-12-06 00:03:30 +00:00
Files
help/_articles/send/about-send.md
fred_the_tech_writer 535ea72847 Release Updates (#474)
* Send Staging (#447)

* - js for in-page tabs
- send category early drafts of articles
- send images

* fix scrolling on tab

* send web vault

* mobile image

* redone 'receive send' article

* send from browser ext & mobile

* send work

* improvements to 'about'

* send additions

* so much send

* lotsa send

* all send all the time

* ain't nothin but a send thang

* cli

* send cli

* simple cli sends in /create-send/

* simple disable & delete in /send-lifespan/

* send desktop screenshots

* send final cleanup

* cli final cleanup

* send edits

* fix

* send final touches

* fixed links & non-send updates

* new import message documentation, several import articles condensed to use tabs, U2F support for Edge, excluded domains article, remove in innacurate note on emergency accesss

* Firefox Attachment Workflow + Date Picker for custom timestamps

* safari attach file Send req

* excluded domains addition

* fix tab titles

* release notes

* unlock articles

* link to status feed

* small typos

* test

* updated release notes

* lastpass article form fill rewrites

* import to org & personal clarifications

* send self-hosting, safari web extension edits, and release notes
2021-03-11 11:58:16 -05:00

3.3 KiB

layout, title, categories, featured, popular, tags, order
layout title categories featured popular tags order
article About Send
send
true false
bitwarden send
send
about send
ephemeral sharing
01

What is Send?

Bitwarden Send is a secure and ephemeral way to transmit sensitive information to anyone. Sends can include plaintext or file attachments up to 100 MB. Every Send is assigned a randomly generated and secure link, which can be [shared with anyone]({% link _articles/send/receive-send.md %}) (including those who do not have Bitwarden accounts) via text, email, or whatever communication channel you prefer. Every Send is:

  • End-to-end Encrypted: Data in a Send is encrypted on creation, and only decrypted when a recipient opens the Send link. The contents of a Send are stored encrypted in Bitwarden systems, just like a traditional Vault item. The link generated for each send doesn't contain any data related to the Send's contents, so it's safe to share over intermediary communications services without exposing information to Bitwarden or any used intermediary services.

  • Dynamically Ephemeral: Sends are designed for ephemeral sharing, so every [Send that you create]({% link _articles/send/create-send.md %}) will have a specified [lifespan]({% link _articles/send/send-lifespan.md %}) (max 30 days) that can be configured using pre-set options or a custom timestamp for down-to-the-minute specification. When its deletion date is reached, the Send and its contents will be completely purged from Bitwarden systems. Using additional options like Expiration Date and Maximum Access Count, you can ensure that access to recipients is terminated according to your needs.

  • Customizably Private: Protect the contents of your Send by optionally configuring a password for access so that no unintended recipients can see the contained information. For text Sends, you can also optionally require users to toggle visibility to prevent exposure to unintentional onlookers.

The Send View

Sends are created, edited, managed, and deleted from the Send view in any Bitwarden application. The Send view can be accessed from the global application navigation, for example in the Web Vault:

{% image /send/send-webvault.png Send in the Web Vault %}

Using Send

Using Bitwarden Send is a simple two-step process:

  1. [Create your Send]({% link _articles/send/create-send.md %}), setting whichever [lifespan options]({% link _articles/send/send-lifespan.md %}) and [privacy options]({% link _articles/send/send-privacy.md %}) are required to fit your sharing needs.
  2. Share the Send link with the [intended recipients]({% link _articles/send/receive-send.md %}), using whatever communication channel you prefer.

As the Sender, we recommend that you keep track of your Send's [configured lifespan]({% link _articles/send/send-lifespan.md %}). To make that as easy as possible, Sends in your Send view will display a set of status icons whenever a lifespan event (for example, expiration) has occurred.