1
0
mirror of https://github.com/bitwarden/help synced 2025-12-10 13:23:16 +00:00

Addressed Issues (#431)

* add to folder addition

* table fix

* custom fields screenshot

* woop!
This commit is contained in:
fred_the_tech_writer
2021-02-25 09:13:24 -05:00
committed by GitHub
parent d75c6ffa80
commit 4d0685a4e8
7 changed files with 21 additions and 8 deletions

View File

@@ -63,7 +63,9 @@ Follow this procedure to correctly configure a custom field for auto-fill. This
2. Find and copy the element `id` (find `id="xxx"`, where `xxx` is the element's `id` value). 2. Find and copy the element `id` (find `id="xxx"`, where `xxx` is the element's `id` value).
3. In the relevant Vault item's **Custom Fields** section, choose the appropriate field type and select the {% icon fa-plus %} **New Custom Field** button: 3. In the relevant Vault item's **Custom Fields** section, choose the appropriate field type and select the {% icon fa-plus %} **New Custom Field** button:
{% image /features/custom-fields/types.png %} {% image /features/custom-fields/types.png Select custom field type%}
4. Paste the copied element `id` in the **Name** field. 4. Paste the copied element `id` in the **Name** field.
5. Specify the desired information to be auto-filled (in the above example, a PIN) in the **Value** field. 5. Specify the desired information to be auto-filled (in the above example, a PIN) in the **Value** field.
{% image /features/custom-fields/custom-field-eg.png Custom field example %}
6. Save the Vault item. 6. Save the Vault item.

View File

@@ -46,3 +46,14 @@ Searching inside a "parent" Folder will not include items in Folders nested insi
To create a nested Folder, give a new Folder a **Name** that includes the "parent" Folder following by a forward slash (`/`) delimiter, for example `Personal/Email`. To create a nested Folder, give a new Folder a **Name** that includes the "parent" Folder following by a forward slash (`/`) delimiter, for example `Personal/Email`.
If there is no Folder with the corresponding "parent" name, the Folder won't nest and its title will be displayed in-full. If there is no Folder with the corresponding "parent" name, the Folder won't nest and its title will be displayed in-full.
## Add Items to a Folder
Once you've created a Folder in your Vault, there are a few ways to add items to it:
- From the **Add Item** or **Edit Item** screen on any Bitwarden application, select your new folder from the **Folder** dropdown and **Save** your item:
{% image manage-items/add-to-folder.png Add item to a Folder%}
- From the **My Vault** view, select the Vault items you want to move and use the top-level {% icon fa-cog %} gear dropdown to select the {% icon fa-share %} **Move Selected** button. On the Move Selected dialog box, choose the Folder you want to move the item(s) to:
{% image manage-items/add-to-folder-move.png Move item to a Folder %}

View File

@@ -40,7 +40,7 @@ Bitwarden Browser Extensions and Mobile Apps can select a **Default match detect
By default, Bitwarden will use **Base domain** matching as the default option. By default, Bitwarden will use **Base domain** matching as the default option.
#### Base domain ### Base domain
Selecting **Base domain** will prompt Bitwarden to offer auto-fill when the top-level domain and second-level domain of a Login's URI value match the detected resource. Selecting **Base domain** will prompt Bitwarden to offer auto-fill when the top-level domain and second-level domain of a Login's URI value match the detected resource.
@@ -49,7 +49,7 @@ For example, if the URI value `https://google.com` uses base domain match detect
- **Auto-fill offered** for `http://google.com` & `https://accounts.google.com` - **Auto-fill offered** for `http://google.com` & `https://accounts.google.com`
- **Auto-fill not offered** for `https://google.net` & `http://yahoo.com` - **Auto-fill not offered** for `https://google.net` & `http://yahoo.com`
#### Host ### Host
Selecting **Host** will prompt Bitwarden to offer auto-fill when the hostname and (*if specified*) port of the Login's URI value matches the detected resource. Selecting **Host** will prompt Bitwarden to offer auto-fill when the hostname and (*if specified*) port of the Login's URI value matches the detected resource.
@@ -58,7 +58,7 @@ For example, if the URI value `https://sub.domain.com:4000` uses host match dete
- **Auto-fill offered** for `http://sub.domain.com:4000` & `https://sub.domain.com:4000/page.html` - **Auto-fill offered** for `http://sub.domain.com:4000` & `https://sub.domain.com:4000/page.html`
- **Auto-fill not offered** for `https://domain.com`, `https://sub.domain.com`, `https://sub2.sub.domain.com:4000`, or `https://sub.domain.com:5000` - **Auto-fill not offered** for `https://domain.com`, `https://sub.domain.com`, `https://sub2.sub.domain.com:4000`, or `https://sub.domain.com:5000`
#### Starts with ### Starts with
Selecting **Starts with** will prompt Bitwarden to offer auto-fill when the detected resource starts with the Login URI value, regardless of what follows it. Selecting **Starts with** will prompt Bitwarden to offer auto-fill when the detected resource starts with the Login URI value, regardless of what follows it.
@@ -67,7 +67,7 @@ For example, if the URI value `https://sub.domain.com/path/` uses starts with ma
- **Auto-fill offered** for `https://sub.domain.com/path/` & `https://sub.domain.com/path/page.html` - **Auto-fill offered** for `https://sub.domain.com/path/` & `https://sub.domain.com/path/page.html`
- **Auto-fill not offered** for `https://sub.domain.com`, `https://sub.domain.com:4000/path/page.html` (interrupted with a port), or `https://sub.domain.com/path` (absent trailing slash) - **Auto-fill not offered** for `https://sub.domain.com`, `https://sub.domain.com:4000/path/page.html` (interrupted with a port), or `https://sub.domain.com/path` (absent trailing slash)
#### Regular expression ### Regular expression
{% callout note %} {% callout note %}
Regular expressions are an advanced option and can be quite dangerous if used incorrectly. You should not use this option if you do not know exactly what you're doing. Regular expressions are an advanced option and can be quite dangerous if used incorrectly. You should not use this option if you do not know exactly what you're doing.
@@ -80,7 +80,7 @@ For example, if the URI vault `^https://.*google\.com$` uses regular expression
- **Auto-fill offered** for `https://google.com`, `https://sub.google.com`, `https://malicious-site.com?q=google.com` - **Auto-fill offered** for `https://google.com`, `https://sub.google.com`, `https://malicious-site.com?q=google.com`
- **Auto-fill not offered** for `http://google.com` or `https://yahoo.com` - **Auto-fill not offered** for `http://google.com` or `https://yahoo.com`
#### Exact ### Exact
Selecting **Exact** will prompt Bitwarden to offer auto-fill when the Login URI value matches the detected resource exactly. Selecting **Exact** will prompt Bitwarden to offer auto-fill when the Login URI value matches the detected resource exactly.
@@ -89,6 +89,6 @@ For example, if the URI value `https://www.google.com/page.html` uses exact matc
- **Auto-fill offered** for `https://www.google.com/page.html` - **Auto-fill offered** for `https://www.google.com/page.html`
- **Auto-fill not offered** for `http://www.google.com/page.html`, `https://www.google.com/page.html?query=123`, or `https://www.google.com` - **Auto-fill not offered** for `http://www.google.com/page.html`, `https://www.google.com/page.html?query=123`, or `https://www.google.com`
#### Never ### Never
Selecting **Never** will prompt Bitwarden to never offer auto-fill for the Login item. Selecting **Never** will prompt Bitwarden to never offer auto-fill for the Login item.

View File

@@ -46,4 +46,4 @@ The following variables do not already exist in `global.override.env`, and can b
|globalSettings__mail__smtp__sslOverride=|Specify `true` to use SSL (not TLS) on port 25.| |globalSettings__mail__smtp__sslOverride=|Specify `true` to use SSL (not TLS) on port 25.|
|globalSettings__mail__smtp__startTls=|Specify `true` to force STARTTLS (Opportunistic TLS).| |globalSettings__mail__smtp__startTls=|Specify `true` to force STARTTLS (Opportunistic TLS).|
|globalSettings__organizationInviteExpirationHours=|Specify the number of hours after which an Organization Invite will expire (`120` by default).| |globalSettings__organizationInviteExpirationHours=|Specify the number of hours after which an Organization Invite will expire (`120` by default).|
|globalSettings__yubico__validationUrls__0=|Primary URL for self-hosted Yubico Validation Server. For example, `globalSettings__yubico__validationUrls__0=https://your.url.com/wsapi/2.0/verify`.<br><br>Add additional Validation Server URLs by creating incremented environment variables, for example `globalSettings__yubico__validationUrls__1=`, `globalSettings__yubico__validationUrls__2=`.| |globalSettings__yubico__validationUrls__0=|Primary URL for self-hosted Yubico Validation Server. For example: `=https://your.url.com/wsapi/2.0/verify`.<br><br>Add additional Validation Server URLs by creating incremented environment variables, for example `globalSettings__yubico__validationUrls__1=`, `globalSettings__yubico__validationUrls__2=`.|

Binary file not shown.

After

Width:  |  Height:  |  Size: 12 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 27 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 28 KiB