Browse Source
* 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 notespull/476/head
fred_the_tech_writer
5 years ago
committed by
GitHub
69 changed files with 1599 additions and 424 deletions
@ -0,0 +1,39 @@
@@ -0,0 +1,39 @@
|
||||
--- |
||||
layout: article |
||||
title: Send FAQs |
||||
categories: [send] |
||||
featured: true |
||||
popular: false |
||||
tags: [] |
||||
order: 08 |
||||
--- |
||||
|
||||
### Q: Why can't I create a file Send? |
||||
|
||||
**A:** Use of text Sends is available to all Bitwarden users, however creation of file Sends is only available for Premium users, including members of a Paid Organization (Families, Teams, or Enterprise). |
||||
|
||||
### Q: Why can't I create a file Send from Firefox or Safari Browser Extension? |
||||
|
||||
**A:** You can! But in order to browse for a file on the Create Send view in a Firefox Browser Extension, you'll need to open the extension in the sidebar or pop out a new window using the popout {% icon fa-external-link fa-rotate-270 %} button: |
||||
|
||||
{% image /send/send-ff-popout.png The popout icon %} |
||||
|
||||
### Q: Why are Sends missing from my Send view? |
||||
|
||||
**A:** By design, Sends are ephemeral. Each created Send has a **maximum lifespan of 30 days**, configurable when you [create a Send]({% link _articles/send/create-send.md %}) or at any time by editing it. When a Send's [Deletion Date]({{site.baseurl}}/article/send-lifespan/#deletion-date) is reached, it will be purged from Bitwarden systems and inaccessible to both the Sender and any recipients. |
||||
|
||||
### Q: What do the icons next to my Sends indicate? |
||||
|
||||
**A:** Icons in the Send view are intended to help you understand the configured [lifespan]({% link _articles/send/send-lifespan.md %}) and [privacy]({% link _articles/send/send-privacy.md %}) options: |
||||
|
||||
|Icon|Meaning| |
||||
|----|-------| |
||||
|{% icon fa-key %}|This Send is [protected by a password]({{site.baseurl}}/article/send-privacy/#send-passwords).| |
||||
|{% icon fa-warning %}|This Send has been [manually disabled]({{site.baseurl}}/article/send-lifespan/#manually-disable-or-delete).| |
||||
|{% icon fa-clock-o %}|This Send has reached it's specified [Expiration Date]({{site.baseurl}}/article/send-lifespan/#expiration-date).| |
||||
|{% icon fa-ban %}|This Send has reached it's specified [Maximum Access Count]({{site.baseurl}}/article/send-lifespan/#maximum-access-count).| |
||||
|{% icon fa-trash %}|This Send has reached it's specified [Deletion Date]({{site.baseurl}}/article/send-lifespan/#deletion-date) and is **Pending Deletion**.| |
||||
|
||||
### Q: Can I prevent members of my Organization from using Send? |
||||
|
||||
**A:** Enterprise Organizations can prevent their members from creating or editing Sends using the [Disable Send Policy]({{site.baseurl}}/article/policies/#disable-send). |
||||
@ -0,0 +1,18 @@
@@ -0,0 +1,18 @@
|
||||
--- |
||||
layout: article |
||||
title: Exclude Domains |
||||
categories: [miscellaneous] |
||||
featured: false |
||||
popular: false |
||||
tags: [] |
||||
--- |
||||
|
||||
Bitwarden Browser Extensions can be configured to exclude (i.e. explicitly not offer to save passwords for) specific domains. When a domain is in the **Excluded Domains** list, Bitwarden won't issue the popup offering to remember an entered password: |
||||
|
||||
{% image /be-offer.png Browser Extension popup offer %} |
||||
|
||||
To configure excluded domains, open the {% icon fa-cogs %} **Settings** tab and select the **Excluded Domains** option: |
||||
|
||||
{% image be-excludeddomains.png Excluded Domains Configuration %} |
||||
|
||||
*Domain* Exclusion does not register "full" URLs, only the domain component. In the above example, `https://github.com/bitwarden/browser` would resolve to `github.com` when saved, meaning that the Browser Extension would explicitly not offer to save credentials for Github. |
||||
@ -0,0 +1,34 @@
@@ -0,0 +1,34 @@
|
||||
--- |
||||
layout: article |
||||
title: About Send |
||||
categories: [send] |
||||
featured: true |
||||
popular: false |
||||
tags: [bitwarden send, send, about send, ephemeral sharing] |
||||
order: 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]({{site.baseurl}}/article/send-lifespan/#expiration-date) and [Maximum Access Count]({{site.baseurl}}/article/send-lifespan/#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]({{site.baseurl}}/article/send-privacy/#send-passwords) for access so that no unintended recipients can see the contained information. For text Sends, you can also optionally [require users to toggle visibility]({{site.baseurl}}/article/send-privacy/#hide-text) 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]({{site.baseurl}}/article/send-faqs/#q-what-do-the-icons-next-to-my-sends-indicate) whenever a lifespan event (for example, expiration) has occurred. |
||||
@ -0,0 +1,235 @@
@@ -0,0 +1,235 @@
|
||||
--- |
||||
layout: article |
||||
title: Create a Send |
||||
categories: [send] |
||||
featured: true |
||||
popular: false |
||||
tags: [bitwarden send, send, create a send, how to, ephemeral sharing] |
||||
order: 02 |
||||
--- |
||||
|
||||
Creation of file Sends is available for Premium users, including members of a Paid Organization (Families, Teams, or Enterprise). Free users may still create text Sends. |
||||
|
||||
Sends can be created and edited from the [Web Vault](https://vault.bitwarden.com){:target="\_blank"} or any Bitwarden client application. Choose the Bitwarden application you want to Send from to get started: |
||||
|
||||
<ul class="nav nav-tabs" id="myTab" role="tablist"> |
||||
<li class="nav-item" role="presentation"> |
||||
<a class="nav-link active" id="wvtab" data-target="#webvault" role="tab" aria-controls="webvault" aria-selected="true">Web Vault</a> |
||||
</li> |
||||
<li class="nav-item" role="presentation"> |
||||
<a class="nav-link" id="betab" data-target="#browserextension" role="tab" aria-controls="browserextension" aria-selected="false">Browser Extension</a> |
||||
</li> |
||||
<li class="nav-item" role="presentation"> |
||||
<a class="nav-link" id="desktab" data-target="#desktop" role="tab" aria-controls="desktop" aria-selected="false">Desktop</a> |
||||
</li> |
||||
<li class="nav-item" role="presentation"> |
||||
<a class="nav-link" id="mobtab" data-target="#mobile" role="tab" aria-controls="mobile" aria-selected="false">Mobile</a> |
||||
</li> |
||||
<li class="nav-item" role="presentation"> |
||||
<a class="nav-link" id="clitab" data-target="#cli" role="tab" aria-controls="cli" aria-selected="false">CLI</a> |
||||
</li> |
||||
</ul> |
||||
<div class="tab-content" id="clientsContent"> |
||||
<div class="tab-pane show active" id="webvault" role="tabpanel" aria-labelledby="wvtab"> |
||||
{% capture web_vault %} |
||||
### Send from the Web Vault |
||||
|
||||
Complete the following steps to create a new Send from the Bitwarden [Web Vault](https://vault.bitwarden.com){:target="\_blank"}: |
||||
|
||||
1. Select **Send** from the top navigation bar. |
||||
|
||||
This view will list all Sends that haven't reached their [deletion date]({{site.baseurl}}/article/send-lifespan/#deletion-date). Like the **My Vault** view, you can filter your Sends by selecting one of the available **Types**. |
||||
2. To start creating a new Send, select the {% icon fa-plus %} **Create New Send** button: |
||||
|
||||
{% image /send/send-create-webvault.png Send View in the Web Vault %} |
||||
3. On the **Create New Send** dialog, specify the following to create the contents of your Send: |
||||
|
||||
- **What type of Send is this?**: Specify whether this Send will be **Text** or a **File**: |
||||
|
||||
|**Text**|Type or paste the desired text into the input box. Toggle the **When accessing the Send, hide the text by default** option to require recipients to [toggle visibility]({{site.baseurl}}/article/send-privacy/#hide-text) when they open a Send.| |
||||
|**File**|Select the **Choose File** button and browse for the file to send. The maximum file size per Send is 100 MB. (**Requires Premium**)| |
||||
|
||||
- **Name**: Specify an identifiable, meaningful name for this Send. |
||||
|
||||
By default, a Send will be scheduled for deletion 7 days from its creation. You may configure this and other options using the {% icon fa-chevron-down %} **Options** menu (see Step 4), otherwise select **Save** to finish creating your Send. |
||||
|
||||
4. Select the {% icon fa-chevron-down %} **Options** menu to configure the following options as desired: |
||||
|
||||
|**Deletion Date**|The Send will be permanently [deleted]({{site.baseurl}}/article/send-lifespan/#deletion-behavior) on the specified date and time. By default, 7 days from creation. The **maximum allowed value** is 30 days from creation.| |
||||
|**Expiration Date**|The Send will [expire]({{site.baseurl}}/article/send-lifespan/#expiration-behavior) on the specified date and time. By default, **Never**.| |
||||
|**Maximum Access Count**|The Send will be [disabled]({{site.baseurl}}/article/send-lifespan/#maximum-access-count-behavior) after the specified access count is reached. By default, unspecified.| |
||||
|**Password**|[Require a password]({{site.baseurl}}/article/send-privacy/#send-passwords) to be entered by recipients of this Send in order to gain access.| |
||||
|**Notes**|Enter private notes for this Send, which will only be visible to the Sender.| |
||||
**Disable this send so that no one can access it**|Check this box to prevent this Send from being accessible to any recipients. You will still be able to interact this Send from your Send view.| |
||||
|
||||
{% callout success%}The rest of this article covers copying a Send link to your clipboard, but you can do that automatically by checking the **Copy the link to share this Send to my clipboard upon save** option before you click **Save**.{% endcallout %} |
||||
|
||||
Once you're happy with the configuration of your Send, select the **Save** button to finish. |
||||
|
||||
Once your Send is created, use the hover-over {% icon fa-cog %} gear dropdown and select the {% icon fa-copy %} **Copy Send link** button to copy the generated link to your clipboard: |
||||
|
||||
{% image /send/send-from-webvault.png Copy a Send link %} |
||||
|
||||
Once copied, share your Send link with intended recipients however you prefer. Sends are end-to-end encrypted, so you don't need to worry about exposing any Send data to whatever intermediary communications services you use. |
||||
|
||||
{% endcapture %} |
||||
{{ web_vault | markdownify}} |
||||
</div> |
||||
<div class="tab-pane" id="browserextension" role="tabpanel" aria-labelledby="betab"> |
||||
{% capture browser_extension %} |
||||
### Send from a Browser Extension |
||||
|
||||
Complete the following steps to create a new Send from a Bitwarden Browser Extension: |
||||
|
||||
1. Select the {% icon fa-paper-plane %} **Send** tab located at the bottom of your Browser Extension. |
||||
|
||||
This view will list all Sends that haven't reached their [deletion date]({{site.baseurl}}/article/send-lifespan/#deletion-date). Like the {% icon fa-lock %} **My Vault** view, you can filter your Sends by selecting one of the available **Types**. |
||||
2. To start creating a new Send, select the {% icon fa-plus %} **Add** icon: |
||||
|
||||
{% image /send/send-browserext.png Send View in a Browser Extension %} |
||||
|
||||
3. On the **Add Send** view, specify the following to create the contents of your Send: |
||||
|
||||
- **Name**: Specify an identifiable, meaningful name for this Send. |
||||
- **Type**: Specify whether this Send will be **Text** or a **File**: |
||||
|
||||
|**Text** | Type or paste the desired text into the input box. Toggle the **When accessing the Send, hide the text by default** option to require recipients to [toggle visibility]({{site.baseurl}}/article/send-privacy/#hide-text) when they open a Send.| |
||||
|**File** | Select the **Choose File** button and browse for the file to send. The maximum file size per Send is 100 MB. (**Requires Premium**)<br><br>If you're using **Firefox or Safari**, you'll need to popout ({% icon fa-external-link fa-rotate-270 %}) the Browser Extension in order to browse for the file to send.| |
||||
|
||||
By default, a Send will be scheduled for deletion 7 days from its creation. You may configure this and other options using the {% icon fa-chevron-down %} **Options** menu (see Step 4), otherwise select **Save** to finish creating your Send. |
||||
|
||||
4. Select the {% icon fa-chevron-down %} **Options** menu to configure the following options as desired: |
||||
|
||||
|**Deletion Date**|The Send will be permanently [deleted]({{site.baseurl}}/article/send-lifespan/#deletion-behavior) on the specified date and time. By default, 7 days from creation. The **maximum allowed value** is 30 days from creation.| |
||||
|**Expiration Date**|The Send will [expire]({{site.baseurl}}/article/send-lifespan/#expiration-behavior) on the specified date and time. By default, **Never**.| |
||||
|**Maximum Access Count**|The Send will be [disabled]({{site.baseurl}}/article/send-lifespan/#maximum-access-count-behavior) after the specified access count is reached. By default, unspecified.| |
||||
|**Password**|[Require a password]({{site.baseurl}}/article/send-privacy/#send-passwords) to be entered by recipients of this Send in order to gain access.| |
||||
|**Notes**|Enter private notes for this Send, which will only be visible to the Sender.| |
||||
|**Disable this send so that no one can access it**|Check this box to prevent this Send from being accessible to any recipients. You will still be able to interact this Send from your Send view.| |
||||
|
||||
{% callout success%}The rest of this article covers copying a Send link to your clipboard, but you can do that automatically by checking the **Copy the link to share this Send to my clipboard upon save** option before you click **Save**.{% endcallout %} |
||||
|
||||
Once you're happy with the configuration of your Send, select the **Save** button to finish. |
||||
|
||||
Once your Send is created, select the {% icon fa-copy %} **Copy Link** icon to copy the generated link to your clipboard: |
||||
|
||||
{% image /send/send-be-share.png Copy a Send link %} |
||||
|
||||
Once copied, share your Send link with intended recipients however you prefer. Sends are end-to-end encrypted, so you don't need to worry about exposing any Send data to whatever intermediary communications services you use. |
||||
|
||||
{% endcapture %} |
||||
{{ browser_extension | markdownify}} |
||||
</div> |
||||
<div class="tab-pane" id="desktop" role="tabpanel" aria-labelledby="desktab"> |
||||
{% capture desktop_info %} |
||||
### Send from a Desktop App |
||||
|
||||
Complete the following steps to create a new Send from a Bitwarden Desktop App: |
||||
|
||||
1. Select the {% icon fa-paper-plane %} **Send** tab located at the bottom of the left-most column in your Desktop App. |
||||
|
||||
The center column will list all Sends that haven't reached their [deletion date]({% link _articles/send/send-lifespan.md %}). Like the {% icon fa-lock %} **My Vault** view, you can filter your Sends by selecting one of the available **Types** from the left-most column. |
||||
2. To start creating a new Send, select the {% icon fa-plus %} **Add** icon in at the bottom of the center column. |
||||
|
||||
{% image /send/send-desktop-add.png Send view in a Desktop App %} |
||||
3. In the right-most column, specify the following to create the contents of your Send: |
||||
|
||||
- **Name**: Specify an identifiable, meaningful name for this Send. |
||||
- **Type**: Specify whether this Send will be **Text** or a **File**: |
||||
|
||||
| **Text** | Type or paste the desired text into the input box. Toggle the **When accessing the send, hide text by default** option to require recipients to [toggle visibility]({% link _articles/send/send-privacy.md %}) when they open a Send.| |
||||
| **File** | Select the **Choose File** button and browse for the file to send. The maximum file size per Send is 100 MB. (**Requires Premium**)| |
||||
|
||||
By default, a Send will be scheduled for deletion 7 days from its creation. You may configure this and other options using the {% icon fa-chevron-down %} **Options** menu (see Step 4), otherwise select **Save** to finish creating your Send. |
||||
|
||||
4. Select the {% icon fa-chevron-down %} **Options** menu to configure the following options as desired: |
||||
|
||||
|**Deletion Date**|The Send will be permanently [deleted]({{site.baseurl}}/article/send-lifespan/#deletion-behavior) on the specified date and time. By default, 7 days from creation. The **maximum allowed value** is 30 days from creation.| |
||||
|**Expiration Date**|The Send will [expire]({{site.baseurl}}/article/send-lifespan/#expiration-behavior) on the specified date and time. By default, **Never**.| |
||||
|**Maximum Access Count**|The Send will be [disabled]({{site.baseurl}}/article/send-lifespan/#maximum-access-count-behavior) after the specified access count is reached. By default, unspecified.| |
||||
|**Password**|[Require a password]({{site.baseurl}}/article/send-privacy/#send-passwords) to be entered by recipients of this Send in order to gain access.| |
||||
|**Notes**|Enter private notes for this Send, which will only be visible to the Sender.| |
||||
|**Disable this send so that no one can access it**|Check this box to prevent this Send from being accessible to any recipients. You will still be able to interact this Send from your Send view.| |
||||
|
||||
{% callout success%}The rest of this article covers copying a Send link to your clipboard, but you can do that automatically by checking the **Copy the link to share this Send to my clipboard upon save** option before you click **Save**.{% endcallout %} |
||||
|
||||
Once you're happy with the configuration of your Send, select the **Save** button to finish. |
||||
|
||||
Once your Send is created, select the {% icon fa-copy %} **Copy Link** button to copy the generated link to your clipboard: |
||||
|
||||
{% image /send/send-desktop-share.png Copy a Send link %} |
||||
|
||||
Once copied, share your Send link with intended recipients however you prefer. Sends are end-to-end encrypted, so you don't need to worry about exposing any Send data to whatever intermediary communications services you use. |
||||
|
||||
{% endcapture %} |
||||
{{ desktop_info | markdownify}} |
||||
</div> |
||||
<div class="tab-pane" id="mobile" role="tabpanel" aria-labelledby="mobtab"> |
||||
{% capture mobile_info %} |
||||
### Send from a Mobile App |
||||
|
||||
Complete the following steps to create a new Send from Bitwarden Mobile App: |
||||
|
||||
1. Tap the {% icon fa-paper-plane %} **Send** tab located at the bottom of your screen. |
||||
|
||||
This view will list all Sends that haven't reached their [deletion date]({% link _articles/send/send-lifespan.md %}). Like the {% icon fa-lock %} **My Vault** view, you can filter your Sends by tapping one of the available **Types**. |
||||
2. To start creating a new Send, tap the {% icon fa-plus %} **Add** icon: |
||||
|
||||
{% image /send/send-mobile.png Send View on iOS and Android%} |
||||
|
||||
3. On the **Add Send** view, specify the following to create the contents of your Send: |
||||
|
||||
- **Type**: Specify whether this Send will be **Text** or a **File**: |
||||
|
||||
|**Text** | Type or paste the desired text into the input box. Toggle the **When accessing the Send, hide the text by default** option to require recipients to [toggle visibility]({% link _articles/send/send-privacy.md %}) when they open a Send.| |
||||
|**File** | Tap the **Choose File** button and browse for the file to send. The maximum file size per Send is 100 MB. (**Requires Premium**)| |
||||
|
||||
- **Name**: Specify an identifiable, meaningful name for this Send. |
||||
|
||||
By default, a Send will be scheduled for deletion 7 days from its creation. You may configure this and other options using the {% icon fa-chevron-down %} **Options** menu (see Step 4), otherwise tap **Save** to finish creating your Send. |
||||
|
||||
4. Tap the {% icon fa-chevron-down %} **Options** menu to configure the following options as desired: |
||||
|
||||
|**Deletion Date**|The Send will be permanently [deleted]({{site.baseurl}}/article/send-lifespan/#deletion-behavior) on the specified date and time. By default, 7 days from creation. The **maximum allowed value** is 30 days from creation.| |
||||
|**Expiration Date**|The Send will [expire]({{site.baseurl}}/article/send-lifespan/#expiration-behavior) on the specified date and time. By default, **Never**.| |
||||
|**Maximum Access Count**|The Send will be [disabled]({{site.baseurl}}/article/send-lifespan/#maximum-access-count-behavior) after the specified access count is reached. By default, unspecified.| |
||||
|**Password**|[Require a password]({{site.baseurl}}/article/send-privacy/#send-passwords) to be entered by recipients of this Send in order to gain access.| |
||||
|**Notes**|Enter private notes for this Send, which will only be visible to the Sender.| |
||||
|**Disable this send so that no one can access it**|Check this box to prevent this Send from being accessible to any recipients. You will still be able to interact this Send from your Send view.| |
||||
|
||||
{% callout success%}Toggling the **Share upon save** option before you tap **Save** will open the share menu on your device so you can quickly share your Send link.{% endcallout %} |
||||
|
||||
Once you're happy with the configuration of your Send, tap the **Save** button to finish. |
||||
|
||||
Once your Send is created, tap the menu icon ( {% icon fa-ellipsis-v %} or {% icon fa-ellipsis-h %} ) and tap the **Share Link** option: |
||||
|
||||
{% image /send/send-share-mob.png Copy a Send link %} |
||||
|
||||
Share your Send link with intended recipients however you prefer. Sends are end-to-end encrypted, so you don't need to worry about exposing any Send data to whatever intermediary communications services you use. |
||||
{% endcapture %} |
||||
{{ mobile_info | markdownify}} |
||||
</div> |
||||
<div class="tab-pane" id="cli" role="tabpanel" aria-labelledby="cliab"> |
||||
{% capture cli_info %} |
||||
### Send from the CLI |
||||
|
||||
The following are sample commands to help you get started using Send from the CLI. |
||||
|
||||
To create a simple text Send with a [deletion date]({{site.baseurl}}/articles/send-lifespan/#deletion-date) set to 14 days from creation: |
||||
|
||||
``` |
||||
bw send -n "My Text Send" -d 14 "My first secret message." |
||||
``` |
||||
|
||||
To create a simple file Send with a [deletion date]({{site.baseurl}}/articles/send-lifespan/#deletion-date) set to 14 days from creation: |
||||
|
||||
``` |
||||
bw send -n "My File Send" - d 14 -f /Users/myaccount/Documents/my_file.pdf |
||||
``` |
||||
|
||||
The Bitwarden CLI is a fully-featured and powerful tool. We recommend reading the [Send from CLI]({% link _articles/send/send-cli.md %}) article to learn more. |
||||
|
||||
{% endcapture %} |
||||
{{ cli_info | markdownify}} |
||||
</div> |
||||
</div> |
||||
@ -0,0 +1,27 @@
@@ -0,0 +1,27 @@
|
||||
--- |
||||
layout: article |
||||
title: Receive a Send |
||||
categories: [send] |
||||
featured: true |
||||
popular: false |
||||
tags: [bitwarden send, send, receive, receive a send] |
||||
order: 03 |
||||
--- |
||||
|
||||
Unlike traditional Bitwarden Vault items, a Send can be received and opened by anyone with the Send link (including those who *do not* have Bitwarden accounts). Send links are randomly generated, and will look something like the following: |
||||
|
||||
- `https://vault.bitwarden.com/#/send/yawoill8rk6VM6zCATXv2A/9WN8wD-hzsDJjfnXLeNc2Q` |
||||
- `https://your.selfhosted.domain.com/#/send/yawoill8rk6VM6zCATXv2A/9WN8wD-hzsDJjfnXLeNc2Q` |
||||
|
||||
These links can be opened in any modern web browser, and will open a simple no-navigation web page, for example: |
||||
|
||||
{% image /send/received-send.png A received Send%} |
||||
|
||||
Depending on the [options configured]({% link _articles/send/create-send.md %}) by the Sender, the recipient of a Send may be required to: |
||||
|
||||
- Enter a Password to access the contents of the Send. |
||||
- Manually toggle visibility on a hidden-text Send. |
||||
|
||||
When a Send has [been deleted, expired, or disabled]({% link _articles/send/send-lifespan.md %}), recipients who attempt to use the generated Send link will be shown a screen that reports the Send does not exist or is no longer available: |
||||
|
||||
{% image /send/send-unavailable.png A deleted, expired, or disabled Send %} |
||||
@ -0,0 +1,195 @@
@@ -0,0 +1,195 @@
|
||||
--- |
||||
layout: article |
||||
title: Send from CLI |
||||
categories: [send] |
||||
featured: true |
||||
popular: false |
||||
tags: [bitwarden send, send, cli] |
||||
order: 06 |
||||
--- |
||||
|
||||
Bitwarden Send is available as a set of fully-featured CLI commands. This article documents the breadth of `bw send` commands, however Send **is not a separate tool** from the Bitwarden Command-line Interface (CLI). Therefore, many of the commands, options, and concepts in the [CLI documentation]({% link _articles/miscellaneous/cli.md %}) are relevant here. |
||||
|
||||
{% image /send/send-cli.png Send's --help text %} |
||||
|
||||
## send |
||||
|
||||
The `send` command is the master command used to access all Send-related subcommands: |
||||
|
||||
``` |
||||
bw send [options] [command] <data> |
||||
``` |
||||
|
||||
The `send` command can **also** be used as a shortcut to quickly `create` a Send, for example: |
||||
|
||||
``` |
||||
bw send "Fastest Send in the West." |
||||
``` |
||||
|
||||
will create a text Send object with the contents `Fastest Send in the West.` and output the Send link. Or, for example: |
||||
|
||||
``` |
||||
bw send -f <path/to/file.ext> |
||||
``` |
||||
|
||||
will create a file Send object with the specified file at the specified `path` and output the Send link. |
||||
|
||||
**Options:** |
||||
|
||||
- Use `-n <name>` or `--name <name>` to specify a name for the Send. If none is specified, name will default to the `id` for text Sends and file name for file Sends. For multi-word names, use quotations `"<name>"`. |
||||
- Use `-d <days>` or `--deleteInDays <days>` to specify a [deletion date]({{site.baseurl}}/article/send-lifespan/#deletion-date) for the Send (defaults to 7 days if unspecified). |
||||
- Use `--hidden` to specify that a text Send require recipients to [toggle visibility]({{site.baseurl}}/article/send-privacy/#hide-text). |
||||
- Use `--notes <notes>` to add private notes to the Send. For multi-word notes, use quotations `"<notes>"`. |
||||
- Use `--fullObject` to output the full Send object as JSON rather than only the Send link (pair this option with the `--pretty` option for formatted JSON). |
||||
|
||||
**Full Example:** |
||||
|
||||
``` |
||||
bw send -n "My First Send" -d 7 --hidden "The contents of my first Send." |
||||
``` |
||||
|
||||
### create |
||||
|
||||
The `create` command creates a Send. `create` allows more advanced configuration than using only `bw send` and takes encoded JSON for its argument: |
||||
|
||||
``` |
||||
bw send create [options] <encodedJson> |
||||
``` |
||||
|
||||
A typical workflow might look something like: |
||||
|
||||
1. Use the `template` command (see [details](#template)) to output the appropriate JSON template for your Send type. |
||||
2. Use a [command-line JSON processor like jq](https://stedolan.github.io/jq/){:target="\_blank"} to manipulate the outputted template as required. |
||||
3. Use the `encode` command (see [details]({{site.baseurl}}/article/cli/#encode)) to encode the manipulated JSON. |
||||
4. Use the `create` command to create a Send from the encoded JSON. |
||||
|
||||
For example: |
||||
|
||||
``` |
||||
bw send template send.text | jq '.name="My First Send" | .text.text="Secrets I want to share."' | bw encode | bw send create |
||||
``` |
||||
or |
||||
``` |
||||
bw send template send.text | jq ".name=\"My First Send\" | .text.text=\"Secrets I want to share.\" | .password=\"mypassword\" | .deletionDate=\"$(date -uv+14d + "%Y-%m-%dT%H:%M:%SZ")\"" | bw encode | bw send create |
||||
``` |
||||
|
||||
{% callout success %} |
||||
Notice in the 2nd example that the jq invokation must be wrapped in double quotes (`" "`) and use escapes (`\`) for each filter due to a nested `date` variable that configures a `.deletionDate` in the Send. |
||||
{% endcallout %} |
||||
|
||||
**Options:** |
||||
|
||||
- Use `--file <path>` to specify the file to Send (this can also be specified in encoded JSON). |
||||
- Use `--text <text>` to specify the text to Send (this can also be specified in encoded JSON). |
||||
- Use `--hidden` to specify that a text Send require recipients to [toggle visibility]({{site.baseurl}}/article/send-privacy/#hide-text). |
||||
- Use `--password <password>` to specify the password needed to access [password-protected]({{site.baseurl}}/article/send-privacy/#send-passwords). |
||||
- Use `--fullObject` to output the full Send object as JSON rather than only the Send link (pair this option with the `--pretty` option for formatted JSON). |
||||
|
||||
### get |
||||
|
||||
The `get` command will retrieve a Send owned by you and output it as a JSON object. `get` takes an exact `id` value or any string for its argument. If you use a string, `get` will search your Sends for one with a value that matches: |
||||
|
||||
``` |
||||
bw send get [options] <id / string> |
||||
``` |
||||
|
||||
If you create a Send in another Bitwarden application while this session is still active, use the `bw sync` command to pull recent sends. For more information, refer to our [CLI documentation]({% link _articles/miscellaneous/cli.md %}). |
||||
|
||||
**Options:** |
||||
|
||||
- Use `--text` to output only the text contents of a text Send. |
||||
- Use `--file` to output only the file of a file Send. Pair `--file` with `--output` to specify a directory, or with `--raw` to output to stdout. |
||||
- Use `--output <output>` to specify the output directory for the `--file` option. |
||||
|
||||
### edit |
||||
|
||||
The `edit` command edits an existing Send object. `edit` takes encoded JSON for its argument: |
||||
|
||||
``` |
||||
bw send edit <encodedJson> |
||||
``` |
||||
|
||||
A typical workflow might look something like: |
||||
|
||||
1. Use the `get` command (see [details](#get)) to retrieve the desired Send according to its `<id>`. |
||||
2. Use a [command-line JSON processor like jq](https://stedolan.github.io/jq/){:target="\_blank"} to manipulate the retrieved Send as required. |
||||
3. Use the `encode` command (see [details]({{site.baseurl}}/article/cli/#encode)) to encode the manipulated JSON. |
||||
4. Use the `edit` command to write the edits to the Send. |
||||
|
||||
For example: |
||||
|
||||
``` |
||||
bw send get <id> | jq '.name="New Name" | .password=null' | bw encode | bw send edit |
||||
``` |
||||
|
||||
**Options:** |
||||
|
||||
- Use `--itemid <itemid>` to overwrite the id value provided of the Send with a new one. |
||||
|
||||
{% callout note %} |
||||
You can't `edit` a file Send's file. To do this, you'll need to delete the Send and re-create it with the appropriate file. |
||||
{% endcallout %} |
||||
|
||||
### list |
||||
|
||||
The `list` command will list all Sends owned by you and output them as JSON: |
||||
|
||||
``` |
||||
bw send list [options] |
||||
``` |
||||
|
||||
If you create a Send in another Bitwarden application while this session is still active, use the `bw sync` command to pull recent sends. For more information, refer to our [CLI documentation]({% link _articles/miscellaneous/cli.md %}). |
||||
|
||||
**Options:** |
||||
|
||||
- Use `--pretty` to format the JSON the output. |
||||
- Pipe stdout to a file using the `>` operator, for example: |
||||
|
||||
``` |
||||
bw send list --pretty > /Users/myaccount/Documents/pretty_list_of_sends.json |
||||
``` |
||||
|
||||
### delete |
||||
|
||||
The `delete` command will delete a Send owned by you. `delete` takes only an exact `id` value for its argument. |
||||
|
||||
``` |
||||
bw send delete <id> |
||||
``` |
||||
|
||||
{% callout success %} |
||||
If you don't know the exact `id` of the Send you want to delete, use `bw send get <search term>` to find it. |
||||
{% endcallout %} |
||||
|
||||
### template |
||||
|
||||
The `template` command returns the expected JSON formatting for a Send object. `template` takes an `<object>` specification for its argument, either `send.text` or `send.file`. |
||||
|
||||
``` |
||||
bw send template <object> |
||||
``` |
||||
|
||||
While you *can* use `template` to output the format to your screen, the most common use-case is to pipe the output into a `bw send create` operation, using a [command-line JSON processor like jq](https://stedolan.github.io/jq/){:target="\_blank"} and `bw encode` to manipulate the values retrieved from the template, for example: |
||||
|
||||
``` |
||||
bw send template send.text | jq '.name="My First Send" | .text.text="Secrets I want to share."' | bw encode | bw send create |
||||
``` |
||||
|
||||
## receive |
||||
|
||||
The `receive` command accesses a Send. `receive` takes a Send `<url>` for its argument: |
||||
|
||||
``` |
||||
bw send receive [options] <url> |
||||
``` |
||||
|
||||
- For text Sends, `receive` will return the text contents of the Send to stdout. |
||||
- For file Sends, `receive` will download the file to the current working directory. |
||||
|
||||
**Options:** |
||||
|
||||
- Use `--password <password>` to provide the password needed to access [password-protected]({{site.baseurl}}/article/send-privacy/#send-passwords) Sends as a string. |
||||
- Use `--passwordenv <passwordenv>` to specify the password needed to access [password-protected]({{site.baseurl}}/article/send-privacy/#send-passwords) Sends as a stored environment variable. |
||||
- Use `--passwordfile <passwordfile>` to specify the password needed to access [password-protected]({{site.baseurl}}/article/send-privacy/#send-passwords) Sends as a file with the password as its first line. |
||||
- Use `--obj` to output the full Send object as JSON rather than only the Send link (pair this option with the `--pretty` option for formatted JSON). |
||||
- Use `--ouput <output>` to specify the output directory for the contents of a file Send. |
||||
@ -0,0 +1,19 @@
@@ -0,0 +1,19 @@
|
||||
--- |
||||
layout: article |
||||
title: Self-hosting Send |
||||
categories: [send] |
||||
featured: true |
||||
popular: false |
||||
tags: [] |
||||
order: 07 |
||||
--- |
||||
|
||||
Once you [update your instance]({% link _articles/hosting/updating-on-premise.md %}), most implementations will be already setup to begin [using Send]({% link _articles/send/create-send.md %}). An exception to this is if you're using a non-default **mapped volume for attachment storage**. |
||||
|
||||
The files attached to File Sends are stored in a `send` subdirectory of the existing attachments volume (i.e. `./bwdata/core/attachments/send`). This is dictated by the `globalSettings__send__baseDirectory=` environment variable, which has the following default configuration in `global.override.env`: |
||||
|
||||
``` |
||||
globalSettings__send__baseDirectory=/etc/bitwarden/core/attachments/send |
||||
``` |
||||
|
||||
If you want to store the files attached to File Sends in your non-default attachments volume, you'll need to point `globalSettings__send__baseDirectory=` to the new volume. For more information, see [Configure Environment Variables](#). |
||||
@ -0,0 +1,211 @@
@@ -0,0 +1,211 @@
|
||||
--- |
||||
layout: article |
||||
title: Send Lifespan |
||||
categories: [send] |
||||
featured: true |
||||
popular: false |
||||
tags: [bitwarden send, send, ephemeral sharing, deletion, expiration, access count] |
||||
order: 04 |
||||
--- |
||||
|
||||
Unlike traditional Bitwarden Vault items and File Attachments, Sends are ephemeral and have a **default lifespan of 7 days**. The lifespan of a Send is entirely configurable using the [Deletion Date](#deletion-date) option, each having a maximum allowed lifespan of 30 days. When a Send has reached its Deletion Date, it will be purged from Bitwarden systems and inaccessible to both its Sender and recipients. |
||||
|
||||
**Optionally**, you can configure additional limitations on recipient access using the [Expiration Date](#expiration-date) and/or [Maximum Access Count](#maximum-access-count) options. |
||||
|
||||
You can also manually [disable or delete](#manually-disable-or-delete) a Send at any time. |
||||
|
||||
## Deletion Date |
||||
|
||||
By default, a Send will have a Deletion Date set to 7 days from creation. Using the **Deletion Date** option, you may change this to a range of pre-specified options (e.g. *1 hour*, *1 day*, *30 days*) or specify a **Custom** timestamp using the date picker (or in the text input in the format `MM/DD/YYYY HH:MM AM/PM`). |
||||
|
||||
Deletion Date has a **maximum allowed value of 30 days from creation**. |
||||
|
||||
### Deletion Behavior |
||||
|
||||
When a Send reaches its configured Deletion Date: |
||||
|
||||
- For recipients of the Send (i.e. anyone with the generated link), navigating to the Send link will show a screen reporting that the Send does not exist or is no longer available. |
||||
|
||||
- For the Sender, a {% icon fa-trash %} **Pending Deletion** icon will appear next to the Send. The Send will pend deletion for a few minutes, after which it will be permanently deleted from Bitwarden systems and from the Sender's Send view. |
||||
|
||||
{% callout note %}There is no "soft delete" or Trash Can for Sends, meaning that once the pending deletion window has closed you will not be able to access the contents of a Send.{% endcallout %} |
||||
|
||||
## Expiration Date |
||||
|
||||
By default, Expiration Date will be set to Never. Using the **Expiration Date** option, you may change this to a range of pre-specified options (e.g. *1 hour*, *1 day*, *7 days*) or specify a **Custom** timestamp using the date picker (or in the text input in the format `MM/DD/YYYY HH:MM AM/PM`). |
||||
|
||||
### Expiration Behavior |
||||
|
||||
When a Send reaches its specified Expiration Date: |
||||
|
||||
- For recipients of the Send (i.e. anyone with the generated link), navigating to the Send link will show a screen reporting that the Send does not exist or is no longer available. |
||||
|
||||
- For the Sender, an {% icon fa-clock-o %} **Expired** icon will appear next to the Send. The Send will remain accessible to its Sender in the Send view until the specified **Deletion Date** is reached. |
||||
|
||||
## Maximum Access Count |
||||
|
||||
For all Sends, a **Current Access Count** ticker will track the number of times the Send link has been accessed: |
||||
|
||||
{% image /send/send-access-ticker.png Current Access Count ticker %} |
||||
|
||||
For any Send, you may specify a **Maximum Access Count** that is a positive integer. |
||||
|
||||
### Maximum Access Count Behavior |
||||
|
||||
When a Send reaches its specified Maximum Access Count: |
||||
|
||||
- For recipients of the Send (i.e. anyone with the generated link), navigating to the Send link will show a screen reporting that the Send does not exist or is no longer available. |
||||
|
||||
- For the Sender, a {% icon fa-ban %} **Max access count reached** icon will appear next to the Send. The Send will remain accessible to its Sender in the Send view until the specified **Deletion Date** is reached. |
||||
|
||||
{% callout success %} |
||||
The **Current Access Count** ticker counts: |
||||
- For text Sends, the number of times the link has been accessed. |
||||
- For file Sends, the number of times the contents are downloaded. |
||||
{% endcallout %} |
||||
|
||||
## Manually Disable or Delete |
||||
|
||||
Manually disable or delete a Send from any Bitwarden application: |
||||
|
||||
<ul class="nav nav-tabs" id="myTab" role="tablist"> |
||||
<li class="nav-item" role="presentation"> |
||||
<a class="nav-link active" id="wvtab" data-target="#webvault" role="tab" aria-controls="webvault" aria-selected="true">Web Vault</a> |
||||
</li> |
||||
<li class="nav-item" role="presentation"> |
||||
<a class="nav-link" id="betab" data-target="#browserextension" role="tab" aria-controls="browserextension" aria-selected="false">Browser Extension</a> |
||||
</li> |
||||
<li class="nav-item" role="presentation"> |
||||
<a class="nav-link" id="desktab" data-target="#desktop" role="tab" aria-controls="desktop" aria-selected="false">Desktop</a> |
||||
</li> |
||||
<li class="nav-item" role="presentation"> |
||||
<a class="nav-link" id="mobtab" data-target="#mobile" role="tab" aria-controls="mobile" aria-selected="false">Mobile</a> |
||||
</li> |
||||
<li class="nav-item" role="presentation"> |
||||
<a class="nav-link" id="clitab" data-target="#cli" role="tab" aria-controls="cli" aria-selected="false">CLI</a> |
||||
</li> |
||||
</ul> |
||||
<div class="tab-content" id="clientsContent"> |
||||
<div class="tab-pane show active" id="webvault" role="tabpanel" aria-labelledby="wvtab"> |
||||
{% capture web_vault %} |
||||
|
||||
#### Disable from the Web Vault |
||||
|
||||
To disable a Send from the Web Vault, open the **Edit Send** view and check the **Disable this Send so that no one can access it** checkbox. You can uncheck this box at any time to re-enable access to the Send. |
||||
|
||||
{% image /send/send-disable-wv.png Disable from the Web Vault %} |
||||
|
||||
When a Send is disabled: |
||||
|
||||
- For recipients of the Send (i.e. anyone with the generated link), navigating to the Send link will show a screen reporting that the Send does not exist or is no longer available. |
||||
|
||||
- For the Sender, a {% icon fa-warning %} **Disabled** icon will appear next to the Send. The Send will remain accessible to its Sender in the Send view until the specified **Deletion Date** is reached. |
||||
|
||||
#### Delete from the Web Vault |
||||
|
||||
To delete a Send from the Web Vault, use the hover-over {% icon fa-cog %} gear dropdown to select the {% icon fa-trash %} **Delete** button: |
||||
|
||||
{% image /send/send-delete.png Delete from the Web Vault %} |
||||
|
||||
{% endcapture %} |
||||
{{ web_vault | markdownify}} |
||||
</div> |
||||
<div class="tab-pane" id="browserextension" role="tabpanel" aria-labelledby="betab"> |
||||
{% capture browser_extension %} |
||||
|
||||
#### Disable from Browser Extensions |
||||
|
||||
To disable a Send from a Browser Extension, open the **Edit Send** view and check the **Disable this Send so that no one can access it** checkbox. You can uncheck this box at any time to re-enable access to the Send. |
||||
|
||||
{% image /send/send-disable-be.png Disable from a Browser Extension %} |
||||
|
||||
When a Send is disabled: |
||||
|
||||
- For recipients of the Send (i.e. anyone with the generated link), navigating to the Send link will show a screen reporting that the Send does not exist or is no longer available. |
||||
|
||||
- For the Sender, a {% icon fa-warning %} **Disabled** icon will appear next to the Send. The Send will remain accessible to its Sender in the Send view until the specified **Deletion Date** is reached. |
||||
|
||||
#### Delete from Browser Extensions |
||||
|
||||
To delete a Send from a Browser Extension, select the {% icon fa-trash %} **Trash** icon next to the Send you want to delete: |
||||
|
||||
{% image /send/send-delete-be.png Delete from a Browser Extension %} |
||||
|
||||
{% endcapture %} |
||||
{{ browser_extension | markdownify}} |
||||
</div> |
||||
<div class="tab-pane" id="desktop" role="tabpanel" aria-labelledby="desktab"> |
||||
{% capture desktop_info %} |
||||
|
||||
#### Disable from Desktop Apps |
||||
|
||||
To disable a Send from a Desktop App, open the **Edit Send** view and check the **Disable this Send so that no one can access it** checkbox. You can uncheck this box at any time to re-enable access to the Send. |
||||
|
||||
{% image /send/send-desktop-disable.png Disable from a Desktop App%} |
||||
|
||||
When a Send is disabled: |
||||
|
||||
- For recipients of the Send (i.e. anyone with the generated link), navigating to the Send link will show a screen reporting that the Send does not exist or is no longer available. |
||||
|
||||
- For the Sender, a {% icon fa-warning %} **Disabled** icon will appear next to the Send. The Send will remain accessible to its Sender in the Send view until the specified **Deletion Date** is reached. |
||||
|
||||
#### Delete from Desktop Apps |
||||
|
||||
To delete a Send from a Desktop App, open the **Edit Send** view and select the {% icon fa-trash %} **Delete** button: |
||||
|
||||
{% image /send/send-desktop-delete.png Delete from a Desktop App %} |
||||
|
||||
{% endcapture %} |
||||
{{ desktop_info | markdownify}} |
||||
</div> |
||||
<div class="tab-pane" id="mobile" role="tabpanel" aria-labelledby="mobtab"> |
||||
{% capture mobile_info %} |
||||
|
||||
#### Disable from Mobile Apps |
||||
|
||||
To disable a Send from a Mobile App, open the **Edit Send** view and toggle the **Disable this Send so that no one can access it** option. You can toggle this option off at any time to re-enable access to the Send. |
||||
|
||||
{% image /send/send-disable-mobile.png Disable from a Mobile App %} |
||||
|
||||
When a Send is disabled: |
||||
|
||||
- For recipients of the Send (i.e. anyone with the generated link), navigating to the Send link will show a screen reporting that the Send does not exist or is no longer available. |
||||
|
||||
- For the Sender, a {% icon fa-warning %} **Disabled** icon will appear next to the Send. The Send will remain accessible to its Sender in the Send view until the specified **Deletion Date** is reached. |
||||
|
||||
#### Delete from Mobile Apps |
||||
|
||||
To delete a Send from a Mobile App, tap the menu icon ( {% icon fa-ellipsis-v %} or {% icon fa-ellipsis-h %} ) and tap the **Delete** option: |
||||
|
||||
{% image /send/send-delete-mob.png Delete from a Mobile App %} |
||||
|
||||
{% endcapture %} |
||||
{{ mobile_info | markdownify}} |
||||
</div> |
||||
<div class="tab-pane" id="cli" role="tabpanel" aria-labelledby="cliab"> |
||||
{% capture cli_info %} |
||||
|
||||
#### Disable from the CLI |
||||
|
||||
To disable a Send from the CLI, you'll need to use the `edit` command to change the `"disabled":false` key-value pair to `"disabled":true`, for example: |
||||
|
||||
``` |
||||
bw send get <id> | jq '.disabled=false' | bw encode | bw send edit |
||||
``` |
||||
|
||||
We recommend reading the [Send from CLI]({% link _articles/send/send-cli.md %}) article for complete information on using Send from the CLI. |
||||
|
||||
#### Delete from the CLI |
||||
|
||||
To delete a Send from the CLI, use the `delete` command with the Send's exact unique `id` as an argument: |
||||
|
||||
``` |
||||
bw send delete <id> |
||||
``` |
||||
|
||||
We recommend reading the [Send from CLI]({% link _articles/send/send-cli.md %}) article for complete information on using Send from the CLI. |
||||
|
||||
{% endcapture %} |
||||
{{ cli_info | markdownify}} |
||||
</div> |
||||
</div> |
||||
@ -0,0 +1,36 @@
@@ -0,0 +1,36 @@
|
||||
--- |
||||
layout: article |
||||
title: Send Privacy |
||||
categories: [send] |
||||
featured: true |
||||
popular: false |
||||
tags: [bitwarden send, send, passwords, hidden text] |
||||
order: 05 |
||||
--- |
||||
Protect the contents of your Send by optionally configuring a [password for access](#passwords) so that no unintended recipients can see the contained information. For text Sends, you can also optionally require recipients to [toggle visibility](#hide-text) to prevent exposure to unintentional onlookers. |
||||
|
||||
The **Password** and **Hide Text** options are configurable from the Create New Send view, or from the Edit Send views at any time prior to the Send's [deletion]({{site.baseurl}}/article/send-lifespan/#deletion-behavior). |
||||
|
||||
## Send Passwords |
||||
|
||||
For any Send, you may configure a password that recipients will be required to enter in order to access its contents. Password-protecting a Send is a good way to ensure the contents of a Send aren't exposed to unintended recipients: |
||||
|
||||
{% image /send/send-pw-protected.png Receiving a password-protected Send%} |
||||
|
||||
Once you password-protect a Send, you won't be able to view the configured password again, however you can [change](#change-send-passwords) or [remove](#remove-send-password) at any time: |
||||
|
||||
### Change Send Passwords |
||||
|
||||
You can change a Send's password at any time from the **Edit Send** view. Changing a Send's password **will not** require you to enter the previous password. When changing a Send's password, the **Password** field will change to **New Password**: |
||||
|
||||
{% image /send/send-new-pw.png %} |
||||
|
||||
### Remove Send Passwords |
||||
|
||||
You can remove a Send's password at any time using the {% icon fa-undo %} **Remove Password** menu option. Removing a Send's password **will not** require you to enter the previous password. |
||||
|
||||
## Hide Text |
||||
|
||||
For text Sends, toggle the **When accessing the Send, hide the text by default** option to require recipients to {% icon fa-eye %} **Toggle Visibility** in order to see its contents. Hiding the text on a Send is a good way to ensure the contents of a Send aren't exposed to unintentional onlookers: |
||||
|
||||
{% image /send/send-hidden-text.png Receiving a hidden-text Send%} |
||||
@ -0,0 +1,5 @@
@@ -0,0 +1,5 @@
|
||||
--- |
||||
layout: category |
||||
title: Bitwarden Send |
||||
featured: true |
||||
--- |
||||
|
After Width: | Height: | Size: 86 KiB |
|
After Width: | Height: | Size: 38 KiB |
|
After Width: | Height: | Size: 52 KiB |
|
After Width: | Height: | Size: 31 KiB |
|
After Width: | Height: | Size: 71 KiB |
|
Before Width: | Height: | Size: 72 KiB After Width: | Height: | Size: 76 KiB |
|
After Width: | Height: | Size: 12 KiB |
|
After Width: | Height: | Size: 146 KiB |
|
After Width: | Height: | Size: 16 KiB |
|
After Width: | Height: | Size: 14 KiB |
|
After Width: | Height: | Size: 185 KiB |
|
After Width: | Height: | Size: 105 KiB |
|
After Width: | Height: | Size: 35 KiB |
|
After Width: | Height: | Size: 15 KiB |
|
After Width: | Height: | Size: 124 KiB |
|
After Width: | Height: | Size: 47 KiB |
|
After Width: | Height: | Size: 145 KiB |
|
After Width: | Height: | Size: 145 KiB |
|
After Width: | Height: | Size: 38 KiB |
|
After Width: | Height: | Size: 148 KiB |
|
After Width: | Height: | Size: 144 KiB |
|
After Width: | Height: | Size: 37 KiB |
|
After Width: | Height: | Size: 164 KiB |
|
After Width: | Height: | Size: 26 KiB |
|
After Width: | Height: | Size: 32 KiB |
|
After Width: | Height: | Size: 22 KiB |
|
After Width: | Height: | Size: 39 KiB |
|
After Width: | Height: | Size: 27 KiB |
|
After Width: | Height: | Size: 19 KiB |
|
After Width: | Height: | Size: 171 KiB |
|
After Width: | Height: | Size: 126 KiB |
|
After Width: | Height: | Size: 27 KiB |
|
After Width: | Height: | Size: 28 KiB |
|
After Width: | Height: | Size: 123 KiB |
|
After Width: | Height: | Size: 131 KiB |
|
After Width: | Height: | Size: 51 KiB |
|
After Width: | Height: | Size: 42 KiB |
Loading…
Reference in new issue