1
0
mirror of https://github.com/bitwarden/help synced 2025-12-06 00:03:30 +00:00
Files
help/_articles/send/send-lifespan.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

10 KiB

layout, title, categories, featured, popular, tags, order
layout title categories featured popular tags order
article Send Lifespan
send
true false
bitwarden send
send
ephemeral sharing
deletion
expiration
access count
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 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 and/or Maximum Access Count options.

You can also 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:

{% 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}}

{% 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}}

{% 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}}

{% 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}}

{% 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}}