1
0
mirror of https://github.com/bitwarden/help synced 2026-01-01 08:03:28 +00:00

adding quotes for the array error

This commit is contained in:
DanHillesheim
2021-09-08 13:18:06 -06:00
parent eb4f670fa0
commit c97d820416
144 changed files with 144 additions and 144 deletions

View File

@@ -5,7 +5,7 @@ categories: [send]
featured: true
popular: false
tags: [bitwarden send, send, about send, ephemeral sharing]
order: 01
order: "01"
---
## What is Send?

View File

@@ -5,7 +5,7 @@ categories: [send]
featured: true
popular: false
tags: [bitwarden send, send, create a send, how to, ephemeral sharing]
order: 02
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.

View File

@@ -5,7 +5,7 @@ categories: [send]
featured: true
popular: false
tags: [bitwarden send, send, receive, receive a send]
order: 03
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 this:

View File

@@ -5,7 +5,7 @@ categories: [send]
featured: true
popular: false
tags: [bitwarden send, send, cli]
order: 06
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.

View File

@@ -5,7 +5,7 @@ categories: [send]
featured: true
popular: false
tags: [bitwarden send, send, about send, ephemeral sharing]
order: 07
order: "07"
---
## Send Encryption

View File

@@ -5,7 +5,7 @@ categories: [send]
featured: true
popular: false
tags: []
order: 08
order: "08"
---
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**.

View File

@@ -5,7 +5,7 @@ categories: [send]
featured: true
popular: false
tags: [bitwarden send, send, ephemeral sharing, deletion, expiration, access count]
order: 04
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 31 days. When a Send has reached its Deletion Date, it will be purged from Bitwarden systems and inaccessible to both its Sender and recipients.

View File

@@ -5,7 +5,7 @@ categories: [send]
featured: true
popular: false
tags: [bitwarden send, send, passwords, hidden text]
order: 05
order: "05"
---
Protect the contents of your Send by optionally configuring a [password for access](#send-passwords) so that no unintended recipients can see the contained information, and/or to [hide your email from recipients](). For text Sends, you can also optionally require recipients to [toggle visibility](#hide-text) to prevent exposure to unintentional onlookers.