mirror of
https://github.com/bitwarden/help
synced 2025-12-28 06:03:15 +00:00
removed /article from URL
This commit is contained in:
@@ -12,7 +12,7 @@ The Bitwarden Authenticator is an alternative solution to dedicated authenticati
|
||||
|
||||
{% callout info %}Authenticator key (TOTP) storage is available to all accounts. TOTP code generation requires Premium or membership to a Paid Organization (Families, Teams, or Enterprise).{% endcallout %}
|
||||
|
||||
If you're new to using TOTPs for Two-step Login, refer to the [Field Guide to Two-step Login](https://bitwarden.com/help/article/bitwarden-field-guide-two-step-login/#securing-important-websites) for more information.
|
||||
If you're new to using TOTPs for Two-step Login, refer to the [Field Guide to Two-step Login](https://bitwarden.com/help/bitwarden-field-guide-two-step-login/#securing-important-websites) for more information.
|
||||
|
||||
## Generate TOTP Codes
|
||||
|
||||
|
||||
@@ -42,7 +42,7 @@ To enable the autofill service:
|
||||
|
||||
You'll be prompted to confirm you trust Bitwarden. Tapping **OK** will let Bitwarden read content on the screen to know when to offer auto-fill. Learn more from [our blog post](https://bitwarden.com/blog/post/the-oreo-autofill-framework){:target="_blank"}.
|
||||
|
||||
**Autofill Service not working?** See [Troubleshooting the Autofill Service]({{site.baseurl}}/article/auto-fill-android-troubleshooting/#troubleshooting-the-autofill-service).
|
||||
**Autofill Service not working?** See [Troubleshooting the Autofill Service]({{site.baseurl}}/auto-fill-android-troubleshooting/#troubleshooting-the-autofill-service).
|
||||
|
||||
#### Inline Autofill
|
||||
|
||||
@@ -80,7 +80,7 @@ To enable the accessibility method:
|
||||
{% callout warning %}
|
||||
If you're using Android 6+, you must also enable **Draw-Over**.
|
||||
|
||||
**Accessibility not working?** See [Troubleshooting the Accessibility Service]({{site.baseurl}}/article/auto-fill-android-troubleshooting/#troubleshooting-the-accessibility-service).
|
||||
**Accessibility not working?** See [Troubleshooting the Accessibility Service]({{site.baseurl}}/auto-fill-android-troubleshooting/#troubleshooting-the-accessibility-service).
|
||||
{% endcallout %}
|
||||
|
||||
#### Draw-Over
|
||||
|
||||
@@ -11,7 +11,7 @@ tags: [browser, auto-fill, autofill]
|
||||
{% callout success %}
|
||||
Most auto-fill functionality relies on the attribution of URIs to Login items. If you're unfamiliar with using URIs, see [Using URIs]({% link _articles/features/uri-match-detection.md %}).
|
||||
|
||||
Additionally, **basic authentication prompts** work a little differently than regular auto-fills. See our breakout article on [Basic Auth Prompts]({{site.baseurl}}/article/basic-auth-autofill)
|
||||
Additionally, **basic authentication prompts** work a little differently than regular auto-fills. See our breakout article on [Basic Auth Prompts]({{site.baseurl}}/basic-auth-autofill)
|
||||
{% endcallout %}
|
||||
|
||||
Bitwarden Browser Extensions have a unique **Tab** view, which automatically detects the URI (e.g. `myturbotax.intuit.com`) of the page displayed in the open tab and surfaces any Vault items with corresponding URIs.
|
||||
@@ -92,7 +92,7 @@ You can auto-fill items manually that don't have saved URIs by opening them in t
|
||||
|
||||
## TOTP Copy
|
||||
|
||||
If you use [Bitwarden Authenticator]({{site.baseurl}}/article/authenticator-keys/), Bitwarden will automatically copy a Login item's TOTP code to the clipboard when the Login item is autofilled by any of the above methods.
|
||||
If you use [Bitwarden Authenticator]({{site.baseurl}}/authenticator-keys/), Bitwarden will automatically copy a Login item's TOTP code to the clipboard when the Login item is autofilled by any of the above methods.
|
||||
|
||||
{% callout success %}
|
||||
You can disable this option and set a custom interval with which to clear your clipboard from the Browser Extension's {% icon fa-cogs %} **Settings** tab:
|
||||
|
||||
@@ -8,7 +8,7 @@ popular: false
|
||||
tags: [browser, autofill, auto-fill, identity, card, form fill]
|
||||
---
|
||||
|
||||
Bitwarden can do more than just [auto-fill your usernames and passwords]({% link _articles/features/auto-fill-browser.md %})! **Bitwarden Browser Extensions** can auto-fill [Cards]({{site.baseurl}}/article/managing-items/#cards) and [Identities]({{site.baseurl}}/article/managing-items/#identities) to simplify online purchases, account creation, and more using the [unique Tab view]({% link _articles/features/auto-fill-browser.md %}).
|
||||
Bitwarden can do more than just [auto-fill your usernames and passwords]({% link _articles/features/auto-fill-browser.md %})! **Bitwarden Browser Extensions** can auto-fill [Cards]({{site.baseurl}}/managing-items/#cards) and [Identities]({{site.baseurl}}/managing-items/#identities) to simplify online purchases, account creation, and more using the [unique Tab view]({% link _articles/features/auto-fill-browser.md %}).
|
||||
|
||||
{% callout info %}Currently, Autofill for Cards & Identities is **only available for Browser Extensions**. Mobile platforms including Android and iOS do not currently support this type of auto-fill function.{% endcallout %}
|
||||
|
||||
|
||||
@@ -24,7 +24,7 @@ Auto-fill on iOS comes in two flavors:
|
||||
- **Browser App Extension**: Use this option to make Bitwarden auto-fill accessible *only* in Web Browser apps, like Safari, through the Share menu.
|
||||
|
||||
{% callout success %}
|
||||
It is currently not possible to use auto-fill on iOS if the [Vault Timeout Action]({{site.baseurl}}/article/vault-timeout/#vault-timeout-action) for the device is set to **Log Out** and your *only* enabled [Two-step Login Method]({{site.baseurl}}/article/setup-two-step-login) requires NFC (e.g. an NFC YubiKey), as iOS will not allow NFC inputs to interrupt auto-fill workflows.
|
||||
It is currently not possible to use auto-fill on iOS if the [Vault Timeout Action]({{site.baseurl}}/vault-timeout/#vault-timeout-action) for the device is set to **Log Out** and your *only* enabled [Two-step Login Method]({{site.baseurl}}/setup-two-step-login) requires NFC (e.g. an NFC YubiKey), as iOS will not allow NFC inputs to interrupt auto-fill workflows.
|
||||
|
||||
Either change your Vault Timeout Action to **Lock**, or enable another Two-step Login Method.
|
||||
{% endcallout %}
|
||||
@@ -50,7 +50,7 @@ To enable keyboard auto-fill on iOS:
|
||||
|
||||
If a [matching Login]({% link _articles/features/uri-match-detection.md %}) is displayed, tap it to auto-fill. If the {% icon fa-key %} **Passwords** button is displayed, tap it to browse your Vault for the Login item to use. In cases where the {% icon fa-key %} **Passwords** button is displayed, it's probably because there isn't an item in your Vault with a [matching URI]({% link _articles/features/uri-match-detection.md %}).
|
||||
|
||||
{% callout info %}Are you getting a `Biometric unlock disabled pending verification of master password` message? [Learn what to do]({{site.baseurl}}/article/autofill-faqs/#q-what-do-i-do-about-biometric-unlock-disabled-pending-verification-of-master-password).{% endcallout%}
|
||||
{% callout info %}Are you getting a `Biometric unlock disabled pending verification of master password` message? [Learn what to do]({{site.baseurl}}/autofill-faqs/#q-what-do-i-do-about-biometric-unlock-disabled-pending-verification-of-master-password).{% endcallout%}
|
||||
|
||||
### Browser App Extension Auto-fill
|
||||
|
||||
|
||||
@@ -31,7 +31,7 @@ Auto-fill relies on the attribution of URIs to Login items. If you're unfamiliar
|
||||
|
||||
For websites accessed via a web browser, a proper URI will be the `https://..` address of the Login page, for example `https://twitter.com` or `https://twitter.com/login`.
|
||||
|
||||
**For Android Apps**, the [URI scheme]({{site.baseurl}}/article/uri-match-detection/#uri-schemes) always starts with `androidapp://` and is usually a bit different from a typical web browser URI. For example,
|
||||
**For Android Apps**, the [URI scheme]({{site.baseurl}}/uri-match-detection/#uri-schemes) always starts with `androidapp://` and is usually a bit different from a typical web browser URI. For example,
|
||||
|
||||
- The Twitter Android app has the URI `androidapp://com.twitter.android`
|
||||
- The Reddit Android app has the URI `androidapp://com.reddit.frontpage`
|
||||
|
||||
@@ -11,7 +11,7 @@ order: "08"
|
||||
Custom fields, available for any [Vault item type]({% link _articles/account/managing-items.md %}), allow you to store additional well-structured data fields for a Vault item. Custom fields are saved as `Name:Value` pairs, and can be one of three types:
|
||||
|
||||
- **Text**: Field value stores a freeform input (text, numbers, etc.)
|
||||
- **Hidden**: Field value stores freeform input that is hidden from view (particularly useful for Organizations using the [Hide Password access control](https://bitwarden.com/help/article/user-types-access-control/#granular-access-control)).
|
||||
- **Hidden**: Field value stores freeform input that is hidden from view (particularly useful for Organizations using the [Hide Password access control](https://bitwarden.com/help/user-types-access-control/#granular-access-control)).
|
||||
- **Boolean**: Field value stores a boolean value (true/false).
|
||||
|
||||
## Custom Fields for Keys
|
||||
|
||||
@@ -52,7 +52,7 @@ This page will also list any **Saved Passwords** that are being stored by the br
|
||||
|
||||
{% image features/chrome-delete-passwords.png Chrome Saved Passwords %}
|
||||
|
||||
If you haven't already saved these passwords in Bitwarden, [export them]({{site.baseurl}}/article/import-from-chrome/#export-from-chrome) to prepare for future import to Bitwarden. Once exported, you should delete these passwords from the browser's storage.
|
||||
If you haven't already saved these passwords in Bitwarden, [export them]({{site.baseurl}}/import-from-chrome/#export-from-chrome) to prepare for future import to Bitwarden. Once exported, you should delete these passwords from the browser's storage.
|
||||
|
||||
{% endcapture %}
|
||||
{{ chrome | markdownify }}
|
||||
@@ -69,7 +69,7 @@ You should also find out which Logins Firefox has already saved by selecting the
|
||||
|
||||
{% image features/firefox-delete.png Firefox Saved Logins %}
|
||||
|
||||
If you haven't already saved these passwords in Bitwarden, [export them]({{site.baseurl}}/article/import-from-firefox) for future import to Bitwarden. Once exported, you should {% icon fa-trash %} **Remove** these passwords from Firefox.
|
||||
If you haven't already saved these passwords in Bitwarden, [export them]({{site.baseurl}}/import-from-firefox) for future import to Bitwarden. Once exported, you should {% icon fa-trash %} **Remove** these passwords from Firefox.
|
||||
|
||||
{% endcapture %}
|
||||
{{ firefox | markdownify }}
|
||||
|
||||
@@ -8,7 +8,7 @@ tags: [categories, folders, sub-folders]
|
||||
order: "06"
|
||||
---
|
||||
|
||||
Folders are structures used to organize your Personal Vault by gathering together Logins, Cards, Identities, and Secure Notes. Using Folders is a great way to make all Vault items easy to find. Any Vault item can be added to a Folder, including [items shared with you from an Organization]({{site.baseurl}}/article/sharing/).
|
||||
Folders are structures used to organize your Personal Vault by gathering together Logins, Cards, Identities, and Secure Notes. Using Folders is a great way to make all Vault items easy to find. Any Vault item can be added to a Folder, including [items shared with you from an Organization]({{site.baseurl}}/sharing/).
|
||||
|
||||
{% callout success %}
|
||||
Items added to a Folder will still appear in your Vault when {% icon fa-th %} **All Items** is selected from the Filter menu, and deleting a Folder **will not** delete the items in that Folder.
|
||||
@@ -98,7 +98,7 @@ To create a Folder, use the command:
|
||||
bw create folder <foldername>
|
||||
```
|
||||
|
||||
You can edit an existing folder using `bw edit <folderId>` and delete one using `bw delete folder <folderId>`. For more information, refer to our [CLI documentation]({{site.baseurl}}/article/cli).
|
||||
You can edit an existing folder using `bw edit <folderId>` and delete one using `bw delete folder <folderId>`. For more information, refer to our [CLI documentation]({{site.baseurl}}/cli).
|
||||
|
||||
{% endcapture %}
|
||||
{{ cli_info | markdownify}}
|
||||
@@ -108,7 +108,7 @@ You can edit an existing folder using `bw edit <folderId>` and delete one using
|
||||
{% callout info %}
|
||||
If you're a member of an Organization, **Collections** will be shown below your Folders in the Filters menu.
|
||||
|
||||
There are similarities between Folders and Collections. **Folders organize your Personal Vault** (but can include [shared items]({{site.baseurl}}/article/sharing/)) and are unique to you, where Collections are shared between members of Organizations.
|
||||
There are similarities between Folders and Collections. **Folders organize your Personal Vault** (but can include [shared items]({{site.baseurl}}/sharing/)) and are unique to you, where Collections are shared between members of Organizations.
|
||||
{% endcallout %}
|
||||
|
||||
### Nested Folders
|
||||
@@ -213,7 +213,7 @@ Using `edit` will require you to:
|
||||
- Manipulate the JSON object (specifically, the `folderId` attribute) with a [command-line JSON processor like jq](https://stedolan.github.io/jq/){:target="\_blank"}.
|
||||
- Use the `encode` command to encode changes to the JSON object.
|
||||
|
||||
If you're unfamiliar with using any of these parts, refer to our [CLI documentation]({{site.baseurl}}/article/cli).
|
||||
If you're unfamiliar with using any of these parts, refer to our [CLI documentation]({{site.baseurl}}/cli).
|
||||
{% endcallout %}
|
||||
|
||||
{% endcapture %}
|
||||
@@ -222,5 +222,5 @@ If you're unfamiliar with using any of these parts, refer to our [CLI documentat
|
||||
</div>
|
||||
|
||||
{% callout success %}
|
||||
Items [shared with you from an Organization]({{site.baseurl}}/article/sharing/) can be added to your personal Folders, and doing so will only impact how the item appears in your Personal Vault (i.e. adding an item to a Folder won't give anyone access to that Folder, or change whether it's in a Folder in their Vaults).
|
||||
Items [shared with you from an Organization]({{site.baseurl}}/sharing/) can be added to your personal Folders, and doing so will only impact how the item appears in your Personal Vault (i.e. adding an item to a Folder won't give anyone access to that Folder, or change whether it's in a Folder in their Vaults).
|
||||
{% endcallout %}
|
||||
|
||||
@@ -30,7 +30,7 @@ Schemes include:
|
||||
- `androidapp://` references an Android Application Package ID or Name (e.g. `androidapp://com.twitter.android`)
|
||||
|
||||
{% callout success %}
|
||||
An easy way to obtain the proper URI for an Android app is to **use a web browser** to visit the App's page in the Google Play store. The URI for the app will appear in the URL as an `?id=` query parameter (e.g. `https://play.google.com/store/apps/details?id=com.twitter.android`). [Learn more]({{site.baseurl}}/article/blacklisting-uris/#android-app-uris).
|
||||
An easy way to obtain the proper URI for an Android app is to **use a web browser** to visit the App's page in the Google Play store. The URI for the app will appear in the URL as an `?id=` query parameter (e.g. `https://play.google.com/store/apps/details?id=com.twitter.android`). [Learn more]({{site.baseurl}}/blacklisting-uris/#android-app-uris).
|
||||
{% endcallout %}
|
||||
|
||||
## Match Detection Options
|
||||
|
||||
Reference in New Issue
Block a user