* initial commit
* adding quotes for the array error
* Create Gemfile
* Create Gemfile.lock
* add .nvmrc and .node-version
* removed /article from URL
* update links to work with netlify
* more fixed links
* link fixes
* update bad links
* Update netlify.toml
toml test for redirects
* article redirect
* link fixes
* Update index.html
* Update netlify.toml
* Update _config.yml
* Update netlify.toml
* Update netlify.toml
* Update netlify.toml
* Update netlify.toml
* Update netlify.toml
* add article back into URL for launch
* Update netlify.toml
* Update netlify.toml
* add order to categories front matter
* Update netlify.toml
* update
* sidemenu update
* Revert "sidemenu update"
This reverts commit 5441c3d35c.
* update order prop
* Navbar updates per Gary and compiler warnings
* font/style tweaks
* Update sidebar.html
* Stage Release Documentation (#739)
* initial drafts
* rewrite Custom Fields article to prioritize new context-menu option & better organize ancillary information
* edit
* edit
* Custom Field Context Menu & CAPTCHA item in release notes
* SSO relink event
* update rn
* small edits
* improve release notes titles
* fix side menu
* Edits courtest of mportune!
* update order
* link fixes
* link cleanup
* image updates and a link
* fix trailing slash
Co-authored-by: DanHillesheim <79476558+DanHillesheim@users.noreply.github.com>
3.5 KiB
layout, title, categories, featured, popular, tags, order
| layout | title | categories | featured | popular | tags | order | |||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| article | About Send |
|
true | false |
|
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 500 MB (100 MB if creating from Mobile). Every Send is assigned a randomly generated and secure link, which can be shared with anyone (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 will have a specified lifespan (max 31 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 or hiding your email address from recipients. 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:
- Create your Send, setting whichever lifespan options and privacy options are required to fit your sharing needs.Create your Send
- Share the Send link with the intended recipients, using whatever communication channel you prefer.
As the Sender, we recommend that you keep track of your Send's configured lifespan. 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.