mirror of
https://github.com/bitwarden/help
synced 2025-12-10 05:13:43 +00:00
fix double slash (#704)
This commit is contained in:
@@ -45,7 +45,7 @@ To enable Unlock with Biometrics for your Mobile device:
|
||||
2. In your Bitwarden app, open the {% icon fa-cogs %} **Settings** tab.
|
||||
3. Scroll down to the Security section and tap the biometrics option you want to enable. What's available on this screen is determined by your device's hardware capabilities and what you've enabled (**Step 1**), for example:
|
||||
|
||||
{% image /biometrics/ios_faceid.jpeg Enable Face ID in iOS%}
|
||||
{% image biometrics/ios_faceid.jpeg Enable Face ID in iOS%}
|
||||
|
||||
Tapping the option should prompt you to input your biometric (i.e. face or thumb-print). A green `Enabled` status indicator (pictured above) will indicate when Unlock with Biometrics is successfully enabled.
|
||||
|
||||
@@ -67,15 +67,15 @@ To enable Unlock with Biometrics for your Desktop app:
|
||||
2. In your Bitwarden app, open your Settings (on Windows, **File** → **Settings**) (on macOS, **Bitwarden** → **Preferences**).
|
||||
3. Scroll down to the Security section and select the biometrics option you want to enable. What's available on this screen is determined by your device's hardware capabilities and what you've turned on (**Step 1**), for example:
|
||||
|
||||
{% image /biometrics/windows.png Unlock with Windows Hello %}
|
||||
{% image biometrics/windows.png Unlock with Windows Hello %}
|
||||
|
||||
Once enabled, the Desktop app will automatically prompt for your biometric method to unlock your Vault. You can turn off automatic-prompting from the same menu using the **Do not prompt...** option:
|
||||
|
||||
{% image /biometrics/auto-off.png Unlock with Windows Hello %}
|
||||
{% image biometrics/auto-off.png Unlock with Windows Hello %}
|
||||
|
||||
Regardless of your auto-prompt selection, a new button will be presented on the Unlock screen for unlocking your Vault:
|
||||
|
||||
{% image /biometrics/hello-unlock.png Unlock with Windows Hello %}
|
||||
{% image biometrics/hello-unlock.png Unlock with Windows Hello %}
|
||||
|
||||
{% endcapture %}
|
||||
{{ desktop_info | markdownify}}
|
||||
@@ -129,7 +129,7 @@ To enable Unlock with Biometrics for your Browser Extension:
|
||||
|
||||
Once enabled, a new button will be presented on the Unlock screen:
|
||||
|
||||
{% image /biometrics/be-bio-unlock.png Unlock with Biometrics %}
|
||||
{% image biometrics/be-bio-unlock.png Unlock with Biometrics %}
|
||||
|
||||
{% callout success %}
|
||||
Your Desktop app needs to be **Logged In** but does not need to be **Unlocked** to unlock a Browser Extension with biometrics.
|
||||
|
||||
@@ -32,7 +32,7 @@ Effectively managing the items in your Vault is key to making sure that you secu
|
||||
|
||||
Login items are most often used to store username and password combinations, and support [TOTP seeds]({{site.baseurl}}/article/authenticator-keys/) for Premium users. Whatever plan you're on, we recommend giving every Login a [URI for easy auto-fill]({{site.baseurl}}/article/uri-match-detection):
|
||||
|
||||
{% image /manage-items/login-item.png Login Vault Item %}
|
||||
{% image manage-items/login-item.png Login Vault Item %}
|
||||
|
||||
{% endcapture %}
|
||||
{{ logins | markdownify }}
|
||||
@@ -43,7 +43,7 @@ Login items are most often used to store username and password combinations, and
|
||||
|
||||
Card items can be used to store credit or debit card information:
|
||||
|
||||
{% image /manage-items/card-item.png Card Vault Item %}
|
||||
{% image manage-items/card-item.png Card Vault Item %}
|
||||
|
||||
{% endcapture %}
|
||||
{{ cards | markdownify }}
|
||||
@@ -54,7 +54,7 @@ Card items can be used to store credit or debit card information:
|
||||
|
||||
Identities can be used to store billing info, mailing info, or anything else you might need to have access to when filling out online forms:
|
||||
|
||||
{% image /manage-items/identity-item.png Identity Vault Item %}
|
||||
{% image manage-items/identity-item.png Identity Vault Item %}
|
||||
|
||||
{% endcapture %}
|
||||
{{ identities | markdownify }}
|
||||
@@ -65,7 +65,7 @@ Identities can be used to store billing info, mailing info, or anything else you
|
||||
|
||||
Secure Notes can be used to store encrypted freeform text for anything you want protected:
|
||||
|
||||
{% image /manage-items/note-item.png Secure Note Vault Item %}
|
||||
{% image manage-items/note-item.png Secure Note Vault Item %}
|
||||
|
||||
{% endcapture %}
|
||||
{{ notes | markdownify }}
|
||||
@@ -103,7 +103,7 @@ You can add, edit, and delete Vault items from any Bitwarden client application:
|
||||
{% capture wv %}
|
||||
### Web Vault
|
||||
|
||||
{% image /manage-items/manage-webvault.png Manage an Item %}
|
||||
{% image manage-items/manage-webvault.png Manage an Item %}
|
||||
|
||||
{% endcapture %}
|
||||
{{ wv | markdownify }}
|
||||
@@ -112,7 +112,7 @@ You can add, edit, and delete Vault items from any Bitwarden client application:
|
||||
{% capture be_sync %}
|
||||
### Browser Extensions
|
||||
|
||||
{% image /manage-items/manage-be.png Manage an Item %}
|
||||
{% image manage-items/manage-be.png Manage an Item %}
|
||||
|
||||
{% endcapture %}
|
||||
{{ be_sync | markdownify }}
|
||||
@@ -121,9 +121,9 @@ You can add, edit, and delete Vault items from any Bitwarden client application:
|
||||
{% capture mob_sync%}
|
||||
### Mobile Apps
|
||||
|
||||
{% image /manage-items/manage-mobile-1.png Add or Open an Item %}
|
||||
{% image manage-items/manage-mobile-1.png Add or Open an Item %}
|
||||
|
||||
{% image /manage-items/manage-mobile-2.png Manage an Item %}
|
||||
{% image manage-items/manage-mobile-2.png Manage an Item %}
|
||||
|
||||
|
||||
{% endcapture %}
|
||||
@@ -133,7 +133,7 @@ You can add, edit, and delete Vault items from any Bitwarden client application:
|
||||
{% capture desk_sync%}
|
||||
### Desktop Apps
|
||||
|
||||
{% image /manage-items/manage-desktop.png Manage an Item %}
|
||||
{% image manage-items/manage-desktop.png Manage an Item %}
|
||||
|
||||
{% endcapture %}
|
||||
{{ desk_sync | markdownify }}
|
||||
@@ -159,7 +159,7 @@ Deleted items are sent to the Trash, where they remain for 30 days after deletio
|
||||
|
||||
In the Trash, you can **Restore** an item to your Vault or **Permanently Delete** it prior to the 30-day waiting period:
|
||||
|
||||
{% image /manage-items/item-trash-restore-delete.png The Trash %}
|
||||
{% image manage-items/item-trash-restore-delete.png The Trash %}
|
||||
|
||||
### Protect Individual Items
|
||||
|
||||
@@ -169,7 +169,7 @@ For any given Vault item, you can activate the **Master password re-prompt** opt
|
||||
Master password re-prompt **is not** an encryption mechanism. This feature is an interface-only guardrail that a sophisticated user may find ways to work around. We recommend **never** leaving your Vault unlocked when unattended or on a shared workstation.
|
||||
{% endcallout %}
|
||||
|
||||
{% image /manage-items/reprompt.gif Master Password Reprompt %}
|
||||
{% image manage-items/reprompt.gif Master Password Reprompt %}
|
||||
|
||||
## Share Vault Items
|
||||
|
||||
|
||||
@@ -160,7 +160,7 @@ It may take up to 15 minutes for permissions for your application to properly pr
|
||||
If you get the error message `Resource <user id> does not exist or one of its queried reference-property objects are not present`, you'll need to permanently delete or restore the user(s) with `<user id>`. **Please note**, this was fixed in a recent version of Directory Connector. Update your application if you're still experiencing this error.
|
||||
{% endcallout %}
|
||||
|
||||
{% image /directory-connector/okta/dc-okta-test.png Test sync results %}
|
||||
{% image directory-connector/okta/dc-okta-test.png Test sync results %}
|
||||
|
||||
## Start Automatic Sync
|
||||
|
||||
|
||||
@@ -18,7 +18,7 @@ Directory Connector will issue invitations to synced users, however it will not
|
||||
Directory Connector functionality is available to **Teams** and **Enterprise** Organizations. To use Directory Connector, you must have access to your [Organization API Key]({{site.baseurl}}/article/public-api/#authentication) which can only be retrieved by an [Organization Owner]({{site.baseurl}}/article/user-types-access-control/) and securely shared using [Bitwarden Send]({{site.baseurl}}/article/about-send/).
|
||||
{% endcallout %}
|
||||
|
||||
{% image /directory-connector/dc-diagram.png %}
|
||||
{% image directory-connector/dc-diagram.png %}
|
||||
|
||||
A Directory Connector sync operation can be run on-demand or automatically on a configured interval. Directory Connector applications can be installed as an agent on the server that hosts your directory, an administrator's workstation, or any other desktop device that can access the source directory.
|
||||
|
||||
|
||||
@@ -163,7 +163,7 @@ exclude:Group A,Group B
|
||||
|
||||
To test whether Directory Connector will successfully connect to your directory and return the desired users and groups, navigate to the **Dashboard** tab and select the **Test Now** button. If successful, users and groups will be printed to the Directory Connector window according to the specified [Sync Options](#configure-sync-options) and [Filters](#specify-sync-filters):
|
||||
|
||||
{% image /directory-connector/okta/dc-okta-test.png Test sync results %}
|
||||
{% image directory-connector/okta/dc-okta-test.png Test sync results %}
|
||||
|
||||
## Start Automatic Sync
|
||||
|
||||
|
||||
@@ -120,7 +120,7 @@ To filter a sync for all entries that have `objectClass=user` and `cn` (common n
|
||||
|
||||
To test whether Directory Connector will successfully connect to your Directory and return the desired users and groups, navigate to the **Dashboard** tab and select the **Test Now** button. If successful, users and groups will be printed to the Directory Connector window according the specified [Sync Options](#configure-sync-options) and [Filters](#specify-sync-filters):
|
||||
|
||||
{% image /directory-connector/okta/dc-okta-test.png Test sync results %}
|
||||
{% image directory-connector/okta/dc-okta-test.png Test sync results %}
|
||||
|
||||
## Start Automatic Sync
|
||||
|
||||
|
||||
@@ -119,7 +119,7 @@ To use only the `filter` parameter, prefix the query with a pipe (`|`):
|
||||
|
||||
To test whether Directory Connector will successfully connect to your directory and return the desired users and groups, navigate to the **Dashboard** tab and select the **Test Now** button. If successful, users and groups will be printed to the Directory Connector window according to specified [Sync Options](#configure-sync-options) and [Filters](#specify-sync-filters):
|
||||
|
||||
{% image /directory-connector/okta/dc-okta-test.png Test sync results%}
|
||||
{% image directory-connector/okta/dc-okta-test.png Test sync results%}
|
||||
|
||||
## Start Automatic Sync
|
||||
|
||||
|
||||
@@ -91,7 +91,7 @@ exclude:Role A,Role B
|
||||
|
||||
To test whether Directory Connector will successfully connect to your directory and return the desired users and groups, navigate to the **Dashboard** tab and select the **Test Now** button. If successful, users and groups will be printed to the Directory Connector window according to specified [Sync Options](#configure-sync-options) and [Filters](#specify-sync-filters):
|
||||
|
||||
{% image /directory-connector/okta/dc-okta-test.png Test sync results %}
|
||||
{% image directory-connector/okta/dc-okta-test.png Test sync results %}
|
||||
|
||||
## Start Automatic Sync
|
||||
|
||||
|
||||
@@ -38,7 +38,7 @@ For help selecting the right Bitwarden plan for you, refer to [What Plan is Righ
|
||||
|
||||
**A:** Login to your [Web Vault](https://vault.bitwarden.com) and open your Organization. In your Organization's **Settings** tab, select the **Subscription** from the left menu:
|
||||
|
||||
{% image /organizations/org-subscription-screen-overlay-addseats.png Add or Remove seats %}
|
||||
{% image organizations/org-subscription-screen-overlay-addseats.png Add or Remove seats %}
|
||||
|
||||
You can add or remove seats from your Organization at any time. The cost will be automatically pro-rated and debited or credited accordingly.
|
||||
|
||||
|
||||
@@ -59,7 +59,7 @@ Like with any software, running old versions may present a security risk.
|
||||
**A:** To unshare an item:
|
||||
1. Clone the item back to your Personal Vault by navigating to your Organization Vault and selecting **Clone** from the gear dropdown for the item you want to clone. Only users with User Type **Admin** or higher can only clone items into their Personal Vault by changing the **Ownership** setting.
|
||||
|
||||
{% image /organizations/clone-org-item.png %}
|
||||
{% image organizations/clone-org-item.png %}
|
||||
2. Delete the item from the Organization Vault by selecting **Delete** from the same gear dropdown.
|
||||
|
||||
Alternatively, you can unshare items by moving them to a different Collection with higher Access Control restrictions.
|
||||
|
||||
@@ -18,7 +18,7 @@ Additionally, creation of file Sends requires your Email Address to be verified.
|
||||
|
||||
**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 %}
|
||||
{% image send/send-ff-popout.png The popout icon %}
|
||||
|
||||
### Q: Why are Sends missing from my Send view?
|
||||
|
||||
|
||||
@@ -31,6 +31,6 @@ This article contains Frequently Asked Questions (FAQs) regarding **Two-step Log
|
||||
|
||||
2. You may have previously checked the **Remember me** checkbox on a device when accessing your Vault using Two-step Login.
|
||||
|
||||
{% image /two-step/twostep-remember.png Remember me option %}
|
||||
{% image two-step/twostep-remember.png Remember me option %}
|
||||
|
||||
If you used the **Remember me** option, you will need to **Deauthorize Sessions** from your Web Vault (**Settings** → **My Account**) for that device to continue asking for your Two-step Login method.
|
||||
|
||||
@@ -47,7 +47,7 @@ Once setup, Bitwarden Authenticator will continuously generate 6-digit TOTPs rot
|
||||
|
||||
Bitwarden Mobile applications and Browser Extensions will automatically copy the TOTP code to your device's clipboard after Auto-fill, unless the **Enable Auto-fill on Page Load** option is active. Paste from your clipboard immediately after successful Auto-fill to use your TOTP or (if you're using a Browser Extension) use the context menu:
|
||||
|
||||
{% image /two-step/be-totpcopy.png Browser Extension Context Menu %}
|
||||
{% image two-step/be-totpcopy.png Browser Extension Context Menu %}
|
||||
|
||||
{% callout success %}Automatic TOTP copying can be toggled off under **Settings** → **Options** → **Disable Automatic TOTP Copy**.{% endcallout %}
|
||||
|
||||
|
||||
@@ -18,7 +18,7 @@ Bitwarden Browser Extensions have a unique **Tab** view, which automatically det
|
||||
|
||||
When a Vault item has a corresponding URI, the Bitwarden icon will overlay a badge counter reporting the number of Vault items for that web page (*pictured below*).
|
||||
|
||||
{% image /getting-started/browserext/browserext-tab.png Badge Counter %}
|
||||
{% image getting-started/browserext/browserext-tab.png Badge Counter %}
|
||||
|
||||
{% callout success %}
|
||||
If you want, you can disable the badge counter using a toggle in the {% icon fa-cogs %} **Settings** → **Options** menu:
|
||||
@@ -40,7 +40,7 @@ Currently unavailable in the Safari Browser Extension.
|
||||
|
||||
Without opening your Browser Extension, you can right-click on the username or password input field and use the **Bitwarden** → **Auto-fill** option. Your Vault must be unlocked for this option to be available.
|
||||
|
||||
{% image /getting-started/browserext/browserext-context.png %}
|
||||
{% image getting-started/browserext/browserext-context.png %}
|
||||
|
||||
## Using Keyboard Shortcuts
|
||||
|
||||
|
||||
@@ -63,7 +63,7 @@ Prefixing your custom field's name with `regex=` allows you to perform [regular
|
||||
|
||||
Follow this procedure to correctly configure a custom field for auto-fill. This example uses Google Chrome for its Developer Tools.
|
||||
|
||||
{% image /features/custom-fields/custom_field.gif %}
|
||||
{% image features/custom-fields/custom_field.gif %}
|
||||
|
||||
1. On the webpage that matches the Login item's URI, right-click the field you want to auto-fill to and select **Inspect**.
|
||||
|
||||
@@ -71,9 +71,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).
|
||||
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 Select custom field type%}
|
||||
{% image features/custom-fields/types.png Select custom field type%}
|
||||
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.
|
||||
|
||||
{% image /features/custom-fields/custom-field-eg.png Custom field example %}
|
||||
{% image features/custom-fields/custom-field-eg.png Custom field example %}
|
||||
6. Save the Vault item.
|
||||
|
||||
@@ -24,22 +24,22 @@ Designate any Vault item as a **Favorite** when you initially create it, or at a
|
||||
|
||||
On the Add Item or Edit Item screen, select the {% icon fa-star %} **Star** icon in the bottom-right corner and **Save** the item:
|
||||
|
||||
{% image /favorites/favorite_webvault_cropped.gif %}
|
||||
{% image favorites/favorite_webvault_cropped.gif %}
|
||||
|
||||
### In Browser Extensions
|
||||
|
||||
On the Add Item or Edit Item screen, check the **Favorite** checkbox and **Save** the item:
|
||||
|
||||
{% image /favorites/favorite_extension_cropped.gif %}
|
||||
{% image favorites/favorite_extension_cropped.gif %}
|
||||
|
||||
### In Desktop Applications
|
||||
|
||||
On the Add Item or Edit Item screen, check the **Favorite** checkbox and **Save** the item:
|
||||
|
||||
{% image /favorites/favorite_desktop_cropped.gif %}
|
||||
{% image favorites/favorite_desktop_cropped.gif %}
|
||||
|
||||
### In Mobile Apps
|
||||
|
||||
On the Add Item or Edit Item screen, toggle the **Favorite** switch and **Save** the item:
|
||||
|
||||
{% image /favorites/favorite_mobile.gif %}
|
||||
{% image favorites/favorite_mobile.gif %}
|
||||
|
||||
@@ -42,7 +42,7 @@ Folders can be created, renamed, and deleted from any Bitwarden client applicati
|
||||
|
||||
To create a Folder, select the {% icon fa-plus %} **Add** icon in the Folders list:
|
||||
|
||||
{% image /manage-items/folder-add-web.png Add a folder %}
|
||||
{% image manage-items/folder-add-web.png Add a folder %}
|
||||
|
||||
Once created, you can **rename or delete** a folder at any time using the hover-over {% icon fa-pencil %} **Pencil** icon.
|
||||
|
||||
@@ -55,7 +55,7 @@ Once created, you can **rename or delete** a folder at any time using the hover-
|
||||
|
||||
To create a Folder, select the {% icon fa-cogs %} **Settings** menu, select the **Folders** option, and tap/select the {% icon fa-plus %} **Add** icon:
|
||||
|
||||
{% image /manage-items/folder-add-extension.gif Add a folder %}
|
||||
{% image manage-items/folder-add-extension.gif Add a folder %}
|
||||
|
||||
Once created, you can **rename or delete** a folder at any time from the same menu by selecting an existing folder.
|
||||
|
||||
@@ -68,7 +68,7 @@ Once created, you can **rename or delete** a folder at any time from the same me
|
||||
|
||||
To create a Folder, select the {% icon fa-plus %} **Add** icon in the Folders list:
|
||||
|
||||
{% image /manage-items/folder-add-desk.png Add a folder %}
|
||||
{% image manage-items/folder-add-desk.png Add a folder %}
|
||||
|
||||
Once created, you can **rename or delete** a folder at any time using the hover-over {% icon fa-pencil %} **Pencil** icon.
|
||||
|
||||
@@ -81,7 +81,7 @@ Once created, you can **rename or delete** a folder at any time using the hover-
|
||||
|
||||
To create a Folder, tap the {% icon fa-cogs %} **Settings** menu, tap the **Folders** option, and tap/select the {% icon fa-plus %} **Add** icon:
|
||||
|
||||
{% image /manage-items/folder-add-mob.jpeg Add a folder %}
|
||||
{% image manage-items/folder-add-mob.jpeg Add a folder %}
|
||||
|
||||
Once created, you can **rename or delete** a folder at any time from the same menu by tapping an existing folder.
|
||||
|
||||
@@ -119,7 +119,7 @@ Folders can be "nested" in order to logically organize them within your Vault. T
|
||||
Searching inside a "parent" Folder will not include items in Folders nested inside it as potential search results. For more information, see [Search your Vault]({% link _articles/features/searching-vault.md %}).
|
||||
{% endcallout %}
|
||||
|
||||
{% image /manage-items/subfolders.png Nested folders %}
|
||||
{% image manage-items/subfolders.png Nested folders %}
|
||||
|
||||
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`.
|
||||
|
||||
@@ -169,7 +169,7 @@ From the Web Vault, you can either:
|
||||
|
||||
Open the Vault item you want to move, select the **Folders** dropdown, and choose the folder to move the item to:
|
||||
|
||||
{% image /manage-items/folder-move-be.png Move item to a folder %}
|
||||
{% image manage-items/folder-move-be.png Move item to a folder %}
|
||||
|
||||
{% endcapture %}
|
||||
{{ browser_extension | markdownify}}
|
||||
@@ -180,7 +180,7 @@ Open the Vault item you want to move, select the **Folders** dropdown, and choos
|
||||
|
||||
Open the Vault item you want to move, select the **Folders** dropdown, and choose the folder to move the item to:
|
||||
|
||||
{% image /manage-items/folder-move-desk.png Move item to a folder %}
|
||||
{% image manage-items/folder-move-desk.png Move item to a folder %}
|
||||
|
||||
{% endcapture %}
|
||||
{{ desktop_info | markdownify}}
|
||||
@@ -191,7 +191,7 @@ Open the Vault item you want to move, select the **Folders** dropdown, and choos
|
||||
|
||||
Open the Vault item you want to move, tap the **Folders** dropdown, and choose the folder to move the item to:
|
||||
|
||||
{% image /manage-items/folder-move-mob.jpeg Move item to a folder %}
|
||||
{% image manage-items/folder-move-mob.jpeg Move item to a folder %}
|
||||
|
||||
{% endcapture %}
|
||||
{{ mobile_info | markdownify}}
|
||||
|
||||
@@ -27,7 +27,7 @@ Complete the following steps to view any Vault Health Reports for your **Organiz
|
||||
1. Log in to the [Web Vault](https://vault.bitwarden.com){:target-"\_blank"} and open your Organization.
|
||||
2. In your Organization, open the **Tools** tab.
|
||||
|
||||
{% image /features/reports/tools-section.png Organization Reports %}
|
||||
{% image features/reports/tools-section.png Organization Reports %}
|
||||
3. Select a report from the **Reports** section of the left menu.
|
||||
|
||||
## Available Reports
|
||||
@@ -74,7 +74,7 @@ Two-factor Authentication (2FA) is an important security step that helps secure
|
||||
|
||||
Once identified, setup 2FA using the `Instructions` hyperlink for each offending item:
|
||||
|
||||
{% image /features/reports/inactive-2fa.png %}
|
||||
{% image features/reports/inactive-2fa.png %}
|
||||
|
||||
### Data Breach Report (*Personal Vaults only*)
|
||||
|
||||
|
||||
@@ -18,7 +18,7 @@ The potential results available to any search operation is dependent on what is
|
||||
|
||||
The placeholder text in the search box will transform to indicate the current search location:
|
||||
|
||||
{% image /manage-items/search.png Search a Folder%}
|
||||
{% image manage-items/search.png Search a Folder%}
|
||||
|
||||
## Basic Search
|
||||
|
||||
|
||||
@@ -11,13 +11,13 @@ order: 01
|
||||
|
||||
We're thrilled to be a part of your secure password management journey. To create a Bitwarden account, click the **Get Started** button on our homepage, or click [**here**](https://vault.bitwarden.com/#/register).
|
||||
|
||||
{% image /getting-started/get-started-homepage-overlay.png Bitwarden Homepage%}
|
||||
{% image getting-started/get-started-homepage-overlay.png Bitwarden Homepage%}
|
||||
|
||||
## Create Account Screen
|
||||
|
||||
Once you've clicked the link, the following screen will appear. Fill out all fields (*Master Password Hint* is optional) and click **Submit** when you're finished.
|
||||
|
||||
{% image /getting-started/create-account-screen-overlay.png Create Account screen%}
|
||||
{% image getting-started/create-account-screen-overlay.png Create Account screen%}
|
||||
|
||||
## Verify Your Email
|
||||
|
||||
|
||||
@@ -24,7 +24,7 @@ Bitwarden Browser Extensions integrate password management directly into your fa
|
||||
**The Safari Browser Extension is packaged with the Desktop Application**, available for download from the App Store. For more information, see [Safari App Extension]({% link _articles/account/install-safari-app-extension.md %}).
|
||||
{% endcallout %}
|
||||
|
||||
{% image /getting-started/browserext/browserext-vault.png Bitwarden Browser Extension in Google Chrome %}
|
||||
{% image getting-started/browserext/browserext-vault.png Bitwarden Browser Extension in Google Chrome %}
|
||||
|
||||
## Explore your Vault
|
||||
|
||||
@@ -56,7 +56,7 @@ For more information, see [Folders]({% link _articles/features/folders.md %}) an
|
||||
|
||||
Any time you log in to a website that doesn't already have a Login item saved for it, Bitwarden will offer to remember the login information for you:
|
||||
|
||||
{% image /getting-started/browserext/browserext-add.png %}
|
||||
{% image getting-started/browserext/browserext-add.png %}
|
||||
|
||||
Selecting **Yes, Save Now** will automatically add a Login item to your Vault with the entered username, password, and URI. If you're unfamiliar with using URIs, see [Using URIs]({% link _articles/features/uri-match-detection.md %}).
|
||||
|
||||
@@ -68,7 +68,7 @@ You can disable this banner by selecting the **Disable Add Login Notification**
|
||||
|
||||
You can launch a website directly from the Bitwarden Browser Extension by selecting the {% icon fa-share-square %} **Launch** button in any Vault item with a valid URI. If you're unfamiliar with using URIs, see [Using URIs]({% link _articles/features/uri-match-detection.md %}).
|
||||
|
||||
{% image /getting-started/browserext/browserext-launch.png %}
|
||||
{% image getting-started/browserext/browserext-launch.png %}
|
||||
|
||||
## Auto-fill Login Information
|
||||
|
||||
@@ -76,7 +76,7 @@ Bitwarden Browser Extensions have a unique **Tab** view, which automatically det
|
||||
|
||||
When a Vault item has a corresponding URI, the Bitwarden icon will overlay a notification bubble reporting the number of Vault items for that web page (*pictured below*).
|
||||
|
||||
{% image /getting-started/browserext/browserext-tab.png %}
|
||||
{% image getting-started/browserext/browserext-tab.png %}
|
||||
|
||||
Simply clicking on the Vault item inside the Browser Extension will auto-fill login information to the detected input fields.
|
||||
|
||||
|
||||
@@ -11,7 +11,7 @@ order: 05
|
||||
|
||||
Bitwarden's Desktop App brings a full Vault experience straight out of your browser and into your desktop. Using a 3-column layout, the Bitwarden Desktop App is designed to help you quickly locate the Vault item you want to use or edit:
|
||||
|
||||
{% image /getting-started/desktop-app2.png Bitwarden Desktop App%}
|
||||
{% image getting-started/desktop-app2.png Bitwarden Desktop App%}
|
||||
|
||||
- The left-most column contains your **Vault Filters**. Vault items are sorted into Types (*Login*, *Card*, *Identity*, or *Secure Note*), Folders, and Collections if you're a member of an Organization.
|
||||
|
||||
@@ -81,13 +81,13 @@ Windows Hello must be enabled on your computer **before** it can be enabled in B
|
||||
1. In your Desktop App, select **File** → **Settings**.
|
||||
2. In the Security section, an **Unlock with Windows Hello** option will appear if Windows Hello is supported and enabled on your computer:
|
||||
|
||||
{% image /biometrics/windows.png Windows unlock options %}
|
||||
{% image biometrics/windows.png Windows unlock options %}
|
||||
|
||||
Check the **Unlock with Windows Hello** option to proceed. Your computer will prompt you to input your biometric.
|
||||
|
||||
Once enabled, a new button will be presented on the Unlock screen. Selecting **Unlock with Windows Hello** will prompt you to input your biometric to initiate unlock.
|
||||
|
||||
{% image /biometrics/hello-unlock.png Unlock with Windows Hello %}
|
||||
{% image biometrics/hello-unlock.png Unlock with Windows Hello %}
|
||||
|
||||
### Start Bitwarden Automatically
|
||||
|
||||
@@ -147,13 +147,13 @@ Touch ID must be enabled on your computer **before** it can be enabled in Bitwar
|
||||
1. From the macOS menu bar, select **Bitwarden** → **Preferences**.
|
||||
2. In the Security section, an **Unlock with Touch ID** option will appear if Touch ID is supported and enabled on your computer:
|
||||
|
||||
{% image /getting-started/macos-bio1.png macOS unlock options%}
|
||||
{% image getting-started/macos-bio1.png macOS unlock options%}
|
||||
|
||||
Check the **Unlock with Touch ID** checkbox to proceed. Your computer will prompt your to input your fingerprint to confirm.
|
||||
|
||||
Once enabled, a new button will be presented on the Unlock screen. Selecting **Unlock with Touch ID** will prompt you to input your fingerprint and initiate unlock once authenticated.
|
||||
|
||||
{% image /getting-started/macos-bio2.png Unlock with Touch ID %}
|
||||
{% image getting-started/macos-bio2.png Unlock with Touch ID %}
|
||||
|
||||
### Start Bitwarden Automatically
|
||||
|
||||
|
||||
@@ -14,7 +14,7 @@ redirect_from:
|
||||
|
||||
Bitwarden's Mobile App lets you take your password manager on the go. Download Bitwarden from the App Store or Google Play Store, or by navigating to [get.bitwarden.com](https://get.bitwarden.com) on any device.
|
||||
|
||||
{% image /getting-started/bitwarden-ios-trio.png Bitwarden on Android and iOS%}
|
||||
{% image getting-started/bitwarden-ios-trio.png Bitwarden on Android and iOS%}
|
||||
|
||||
Bitwarden's Mobile App is available for iOS and Android. For help getting started, select which device you use:
|
||||
|
||||
@@ -88,7 +88,7 @@ Setup Auto-fill to automatically enter logins from your Android device to a Web
|
||||
|
||||
You can launch a website directly from the Bitwarden Mobile App by selecting the {% icon fa-share-square %} **Launch** button in any Vault item with a valid URI. If you're unfamiliar with using URIs, see [Using URIs]({% link _articles/features/uri-match-detection.md %}).
|
||||
|
||||
{% image /getting-started/mobile-launch.png %}
|
||||
{% image getting-started/mobile-launch.png %}
|
||||
|
||||
### Unlock with Biometrics
|
||||
|
||||
@@ -109,7 +109,7 @@ Once you've setup [Auto-fill](#setup-auto-fill) and [Biometrics](#unlock-with-bi
|
||||
1. Tap the Email/Username or Password input box in the app or website.
|
||||
2. Depending on which auto-fill option your device uses, tap the available overlay:
|
||||
|
||||
{% image /getting-started/autofill-android-2.png Android Auto-fill varieties %}
|
||||
{% image getting-started/autofill-android-2.png Android Auto-fill varieties %}
|
||||
3. You'll be prompted for your Face ID or Fingerprint. If you aren't using [Biometrics](#unlock-with-biometrics), enter your Master Password.
|
||||
4. If you've connected a login to this website or app using the [URI field](#create-items), that login will appear in this window. If you haven't, tap {% icon fa-search %} **Search** to find it.
|
||||
|
||||
@@ -185,7 +185,7 @@ When you create new logins, make sure you enter a website in the [URI field](#cr
|
||||
|
||||
You can launch a website directly from the Bitwarden Mobile App by selecting the {% icon fa-share-square %} **Launch** button in any Vault item with a valid URI. If you're unfamiliar with using URIs, see [Using URIs]({% link _articles/features/uri-match-detection.md %}).
|
||||
|
||||
{% image /getting-started/mobile-launch.png %}
|
||||
{% image getting-started/mobile-launch.png %}
|
||||
|
||||
### Unlock with Biometrics
|
||||
|
||||
@@ -206,7 +206,7 @@ Once you've setup [Auto-fill](#setup-auto-fill) and [Biometrics](#unlock-with-bi
|
||||
1. Tap the Email/Username or Password input box in the app or website.
|
||||
2. Above your keyboard, tap **Passwords**.
|
||||
|
||||
{% image /getting-started/autofill-ios.png %}
|
||||
{% image getting-started/autofill-ios.png %}
|
||||
3. You'll be prompted for your Face ID or Touch ID. If you aren't using [Biometrics](#unlock-with-biometrics), enter your Master Password.
|
||||
4. If you've connected a login to this website or app using the [URI field](#create-items), that login will appear in this window. If you haven't, tap {% icon fa-search %} **Search** to find it.
|
||||
|
||||
|
||||
@@ -21,7 +21,7 @@ This article will help you get started with a **free 2-person Organization** so
|
||||
|
||||
Bitwarden Organizations relate users and Vault items together for [secure sharing]({{site.baseurl}}/article/share-to-a-collection/) of Logins, Notes, Cards, and Identities. Organizations could be a family, team, company or any group of people that needs to securely share data. Organizations have a unique Vault, where [administrators]({{site.baseurl}}/article/user-types-access-control/) can manage the Organization's items, users, and settings:
|
||||
|
||||
{% image /organizations/org-vault-admin.png Organization Vault %}
|
||||
{% image organizations/org-vault-admin.png Organization Vault %}
|
||||
|
||||
#### Comparing Organizations with Premium
|
||||
|
||||
@@ -45,7 +45,7 @@ Bitwarden provides applications on lots of devices, including Browser Extensions
|
||||
|
||||
Once your account is created, log in to your [Web Vault](https://vault.bitwarden.com){:target="\_blank"} and verify your account's email address to unlock access to all features:
|
||||
|
||||
{% image /getting-started/verify-email.png Send Verification Email %}
|
||||
{% image getting-started/verify-email.png Send Verification Email %}
|
||||
|
||||
### Sign up for Bitwarden again
|
||||
|
||||
@@ -70,13 +70,13 @@ To setup your Organization:
|
||||
|
||||
Once created, you'll land in your Organization Vault, which is the central hub for all things sharing and Organization administration. As the [Organization Owner]({{site.baseurl}}/article/user-types-access-control/), you'll be able to see your **Vault**, to **Manage** users and [Collections](#get-to-know-collections), to use some Bitwarden **Tools**, and to configure your Organization's **Settings**:
|
||||
|
||||
{% image /getting-started/org-vault.png Organization Vault %}
|
||||
{% image getting-started/org-vault.png Organization Vault %}
|
||||
|
||||
### Get to know Collections
|
||||
|
||||
Collections are an important part of a Bitwarden Organization; they represent the logical grouping of shared Vault items that [belong to your Organization](#shared-items). Your Organization comes pre-loaded with a **Default Collection** and an **Unassigned** tag. With a free Organization, you can create up to 2 Collections using the **Manage** tab:
|
||||
|
||||
{% image /getting-started/collections.png Collections %}
|
||||
{% image getting-started/collections.png Collections %}
|
||||
|
||||
{% callout success %}
|
||||
In a lot of ways, Collections are like the [Folders]({{site.baseurl}}/article/folders/) you might use to organize your Personal Vault. A key difference is that items that [belong to your Organization](#shared-items) **must be included in at least 1 Collection**.
|
||||
@@ -92,7 +92,7 @@ As the Organization Owner, invite a new member:
|
||||
|
||||
1. In your Organization Vault, open the **Manage** tab and select the {% icon fa-plus %} **Invite User** button:
|
||||
|
||||
{% image /organizations/org-people-invite.png %}
|
||||
{% image organizations/org-people-invite.png %}
|
||||
2. Enter the **Email** of your second member, which should match the email they [signed up for Bitwarden](#sign-up-for-bitwarden-again) with. You can also choose the [User Type]({{site.baseurl}}/article/user-types-access-control/#user-types) and [Access Controls]({{site.baseurl}}/article/user-types-access-control/#access-control) assigned to this user, including which [Collections](#get-to-know-collections) they can access.
|
||||
3. Select **Save** to send the invitation to the designated email address.
|
||||
|
||||
@@ -137,7 +137,7 @@ Part of the magic of Bitwarden Organizations is that items that belong to you an
|
||||
|
||||
You probably don't have a [shared item](#share-a-login) yet, but when you do it will be displayed in your Vault with a {% icon fa-share-alt %} **Shared** icon:
|
||||
|
||||
{% image /organizations/collection-shared-item.png Shared Item icon %}
|
||||
{% image organizations/collection-shared-item.png Shared Item icon %}
|
||||
|
||||
Shared items are **owned** by the Organization. This means that anyone with permission can alter the item or delete it, which would remove it from your Vault as well.
|
||||
|
||||
|
||||
@@ -13,7 +13,7 @@ order: 02
|
||||
|
||||
Your Web Vault is accessible from any modern web browser by navigating to [vault.bitwarden.com](https://vault.bitwarden.com){:target=\_blank}.
|
||||
|
||||
{% image /getting-started/webvault.png The Bitwarden Web Vault %}
|
||||
{% image getting-started/webvault.png The Bitwarden Web Vault %}
|
||||
|
||||
When your first log in to your Web Vault, you'll land on the **My Vault** view. This space will list all your Vault items, including Logins, Cards, Identities, and Secure Notes. To learn about these different types of items, see [Vault Items]({% link _articles/account/managing-items.md %}).
|
||||
|
||||
@@ -44,7 +44,7 @@ To add a new Login item:
|
||||
|
||||
For most Login items, this should be the URL a webpage (e.g. `https://twitter.com/login`). If you don't know what URL to use, navigate to the website's login screen and copy it from your address bar.
|
||||
|
||||
{% image /getting-started/gs-uri.png Finding a URI %}
|
||||
{% image getting-started/gs-uri.png Finding a URI %}
|
||||
6. From the **Folder** dropdown menu, select the name of the Folder you want to add this item to (e.g. the `Social Media Logins` folder we created earlier).
|
||||
|
||||
Select the {% icon fa-star-o %} **Favorite** icon in the bottom-right of this panel if you want to add this item to your Favorites. The icon will fill-in ({% icon fa-star-o %} → {% icon fa-star %}) when it's marked as a Favorite.
|
||||
@@ -69,7 +69,7 @@ Now that a new Login item is saved in your Vault, you can beef up its security b
|
||||
This will replace your **Password** value with a randomly generated strong password. Moving from a password like `Fido1234` to `X@Ln@x9J@&u@5n##B` can stop a would-be hacker in their tracks.
|
||||
6. Copy your new password with the same {% icon fa-copy %} **Copy** icon you used earlier, and hit the **Save** button.
|
||||
|
||||
{% callout success %}Don't worry about overwriting your existing password! If something goes wrong, Bitwarden maintains a **Password History** of the last 5 passwords for every Login item:<br><br>{% image /getting-started/pwhistory.png %}{% endcallout %}
|
||||
{% callout success %}Don't worry about overwriting your existing password! If something goes wrong, Bitwarden maintains a **Password History** of the last 5 passwords for every Login item:<br><br>{% image getting-started/pwhistory.png %}{% endcallout %}
|
||||
7. Tab back over to the other website, and paste your strong password in the **New Password** and **Confirm new password** fields.
|
||||
8. Once you **Save** the password change, you're finished!
|
||||
|
||||
@@ -90,7 +90,7 @@ There are many [available methods]({% link _articles/two-step-login/setup-two-st
|
||||
3. From the left-side Settings menu, select **Two-step Login**.
|
||||
4. Locate the **Authenticator App** option and select the **Manage** button:
|
||||
|
||||
{% image /two-step/twostep-options-authoverlay.png Select the Manage Button %}
|
||||
{% image two-step/twostep-options-authoverlay.png Select the Manage Button %}
|
||||
|
||||
You'll be prompted to enter your Bitwarden Master Password to continue.
|
||||
5. On your mobile device, open Authy and tap the {% icon fa-plus %} **Add Account** button.
|
||||
@@ -101,7 +101,7 @@ There are many [available methods]({% link _articles/two-step-login/setup-two-st
|
||||
Your Two-step Login Recovery code can be used in the event that you lose your mobile device. **This is a critical step to ensure you don't ever get locked out of your Vault**, so don't skip it!
|
||||
9. Enter your Master Password and select the **Continue** button to get your Recovery Code.
|
||||
|
||||
{% image /getting-started/recoverycode.png Example Recovery Code %}
|
||||
{% image getting-started/recoverycode.png Example Recovery Code %}
|
||||
|
||||
Save your Recovery Code in the way that makes the most sense for you. Believe it or not, printing your Recovery Code and keeping it somewhere safe is one of the best ways to make that the code isn't vulnerable to theft or inadvertent deletion.
|
||||
|
||||
|
||||
@@ -46,7 +46,7 @@ Currently, file attachments are not included in Bitwarden import operations and
|
||||
|
||||
The following error messages, typically received when attempting to import a `.csv`, indicate that an item in your import file has a specified value that exceeds the allowed **encrypted** character limit for its field type:
|
||||
|
||||
{% image /importing/ciphererror_2021.png Cipher errors in the Web Vault%}
|
||||
{% image importing/ciphererror_2021.png Cipher errors in the Web Vault%}
|
||||
|
||||
To solve this issue, open the `.csv` file in a text editor or spreadsheet program and **remove** or **reduce the character count** of the offending item. Bitwarden won't import your `.csv` file until it is free of offenses. The contents of the error messages contain several pieces of pertinent data to help you identify the offending item. For example, in the above example:
|
||||
|
||||
|
||||
@@ -37,7 +37,7 @@ To export your data from the LastPass Web Vault:
|
||||
|
||||
1. Select the {% icon fa-rocket %} **Advanced Options** option on the left sidebar:
|
||||
|
||||
{% image /importing/lastpassadvancedoptions.png Export from Web Vault %}
|
||||
{% image importing/lastpassadvancedoptions.png Export from Web Vault %}
|
||||
2. From the Manage Your Vault section, select the **Export** option.
|
||||
3. Enter your Master Password to validate the export attempt.
|
||||
|
||||
@@ -64,7 +64,7 @@ To export your data from a LastPass Browser Extension:
|
||||
|
||||
1. In the Browser Extension, navigate to **Account Options** → **Advanced** → **Export** → **LastPass CSV File**:
|
||||
|
||||
{% image /importing/lp-be.png Export from Browser Extension %}
|
||||
{% image importing/lp-be.png Export from Browser Extension %}
|
||||
2. Enter your Master Password to validate the export attempt.
|
||||
|
||||
Depending on your browser, your Vault data will either be automatically saved as a `.csv` or printed to the screen in a `.csv` format:
|
||||
@@ -99,7 +99,7 @@ Importing data to Bitwarden **can only be done from the** [**Web Vault**](https:
|
||||
|
||||
The following error messages, typically received when attempting to import a `.csv`, indicate that an item in your import file has a specified value that exceeds the allowed **encrypted** character limit for its field type:
|
||||
|
||||
{% image /importing/ciphererror_2021.png Cipher errors in the Web Vault%}
|
||||
{% image importing/ciphererror_2021.png Cipher errors in the Web Vault%}
|
||||
|
||||
To solve this issue, open the `.csv` file in a text editor or spreadsheet program and **remove** or **reduce the character count** of the offending item. Bitwarden won't import your `.csv` file until it is free of offenses. The contents of the error messages contain several pieces of pertinent data to help you identify the offending item. For example, in the above example:
|
||||
|
||||
@@ -117,7 +117,7 @@ If you continue to have trouble locating the offending item using the data provi
|
||||
|
||||
When importing Lastpass `.csv` exports to a [Free Organization]({% link _articles/plans-and-pricing/about-bitwarden-plans.md %}), you may observe the following error:
|
||||
|
||||
{% image /importing/lpcollectionserror.png Free Organization Max Collections Error%}
|
||||
{% image importing/lpcollectionserror.png Free Organization Max Collections Error%}
|
||||
|
||||
This error occurs when the Lastpass export contains 3 or more `grouping` values. The values in the `grouping` field are interpreted by Bitwarden as [Collections]({% link _articles/organizations/about-collections.md %}), however [Free Organizations]({% link _articles/plans-and-pricing/about-bitwarden-plans.md %}) are limited to only two Collections. The following `.csv`, for example, would cause this error:
|
||||
|
||||
|
||||
@@ -19,14 +19,14 @@ Complete the following steps to export data from the Password Safe Desktop App:
|
||||
2. Locate the **Export** option on the left-hand side and then choose **Passwords**.
|
||||
|
||||
3. For the type please select `CSV` and enter a path to save the exported file. Leave the encoding at UTF-8.
|
||||
{% image /importing/passwordsafeV8-export.png Export from Desktop App %}
|
||||
{% image importing/passwordsafeV8-export.png Export from Desktop App %}
|
||||
|
||||
4. Click on the big gray arrow on the right to proceed to the export settings screen
|
||||
|
||||
5. Set the separating character to **Semicolon**
|
||||
6. Set the text qualifier to **`"`**(double quote)
|
||||
7. Check the checkbox to keep the column headers
|
||||
{% image /importing/passwordsafeV8-exportsettings.png Export settings screen from Desktop App %}
|
||||
{% image importing/passwordsafeV8-exportsettings.png Export settings screen from Desktop App %}
|
||||
|
||||
8. Click **Finish** to start the export.
|
||||
{% callout warning %}Please note that Password Safe will export a `.csv` for **every** category you have and not just a single `.csv`.
|
||||
|
||||
@@ -20,7 +20,7 @@ Users of Bitwarden authenticate into their vaults using the **Enterprise Single
|
||||
|
||||
Administrators can configure Login with SSO in the Business Portal. For more information, see [About the Business Portal](https://bitwarden.com/help/article/about-business-portal/).
|
||||
|
||||
{% image /sso/sso-button-lg.png Enterprise Single Sign-On button %}
|
||||
{% image sso/sso-button-lg.png Enterprise Single Sign-On button %}
|
||||
|
||||
### Requiring SSO for Users
|
||||
|
||||
|
||||
@@ -15,7 +15,7 @@ Users who [authenticate their identity using SSO]({{site.baseurl}}/article/sso-a
|
||||
1. Log in to your [Web Vault](https://vault.bitwarden.com){:target="\_blank"} and open your Organization.
|
||||
2. Open the **Settings** tab and enter a unique **Identifier** for your Organization.
|
||||
|
||||
{% image /sso/org-id.png Enter an Identifier %}
|
||||
{% image sso/org-id.png Enter an Identifier %}
|
||||
3. **Save** your changes before exiting this page.
|
||||
|
||||
{% callout success %}
|
||||
@@ -28,7 +28,7 @@ Once you have your Organization Identifier, you can proceed to enabling and conf
|
||||
|
||||
1. From your Organization Vault, navigate to the **Business Portal**:
|
||||
|
||||
{% image /organizations/business-portal-button-overlay.png Business Portal %}
|
||||
{% image organizations/business-portal-button-overlay.png Business Portal %}
|
||||
|
||||
2. From the Business Portal menu bar, check that the correct Organization is listed and select the **Single Sign-On** button:
|
||||
|
||||
|
||||
@@ -35,13 +35,13 @@ Complete the following steps to enable Login with SSO for SAML 2.0 authenticatio
|
||||
1. In the Web Vault, navigate to your Organization and open the **Settings** tab.
|
||||
2. In the **Identifier** field, enter a unique identifier for your Organization:
|
||||
|
||||
{% image /sso/org-id.png Enter an Identifier %}
|
||||
{% image sso/org-id.png Enter an Identifier %}
|
||||
|
||||
Don't forget to **Save** your identifier. Users will be required to enter this **Identifier** upon login.
|
||||
|
||||
3. Navigate to the **Business Portal**.
|
||||
|
||||
{% image /organizations/business-portal-button-overlay.png Business Portal button %}
|
||||
{% image organizations/business-portal-button-overlay.png Business Portal button %}
|
||||
|
||||
4. Select the **Single Sign-On** button.
|
||||
4. Check the **Enabled** checkbox.
|
||||
@@ -55,7 +55,7 @@ After selecting **SAML 2.0**, this page will display two sections of fields you
|
||||
|
||||
Fields in this section will be required when you [Configure your IdP](#step-3-configure-your-idp).
|
||||
|
||||
{% image /sso/sso-saml-sp.png SAML Service Provider Configuration section %}
|
||||
{% image sso/sso-saml-sp.png SAML Service Provider Configuration section %}
|
||||
|
||||
#### SP Entity ID
|
||||
|
||||
@@ -127,7 +127,7 @@ Fields in this section should come from the configured values in [Step 3: Config
|
||||
|
||||
Required fields will be marked. Failing to provide a value for a required field will cause your configuration to be rejected.
|
||||
|
||||
{% image /sso/sso-saml-ip.png %}
|
||||
{% image sso/sso-saml-ip.png %}
|
||||
|
||||
#### Entity ID (*Required*)
|
||||
|
||||
|
||||
@@ -78,7 +78,7 @@ When you're done configuring these fields, **Save** your work.
|
||||
|
||||
Once your configuration is complete, test it by navigating to [https://vault.bitwarden.com](https://vault.bitwarden.com){:target="\_blank"} and selecting the **Enterprise Single Sign-On** button:
|
||||
|
||||
{% image /sso/sso-button-lg.png Enterprise Single Sign-On button %}
|
||||
{% image sso/sso-button-lg.png Enterprise Single Sign-On button %}
|
||||
|
||||
Enter the [configured Organization Identifier]({{site.baseurl}}/article/configure-sso-saml/#step-1-enabling-login-with-sso) and select **Log In**. If your implementation is successfully configured, you'll be redirected to the Microsoft login screen:
|
||||
|
||||
|
||||
@@ -81,7 +81,7 @@ When you're done configuring these fields, **Save** your work.
|
||||
|
||||
Once your configuration is complete, test it by navigating to [https://vault.bitwarden.com](https://vault.bitwarden.com){:target="\_blank"} and selecting the **Enterprise Single Sign-On** button:
|
||||
|
||||
{% image /sso/sso-button-lg.png Enterprise Single Sign-On button %}
|
||||
{% image sso/sso-button-lg.png Enterprise Single Sign-On button %}
|
||||
|
||||
Enter the [configured Organization Identifier](#) and select **Log In**. If your implementation is successfully configured, you'll be redirected to the Okta login screen:
|
||||
|
||||
|
||||
@@ -162,7 +162,7 @@ When you're done with the Identity Provider Configuration section, **Save** your
|
||||
|
||||
Once your configuration is complete, test it by navigating to [https://vault.bitwarden.com](https://vault.bitwarden.com){:target="\_blank"} and selecting the **Enterprise Single-On** button:
|
||||
|
||||
{% image /sso/sso-button-lg.png Enterprise Single Sign-On button %}
|
||||
{% image sso/sso-button-lg.png Enterprise Single Sign-On button %}
|
||||
|
||||
Enter the [configured Organization Identifier]({{site.baseurl}}/article/configure-sso-saml/#step-1-set-an-organization-identifier) and select **Log In**. If your implementation is successfully configured, you'll be redirected to the AD FS SSO login screen. After you authenticate with your AD FS credentials, enter your Bitwarden Master Password to decrypt your Vault!
|
||||
|
||||
|
||||
@@ -133,7 +133,7 @@ When you're done with the Identity Provider Configuration section, **Save** your
|
||||
|
||||
Once your configuration is complete, test it by navigating to [https://vault.bitwarden.com](https://vault.bitwarden.com) and selecting the **Enterprise Single Sign-On** button:
|
||||
|
||||
{% image /sso/sso-button-lg.png Enterprise Single Sign-On button %}
|
||||
{% image sso/sso-button-lg.png Enterprise Single Sign-On button %}
|
||||
|
||||
Enter the [configured Organization Identifier](#) and select **Log In**. If your implementation is successfully configured, you'll be redirected to the Auth0 login screen:
|
||||
|
||||
|
||||
@@ -125,7 +125,7 @@ When you're done with the Identity Provider Configuration section, **Save** your
|
||||
|
||||
Once your configuration is complete, test it by navigating to [https://vault.bitwarden.com](https://vault.bitwarden.com){:target="\_blank"} and selecting the **Enterprise Single Sign-On** button:
|
||||
|
||||
{% image /sso/sso-button-lg.png Enterprise Single Sign-On button %}
|
||||
{% image sso/sso-button-lg.png Enterprise Single Sign-On button %}
|
||||
|
||||
Enter the [configured Organiztion Identifier]({{site.baseurl}}/article/configure-sso-saml/#step-1-enabling-login-with-sso) and select **Log In**. If your implementation is successfully configured, you'll be redirected to the AWS SSO login screen:
|
||||
|
||||
|
||||
@@ -131,7 +131,7 @@ When you're done with the Identity Provider Configuration section, **Save** your
|
||||
|
||||
Once your configuration is complete, test it by navigating to [https://vault.bitwarden.com](https://vault.bitwarden.com){:target="\_blank"} and selecting the **Enterprise Single Sign-On** button:
|
||||
|
||||
{% image /sso/sso-button-lg.png Enterprise Single Sign-On button %}
|
||||
{% image sso/sso-button-lg.png Enterprise Single Sign-On button %}
|
||||
|
||||
Enter the [configured Organization Identifier]({{site.baseurl}}/article/configure-sso-saml/#step-1-enabling-login-with-sso) and select **Log In**. If your implementation is successfully configured, you'll be redirected to the Microsoft login screen:
|
||||
|
||||
|
||||
@@ -121,7 +121,7 @@ When you're done with the Identity Provider Configuration section, **Save** your
|
||||
|
||||
Once your configuration is complete, test it by navigating to [https://vault.bitwarden.com](https://vault.bitwarden.com){:target="\_blank"} and selecting the **Enterprise Single Sign-On** button:
|
||||
|
||||
{% image /sso/sso-button-lg.png Enterprise Single Sign-On button %}
|
||||
{% image sso/sso-button-lg.png Enterprise Single Sign-On button %}
|
||||
|
||||
Enter the [configured Organiztion Identifier](#) and select **Log In**. If your implementation is successfully configured, you'll be redirected to your source IdP's login screen.
|
||||
|
||||
|
||||
@@ -121,7 +121,7 @@ When you're done with the Identity Provider Configuration section, **Save** your
|
||||
|
||||
Once your configuration is complete, test it by navigating to [https://vault.bitwarden.com](https://vault.bitwarden.com){:target="\_blank"} and selecting the **Enterprise Single Sign-On** button:
|
||||
|
||||
{% image /sso/sso-button-lg.png Enterprise Single Sign-On button %}
|
||||
{% image sso/sso-button-lg.png Enterprise Single Sign-On button %}
|
||||
|
||||
Enter the [configured Organization Identifier]({{site.baseurl}}/article/configure-sso-saml/#step-1-enabling-login-with-sso) and select **Log In**. If your implementation is successfully configured, you'll be redirected to the Google Workspace login screen:
|
||||
|
||||
|
||||
@@ -138,7 +138,7 @@ Identity Provider Configuration will often require you to refer back to the OneL
|
||||
|
||||
Once your configuration is complete, test it by navigating to [https://vault.bitwarden.com](https://vault.bitwarden.com){:target="\_blank"} and selecting the **Enterprise Single Sign-On** button:
|
||||
|
||||
{% image /sso/sso-button-lg.png Enterprise Single Sign-On button %}
|
||||
{% image sso/sso-button-lg.png Enterprise Single Sign-On button %}
|
||||
|
||||
Enter the [configured Organization Identifier](#) and select **Log In**. If your implementation is successfully configured, you'll be redirected to the JumpCloud login screen:
|
||||
|
||||
|
||||
@@ -187,7 +187,7 @@ When you're done with the Identity Provider Configuration section, **Save** your
|
||||
|
||||
Once your configuration is complete, test it by navigating to [https://vault.bitwarden.com](https://vault.bitwarden.com){:target="\_blank"} and selecting the **Enterprise Single Sign-On** button:
|
||||
|
||||
{% image /sso/sso-button-lg.png Enterprise Single Sign-On button %}
|
||||
{% image sso/sso-button-lg.png Enterprise Single Sign-On button %}
|
||||
|
||||
Enter the [configured Organization Identifier]({{site.baseurl}}/article/configure-sso-saml/#step-1-enabling-login-with-sso) and select **Log In**. If your implementation is successfully configured, you'll be redirected to the Keycloak login screen:
|
||||
|
||||
|
||||
@@ -137,7 +137,7 @@ When you're done with the Identity Provider Configuration section, **Save** your
|
||||
|
||||
Once your configuration is complete, test it by navigating to [https://vault.bitwarden.com](https://vault.bitwarden.com){:target="\_blank"} and selecting the **Enterprise Single Sign-On** button:
|
||||
|
||||
{% image /sso/sso-button-lg.png Enterprise Single Sign-On button %}
|
||||
{% image sso/sso-button-lg.png Enterprise Single Sign-On button %}
|
||||
|
||||
Enter the [configured Organization Identifier]({{site.baseurl}}/article/configure-sso-saml/#step-1-enabling-login-with-sso) and select **Log In**. If your implementation is successfully configured, you'll be redirected to the Okta login screen:
|
||||
|
||||
|
||||
@@ -125,7 +125,7 @@ Identity Provider Configuration will often require you to refer back to the OneL
|
||||
|
||||
Once your configuration is complete, test it by navigating to [https://vault.bitwarden.com](https://vault.bitwarden.com){:target="\_blank"} and selecting the **Enterprise Single Sign-On** button:
|
||||
|
||||
{% image /sso/sso-button-lg.png Enterprise Single Sign-On button %}
|
||||
{% image sso/sso-button-lg.png Enterprise Single Sign-On button %}
|
||||
|
||||
Enter the [configured Organization Identifier](#) and select **Log In**. If your implementation is successfully configured, you'll be redirected to the OneLogin login screen:
|
||||
|
||||
|
||||
@@ -18,14 +18,14 @@ Complete the following steps to use Login with SSO to authenticate into your Bit
|
||||
1. Open your Bitwarden App or navigate to the Bitwarden Web Vault.
|
||||
2. Select the **Enterprise Single Sign-On** button.
|
||||
|
||||
{% image /sso/sso-button-lg.png Enterprise Single Sign-On button %}
|
||||
{% image sso/sso-button-lg.png Enterprise Single Sign-On button %}
|
||||
|
||||
3. Enter your **Organization Identifier** and select **Log In**.
|
||||
|
||||
{% callout info %}We recommend bookmarking this page with your Organization Identifier included as a query string so that you don't have to enter it each time, for example `https://vault.bitwarden.com/#/sso?identifier=your-org-id` or `https://your.domain.com/#/sso?identifier=your-org-id`.
|
||||
{% endcallout %}
|
||||
|
||||
{% image /sso/org-id-input.png Organization Identifier field %}
|
||||
{% image sso/org-id-input.png Organization Identifier field %}
|
||||
|
||||
A browser window will open prompting you to enter your SSO credentials or other required authentication mechanisms.
|
||||
|
||||
|
||||
@@ -9,7 +9,7 @@ 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 %}
|
||||
{% 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:
|
||||
|
||||
|
||||
@@ -11,11 +11,11 @@ order: 12
|
||||
|
||||
The Bitwarden Business Portal is a dedicated space for administrators to configure security controls for their organization. Users with the User Type **Admin** or higher can access the Business Portal by selecting the **Business Portal** button from their Organization screen.
|
||||
|
||||
{% image /organizations/business-portal-button-overlay.png Business Portal button %}
|
||||
{% image organizations/business-portal-button-overlay.png Business Portal button %}
|
||||
|
||||
The Bitwarden Business Portal provides access to configuration for Single Sign-On and Policies for your Organization.
|
||||
|
||||
{% image /organizations/business-portal.png Bitwarden Business Portal %}
|
||||
{% image organizations/business-portal.png Bitwarden Business Portal %}
|
||||
|
||||
### Next Steps
|
||||
To learn how to configure Single Sign-On, see:
|
||||
|
||||
@@ -22,11 +22,11 @@ Collections gather together Logins, Notes, Cards, and Identities for [secure sha
|
||||
|
||||
For many Organizations, using Collections means adding a set of Vault items and individually assigning users to that Collection. Some common methods for constructing scaleable Collections include **Collections by Department** (i.e. users from your Marketing Team are assigned to a **Marketing** Collection), or **Collections by Function** (i.e. users from your Marketing Team are assigned to a **Social Media** Collection):
|
||||
|
||||
{% image /organizations/collections-graphic-1.png Using Collections %}
|
||||
{% image organizations/collections-graphic-1.png Using Collections %}
|
||||
|
||||
Teams and Enterprise Organizations can also designate access to Collections based on user [Groups]({{site.baseurl}}/article/about-groups/), rather than individual users. Group-Collection associations provide a deeper level of access control and scalability to sharing resources. One common Group-Collection methodology is to create **Groups by Department** and **Collections by Function**, for example:
|
||||
|
||||
{% image /organizations/collections-graphic-2.png Using Collections with Groups%}
|
||||
{% image organizations/collections-graphic-2.png Using Collections with Groups%}
|
||||
|
||||
Other common methodologies include **Collections by Vendor or System** (i.e. users in an **Engineering** Group are assigned to a **AWS Credentials** Collection) and **Groups by Locality** (i.e. users are assigned to a **US Employees** Group or **UK Employees** Group).
|
||||
|
||||
@@ -57,7 +57,7 @@ To create a nested Collection, follow the [steps above](#create-a-collection), b
|
||||
|
||||
You may find that you need to add or remove users from a Collection, or delete it entirely. Both of these can be done from the **Manage** → **Collections** view by hovering over the desired Collection and selecting the {% icon fa-cog %} gear dropdown:
|
||||
|
||||
{% image /organizations/collection-delete.png Change a Collection %}
|
||||
{% image organizations/collection-delete.png Change a Collection %}
|
||||
|
||||
{% callout info %}
|
||||
Deleting a Collection **will not** delete the Vault items included in it. When a Collection is deleted, Vault items will be moved to the {% icon fa-cube %} **Unassigned** filter, accessible from the Organization Vault.
|
||||
|
||||
@@ -23,7 +23,7 @@ Groups are available to [Teams and Enterprise Organizations]({{site.baseurl}}/ar
|
||||
|
||||
Teams and Enterprise Organizations can designate access to [Collections]({{site.baseurl}}/article/about-collections/) based on user Groups, rather than individual users. Group-Collection associations provide a deep level of access control and scalability to sharing resources. One common Group-Collection methodology is to create **Groups by Department** and **Collections by Function**, for example:
|
||||
|
||||
{% image /organizations/collections-graphic-2.png Using Collections with Groups%}
|
||||
{% image organizations/collections-graphic-2.png Using Collections with Groups%}
|
||||
|
||||
Other common methodologies include **Collections by Vendor or System** (i.e. users in an **Engineering** Group are assigned to a **AWS Credentials** Collection) and **Groups by Locality** (i.e. users are assigned to a **US Employees** Group or **UK Employees** Group).
|
||||
|
||||
@@ -35,7 +35,7 @@ Users with the [Admin role (or higher)]({{site.baseurl}}/article/user-types-acce
|
||||
2. Open the **Manage** tab and select **Groups** from the left-hand menu.
|
||||
3. On the Groups screen, select the {% icon fa-plus %} **New Group** button.
|
||||
|
||||
{% image /organizations/groups-newgroup.png New Group %}
|
||||
{% image organizations/groups-newgroup.png New Group %}
|
||||
4. Give your Group a **Name** and assign the desired [Access Control]({{site.baseurl}}/article/user-types-access-control/#access-control).
|
||||
|
||||
Access Controls can designate that users can access all items (i.e. all Collections) or only specific Collections, as well as whether [Passwords are hidden or Logins are read-only]({{site.baseurl}}/article/user-types-access-control/#granular-access-control).
|
||||
@@ -50,7 +50,7 @@ Once your Groups are created and configured, add users to them:
|
||||
1. In your Organization Vault open the **Manage** tab and select **People** from the left-hand menu.
|
||||
2. Hover over the user you want to add and use the {% icon fa-cog %} gear dropdown to select **Groups**:
|
||||
|
||||
{% image /organizations/org-people-options-updated-overlay.png %}
|
||||
{% image organizations/org-people-options-updated-overlay.png %}
|
||||
3. Select the Group(s) to add this user to and **Save** your selection.
|
||||
|
||||
{% callout success %}
|
||||
|
||||
@@ -15,11 +15,11 @@ redirect_from:
|
||||
|
||||
Organizations relate Bitwarden users and Vault items together for [secure sharing]({{site.baseurl}}/article/share-to-a-collection/) of Logins, Notes, Cards, and Identities. Organizations have a unique Vault, where [administrators]({{site.baseurl}}/article/user-types-access-control/) can manage the Organization's items, users, and settings:
|
||||
|
||||
{% image /organizations/org-vault-admin.png Organization Vault %}
|
||||
{% image organizations/org-vault-admin.png Organization Vault %}
|
||||
|
||||
Members of an Organization will find shared items ({% icon fa-share-alt %}) in their **My Vault** view alongside personal items, as well as filters for assigned [Collections]({{site.baseurl}}/article/about-collections/), which group Organization items similarly to how [Folders]({{site.baseurl}}/article/folders/) organize personal items:
|
||||
|
||||
{% image /organizations/shared-items.png Access shared items %}
|
||||
{% image organizations/shared-items.png Access shared items %}
|
||||
|
||||
### Types of Organizations
|
||||
|
||||
|
||||
@@ -73,7 +73,7 @@ If you're automatically enrolling Organization members in Admin Password Reset,
|
||||
|
||||
To enroll in Password Reset, navigate to **Settings** → **Organizations** in the [Web Vault](https://vault.bitwarden.com/){:target="\_blank"}:
|
||||
|
||||
{% image /organizations/pwreset-enroll.png Enroll in Password Reset %}
|
||||
{% image organizations/pwreset-enroll.png Enroll in Password Reset %}
|
||||
|
||||
Hover over the Organization you wish to enroll in Password Reset for, select the {% icon fa-cog %} gear dropdown, and choose **Enroll in Password Reset**. When you're enrolled in Password Reset, the Organization listing will display a {% icon fa-key %} key icon. You can enroll in Admin Password Reset for multiple Organizations, if you choose.
|
||||
|
||||
@@ -81,7 +81,7 @@ Hover over the Organization you wish to enroll in Password Reset for, select the
|
||||
|
||||
Once enrolled, you can **Withdraw** from Password Reset from the same dropdown used to enroll:
|
||||
|
||||
{% image /organizations/pwreset-withdraw.png Withdraw from Password Reset %}
|
||||
{% image organizations/pwreset-withdraw.png Withdraw from Password Reset %}
|
||||
|
||||
Manually changing your Master Password or [rotating your encryption key]({{site.baseurl}}/article/account-encryption-key/) **will not** withdraw you from Admin Password Reset.
|
||||
|
||||
@@ -97,11 +97,11 @@ To reset a Master Password for a member of your Enterprise Organization:
|
||||
2. Open the **Manage** tab and navigate to the **People** section.
|
||||
3. Hover over the user whose Master Password you want to reset, select the {% icon fa-cog %} gear dropdown, and choose {% icon fa-key %} **Reset Password**:
|
||||
|
||||
{% image /organizations/pwreset-reset.png Reset Password %}
|
||||
{% image organizations/pwreset-reset.png Reset Password %}
|
||||
|
||||
4. On the Reset Password window, create a **New Password** for the user. If your Organization has enabled the [Master Password Policy]({{site.baseurl}}/article/policies/#master-password), you will need to create a password that meets the implemented requirements (e.g. min 8 characters, contains numbers):
|
||||
|
||||
{% image /organizations/pwreset-newpw.png Create a New Password %}
|
||||
{% image organizations/pwreset-newpw.png Create a New Password %}
|
||||
|
||||
Copy the new Master Password and contact the user to coordinate secure communication of it, for example using [Bitwarden Send]({{site.baseurl}}/article/create-send/).
|
||||
|
||||
|
||||
@@ -17,7 +17,7 @@ This article details *one recommended* implementation to set partners and their
|
||||
|
||||
Bitwarden Organizations relate users and Vault items together for [secure sharing]({{site.baseurl}}/article/share-to-a-collection/) of Logins, Notes, Cards, and Identities. Organizations could be a family, team, company or any group of people that needs to securely share data. Organizations have a unique Vault, where [administrators]({{site.baseurl}}/article/user-types-access-control/) can manage the Organization's items, users, and settings:
|
||||
|
||||
{% image /organizations/org-vault-admin.png Organization Vault %}
|
||||
{% image organizations/org-vault-admin.png Organization Vault %}
|
||||
|
||||
An MSP should [create an Organization]({{site.baseurl}}/article/about-organizations/#create-an-organization) **for each client**, or the client can create one for themselves. There are a few [types of Organizations]({{site.baseurl}}/article/about-organizations/#types-of-organizations) you can choose from to best fit your client's needs. For the most robust set of business features, we recommend [Enterprise Plans]({{site.baseurl}}/article/about-bitwarden-plans/#enterprise-organizations).
|
||||
|
||||
@@ -37,7 +37,7 @@ Bitwarden Organizations are designed to manage users and data in a scalable and
|
||||
|
||||
Collections gather together Logins, Notes, Cards, and Identities for [secure sharing]({{site.baseurl}}/article/share-to-a-collection) within an Organization. Some common methods for constructing scalable Collections include **Collections by Department** (i.e. users from the client's Marketing Team are assigned to a Marketing Collection), or **Collections by Function** (i.e. users from the client's Marketing Team are assigned to a Social Media Collection):
|
||||
|
||||
{% image /organizations/collections-graphic-1.png Collections %}
|
||||
{% image organizations/collections-graphic-1.png Collections %}
|
||||
|
||||
[Learn how to create Collections]({{site.baseurl}}/article/about-collections/#create-a-collection).
|
||||
|
||||
@@ -45,7 +45,7 @@ Collections gather together Logins, Notes, Cards, and Identities for [secure sha
|
||||
|
||||
Teams and Enterprise Organizations can also institute Groups, which relate together individual users to provide a scalable way to assign permissions, including access to [Collections]({{site.baseurl}}/article/about-collections) and other [access controls]({{site.baseurl}}/article/user-types-access-control/#access-control). One common Group-Collection methodology is to create **Groups by Department** and **Collections by Function**, for example:
|
||||
|
||||
{% image /organizations/collections-graphic-2.png Groups %}
|
||||
{% image organizations/collections-graphic-2.png Groups %}
|
||||
|
||||
[Learn how to create Groups]({{site.baseurl}}/article/about-groups/#create-a-group).
|
||||
|
||||
@@ -57,7 +57,7 @@ With Collections now created, and a plan for connecting users to credentials usi
|
||||
|
||||
MSP teams can manage Organization users manually or using Directory Connector to sync users and Groups from existing directory services (LDAP, AD, etc.). For most MSP clients, Directory Connector is the recommended method:
|
||||
|
||||
{% image /directory-connector/dc-diagram.png Directory Connector %}
|
||||
{% image directory-connector/dc-diagram.png Directory Connector %}
|
||||
|
||||
Prepare to onboard users by ensuring your Organization has the correct [number of user seats]({{site.baseurl}}/article/managing-users/#manage-user-seats). Then, onboard users:
|
||||
|
||||
|
||||
@@ -12,7 +12,7 @@ order: 13
|
||||
|
||||
Event Logs are timestamped records of events that occur within your Organization. Event Logs are accessible to [Admins and Owners]({{site.baseurl}}/article/event-logs/) from the **Manage** tab of your Organization Vault:
|
||||
|
||||
{% image /organizations/event-logs-updated.png Event Logs %}
|
||||
{% image organizations/event-logs-updated.png Event Logs %}
|
||||
|
||||
Events Logs are [exportable](#export-events) and accessible from the `/events` endpoint of the [Bitwarden Public API](https://bitwarden.com/help/article/public-api/).
|
||||
|
||||
@@ -90,7 +90,7 @@ https://github.com/bitwarden/web/blob/master/src/locales/en/messages.json
|
||||
|
||||
Exporting event logs will create a `.csv` of all events within the specified date range:
|
||||
|
||||
{% image /organizations/event-logs-export.png Export Event Logs %}
|
||||
{% image organizations/event-logs-export.png Export Event Logs %}
|
||||
|
||||
For example:
|
||||
|
||||
|
||||
@@ -27,7 +27,7 @@ Importing data to Bitwarden **can only be done from the** [**Web Vault**](https:
|
||||
|
||||
1. Open your Organization and navigate to the **Tools** tab:
|
||||
|
||||
{% image /importing/org-tools.png Organization Tools %}
|
||||
{% image importing/org-tools.png Organization Tools %}
|
||||
3. Select **Import Data** from the left-hand Tools menu.
|
||||
3. From the format dropdown, choose a **File Format** (see [What file formats does Bitwarden support for import?]({{site.baseurl}}/article/send-faqs/#q-what-file-formats-does-bitwarden-support-for-import)).
|
||||
4. Select the **Choose File** button and add the file to import.
|
||||
@@ -41,7 +41,7 @@ Currently, file attachments are not included in Bitwarden import operations and
|
||||
|
||||
The following error messages, typically received when attempting to import a `.csv`, indicate that an item in your import file has a specified value that exceeds the allowed **encrypted** character limit for its field type:
|
||||
|
||||
{% image /importing/ciphererror_2021.png Cipher errors in the Web Vault%}
|
||||
{% image importing/ciphererror_2021.png Cipher errors in the Web Vault%}
|
||||
|
||||
To solve this issue, open the `.csv` file in a text editor or spreadsheet program and **remove** or **reduce the character count** of the offending item. Bitwarden won't import your `.csv` file until it is free of offenses. The contents of the error messages contain several pieces of pertinent data to help you identify the offending item. For example, in the above example:
|
||||
|
||||
|
||||
@@ -56,7 +56,7 @@ To invite users to your Organization:
|
||||
2. Open the **Manage** tab and select **People** from the left-hand menu.
|
||||
3. Select the {% icon fa-plus %} **Invite User** button:
|
||||
|
||||
{% image /organizations/org-people-invite.png Invite User %}
|
||||
{% image organizations/org-people-invite.png Invite User %}
|
||||
4. On the Invite User panel:
|
||||
|
||||
- Enter the **Email** address where new users should receive invites. You can add up to 20 users at a time by comma-separating email addresses.
|
||||
@@ -67,7 +67,7 @@ To invite users to your Organization:
|
||||
{% callout info %}
|
||||
**Invitations expire after 5 days**, at which point the user will need to be re-invited. Re-invite users in bulk by selecting each user and using the {% icon fa-cog %} gear dropdown to **Resend Invitations**:
|
||||
|
||||
{% image /organizations/org-people-reinvite.png Bulk Reinvite %}
|
||||
{% image organizations/org-people-reinvite.png Bulk Reinvite %}
|
||||
|
||||
If you're self-hosting Bitwarden, you can configure the invitation expiration period [using an environment variable]({{site.baseurl}}/article/environment-variables/).
|
||||
{% endcallout %}
|
||||
|
||||
@@ -71,11 +71,11 @@ Using the same tool in both areas helps that habit form faster and easier. Enter
|
||||
|
||||
Anyone can start an Organization directly from the Web Vault:
|
||||
|
||||
{% image /organizations/new-org-button-overlay.png Create New Organization %}
|
||||
{% image organizations/new-org-button-overlay.png Create New Organization %}
|
||||
|
||||
Once created, you'll land in your Organization Vault, which is the central hub for all things sharing and Organization administration. Whoever launches the Organization will be the [Owner]({{site.baseurl}}/article/user-types-access-control), giving them full control to oversee the **Vault**, to **Manage** users, [Collections](#), [Groups](#), and [Policies](#), to use a suite of Bitwarden **Tools**, and to configure the Organization's **Settings**:
|
||||
|
||||
{% image /getting-started/org-vault.png Organization Vault %}
|
||||
{% image getting-started/org-vault.png Organization Vault %}
|
||||
|
||||
### Collections
|
||||
|
||||
@@ -83,7 +83,7 @@ Bitwarden Organizations manage users and data in a scalable and secure fashion.
|
||||
|
||||
**Collections** gather together Logins, Notes, Cards, and Identities for [secure sharing]({{site.baseurl}}/article/share-to-a-collection/) within an Organization:
|
||||
|
||||
{% image /organizations/collections-graphic-1.png Using Collections %}
|
||||
{% image organizations/collections-graphic-1.png Using Collections %}
|
||||
|
||||
### Onboarding Users
|
||||
|
||||
@@ -107,7 +107,7 @@ For large Organizations, [Directory Connector](#directory-connector) is the best
|
||||
|
||||
Groups relate together individual users, and provide a scaleable way to assign permissions including access to [Collections](#collections) and other [access controls](#comprehensive-role--based-access-controls). When onboarding new users, add them to a Group to have them automatically inherit that Groups's configured permissions:
|
||||
|
||||
{% image /organizations/collections-graphic-2.png Using Collections with Groups %}
|
||||
{% image organizations/collections-graphic-2.png Using Collections with Groups %}
|
||||
|
||||
|
||||
#### Comprehensive Role-based Access Controls
|
||||
|
||||
@@ -21,7 +21,7 @@ Organization members can share items to any assigned Collection(s) unless they'r
|
||||
|
||||
1. Hover over the item you want to share and select the {% icon fa-cog %} gear dropdown:
|
||||
|
||||
{% image /organizations/share-from-vault-overlay.png Select the gear dropdown %}
|
||||
{% image organizations/share-from-vault-overlay.png Select the gear dropdown %}
|
||||
|
||||
2. From the dropdown, select the {% icon fa-share-alt %} **Share** option.
|
||||
3. On the **Share** screen:
|
||||
@@ -33,7 +33,7 @@ Organization members can share items to any assigned Collection(s) unless they'r
|
||||
|
||||
Sharing an item **will transfer ownership to the Organization**. This means that anyone with permission can alter the item or delete it, which would remove it from your Vault as well. You can tell that an item is shared when it has the {% icon fa-share-alt %} **Shared** icon next to its name:
|
||||
|
||||
{% image /organizations/collection-shared-item.png Shared Item icon %}
|
||||
{% image organizations/collection-shared-item.png Shared Item icon %}
|
||||
|
||||
## Create a Shared Item
|
||||
|
||||
@@ -63,7 +63,7 @@ To create a new shared item:
|
||||
|
||||
Creating a shared item **will set ownership to the Organization**. This means that anyone with permission can alter the item or delete it, which would remove it from your Vault as well. You can tell that an item is shared when it has the {% icon fa-share-alt %} **Shared** icon next to its name:
|
||||
|
||||
{% image /organizations/collection-shared-item.png Shared Item icon %}
|
||||
{% image organizations/collection-shared-item.png Shared Item icon %}
|
||||
|
||||
{% endcapture %}
|
||||
{{ personal | markdownify }}
|
||||
@@ -83,7 +83,7 @@ To create a new shared item:
|
||||
|
||||
Creating a shared item or sharing an item **will set ownership to the Organization**. This means that anyone with permission can alter the item or delete it, which would remove it from your Vault as well. You can tell that an item is shared when it has the {% icon fa-share-alt %} **Shared** icon next to its name:
|
||||
|
||||
{% image /organizations/collection-shared-item.png Shared Item icon %}
|
||||
{% image organizations/collection-shared-item.png Shared Item icon %}
|
||||
|
||||
{% endcapture %}
|
||||
{{ organization | markdownify }}
|
||||
|
||||
@@ -55,7 +55,7 @@ As an example, the Custom role allows for the creation of a user that can fully
|
||||
|
||||
Access Control determines access to Collections, as well as permissions within each individual Collection:
|
||||
|
||||
{% image /organizations/collection-access-control.png Configure Access Control options %}
|
||||
{% image organizations/collection-access-control.png Configure Access Control options %}
|
||||
|
||||
{% callout info %}
|
||||
Recall that [Admins and Owners](#user-types) can automatically access all Collections. For these user types, configuring Access Control will determine **which Collections are readily accessible** in their Personal Vault and client applications (Browser Extension, Mobile, etc.). Admins and Owners will still be able to access "unassigned" Collections from the Organization Vault.
|
||||
|
||||
@@ -20,7 +20,7 @@ Complete the following steps to update the billing information for your individu
|
||||
|
||||
1. In the [Web Vault](https://vault.bitwarden.com), select **Settings** from the top navigation bar.
|
||||
|
||||
{% image /plans-and-pricing/billing-individual-overlay.png Select Billing %}
|
||||
{% image plans-and-pricing/billing-individual-overlay.png Select Billing %}
|
||||
|
||||
2. Select **Billing** from the left menu.
|
||||
|
||||
@@ -37,7 +37,7 @@ Complete the following steps to update the billing information for your Organiza
|
||||
|
||||
1. In the [Web Vault](https://vault.bitwarden.com), select your Organization.
|
||||
|
||||
{% image /organizations/open-org-overlay.png Open your Organization %}
|
||||
{% image organizations/open-org-overlay.png Open your Organization %}
|
||||
|
||||
2. In your Organization, select the **Settings** tab.
|
||||
3. On the Settings screen, select **Billing** from the left menu.
|
||||
|
||||
@@ -22,7 +22,7 @@ This article will guide you through a few questions that can help you determine
|
||||
|
||||
Use this flowchart to guide you through your journey:
|
||||
|
||||
{% image /plans-and-pricing/what-plan-flowchart-1.png What Plan is Right for Me? %}
|
||||
{% image plans-and-pricing/what-plan-flowchart-1.png What Plan is Right for Me? %}
|
||||
|
||||
## Do you want to start protecting your online accounts with Bitwarden?
|
||||
|
||||
|
||||
@@ -67,7 +67,7 @@ As a grantor, complete the following steps to invite a trusted emergency contact
|
||||
3. Select **Emergency Access** from the left-hand Settings menu.
|
||||
4. Select the {% icon fa-plus %} **Add emergency contact** button. In the Invite Emergency Contact window:
|
||||
|
||||
{% image /features/emergency-access/ea-invite.png Add emergency contact%}
|
||||
{% image features/emergency-access/ea-invite.png Add emergency contact%}
|
||||
- Enter the **Email** of your trusted emergency contact. Trusted emergency contacts must have Bitwarden accounts of their own, but don't need to have Premium.
|
||||
- Set a **User Access** level for the trusted emergency contact ([View-only or Takeover](#user-access)).
|
||||
- Set a **Wait Time** for Vault access. Wait Time dictates how long your trusted emergency contact must wait to access your Vault after initiating an emergency access request.
|
||||
@@ -83,7 +83,7 @@ As a grantee, complete the following steps to accept an invitation to become a t
|
||||
|
||||
1. In the received email invitation, select the **Become emergency contact** button in the email to open an Emergency Access acceptance page in your Browser:
|
||||
|
||||
{% image /features/emergency-access/ea-invitation.png Emergency access invitation %}
|
||||
{% image features/emergency-access/ea-invitation.png Emergency access invitation %}
|
||||
2. Log in to your Bitwarden account to accept the invitation. If you don't already have a Bitwarden account, you'll need to create one.
|
||||
|
||||
### Confirm an Accepted Invitation
|
||||
@@ -97,7 +97,7 @@ As a grantor, complete the following steps to confirm an accepted invitation:
|
||||
In the **Trusted emergency contacts** section, the invited user should appear with an `Accepted` status card.
|
||||
4. Hovering over the user, select the gear icon and select **Confirm** from the dropdown menu.
|
||||
|
||||
{% image /features/emergency-access/ea-confirm.png %}
|
||||
{% image features/emergency-access/ea-confirm.png %}
|
||||
|
||||
To ensure the integrity of your encryption keys, verify the displayed fingerprint phrase with the grantee before completing confirmation.
|
||||
|
||||
@@ -111,7 +111,7 @@ As a grantee, complete the following steps to initiate an emergency access reque
|
||||
4. In the **Designated as emergency contact** section, select the grantor whose Vault you wish to access.
|
||||
5. In the Request Access window, select the **Request Access** button.
|
||||
|
||||
{% image /features/emergency-access/ea-request.png Request Access%}
|
||||
{% image features/emergency-access/ea-request.png Request Access%}
|
||||
You will be provided access to the grantor's Vault after the configured Wait Time, or when the grantor [manually approves](#approve-or-reject-emergency-access) the emergency access request.
|
||||
|
||||
### Approve or Reject Emergency Access
|
||||
@@ -144,7 +144,7 @@ The steps to take to regain exclusive access to your Vault after using Emergency
|
||||
|
||||
Trusted emergency contacts who are given **View** access will be able to view your Vault items once they are [approved](#approve-or-reject-emergency-access) and until their access is manually revoked. To manually revoke access, use the {% icon fa-cog %} **gear** dropdown to {% icon fa-times %} **Reject** access:
|
||||
|
||||
{% image /features/emergency-access/ea-revoke.png Revoke Emergency Access %}
|
||||
{% image features/emergency-access/ea-revoke.png Revoke Emergency Access %}
|
||||
|
||||
### Revoke a Takeover
|
||||
|
||||
|
||||
@@ -22,7 +22,7 @@ Bitwarden Send is a secure and ephemeral way to transmit sensitive information t
|
||||
|
||||
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 %}
|
||||
{% image send/send-webvault.png Send in the Web Vault %}
|
||||
|
||||
## Using Send
|
||||
|
||||
|
||||
@@ -41,7 +41,7 @@ Complete the following steps to create a new Send from the Bitwarden [Web Vault]
|
||||
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 %}
|
||||
{% 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**:
|
||||
@@ -69,7 +69,7 @@ Complete the following steps to create a new Send from the Bitwarden [Web Vault]
|
||||
|
||||
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 %}
|
||||
{% 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.
|
||||
|
||||
@@ -87,7 +87,7 @@ Complete the following steps to create a new Send from a Bitwarden Browser Exten
|
||||
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 %}
|
||||
{% 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:
|
||||
|
||||
@@ -115,7 +115,7 @@ Complete the following steps to create a new Send from a Bitwarden Browser Exten
|
||||
|
||||
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 %}
|
||||
{% 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.
|
||||
|
||||
@@ -133,7 +133,7 @@ Complete the following steps to create a new Send from a Bitwarden 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 %}
|
||||
{% 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.
|
||||
@@ -160,7 +160,7 @@ Complete the following steps to create a new Send from a Bitwarden Desktop App:
|
||||
|
||||
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 %}
|
||||
{% 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.
|
||||
|
||||
@@ -178,7 +178,7 @@ Complete the following steps to create a new Send from Bitwarden Mobile App:
|
||||
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%}
|
||||
{% 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:
|
||||
|
||||
@@ -207,7 +207,7 @@ Complete the following steps to create a new Send from Bitwarden Mobile App:
|
||||
|
||||
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 %}
|
||||
{% 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 %}
|
||||
|
||||
@@ -15,7 +15,7 @@ Unlike traditional Bitwarden Vault items, a Send can be received and opened by a
|
||||
|
||||
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%}
|
||||
{% 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:
|
||||
|
||||
@@ -45,4 +45,4 @@ Taking the above measures to ensure the trustworthiness of a hidden-email Send a
|
||||
|
||||
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 %}
|
||||
{% image send/send-unavailable.png A deleted, expired, or disabled Send %}
|
||||
|
||||
@@ -10,7 +10,7 @@ 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 %}
|
||||
{% image send/send-cli.png Send's --help text %}
|
||||
|
||||
## send
|
||||
|
||||
|
||||
@@ -46,7 +46,7 @@ When a Send reaches its specified Expiration Date:
|
||||
|
||||
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 %}
|
||||
{% 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.
|
||||
|
||||
@@ -93,7 +93,7 @@ Manually disable or delete a Send from any Bitwarden application:
|
||||
|
||||
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 %}
|
||||
{% image send/send-disable-wv.png Disable from the Web Vault %}
|
||||
|
||||
When a Send is disabled:
|
||||
|
||||
@@ -105,7 +105,7 @@ When a Send is disabled:
|
||||
|
||||
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 %}
|
||||
{% image send/send-delete.png Delete from the Web Vault %}
|
||||
|
||||
{% endcapture %}
|
||||
{{ web_vault | markdownify}}
|
||||
@@ -117,7 +117,7 @@ To delete a Send from the Web Vault, use the hover-over {% icon fa-cog %} gear d
|
||||
|
||||
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 %}
|
||||
{% image send/send-disable-be.png Disable from a Browser Extension %}
|
||||
|
||||
When a Send is disabled:
|
||||
|
||||
@@ -129,7 +129,7 @@ When a Send is disabled:
|
||||
|
||||
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 %}
|
||||
{% image send/send-delete-be.png Delete from a Browser Extension %}
|
||||
|
||||
{% endcapture %}
|
||||
{{ browser_extension | markdownify}}
|
||||
@@ -141,7 +141,7 @@ To delete a Send from a Browser Extension, select the {% icon fa-trash %} **Tras
|
||||
|
||||
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%}
|
||||
{% image send/send-desktop-disable.png Disable from a Desktop App%}
|
||||
|
||||
When a Send is disabled:
|
||||
|
||||
@@ -153,7 +153,7 @@ When a Send is disabled:
|
||||
|
||||
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 %}
|
||||
{% image send/send-desktop-delete.png Delete from a Desktop App %}
|
||||
|
||||
{% endcapture %}
|
||||
{{ desktop_info | markdownify}}
|
||||
@@ -165,7 +165,7 @@ To delete a Send from a Desktop App, open the **Edit Send** view and select the
|
||||
|
||||
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 %}
|
||||
{% image send/send-disable-mobile.png Disable from a Mobile App %}
|
||||
|
||||
When a Send is disabled:
|
||||
|
||||
@@ -177,7 +177,7 @@ When a Send is disabled:
|
||||
|
||||
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 %}
|
||||
{% image send/send-delete-mob.png Delete from a Mobile App %}
|
||||
|
||||
{% endcapture %}
|
||||
{{ mobile_info | markdownify}}
|
||||
|
||||
@@ -15,7 +15,7 @@ The **Password**, **Hide Email**, and **Hide Text** options are configurable fro
|
||||
|
||||
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%}
|
||||
{% 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-passwords) it at any time:
|
||||
|
||||
@@ -23,7 +23,7 @@ Once you password-protect a Send, you won't be able to view the configured passw
|
||||
|
||||
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 %}
|
||||
{% image send/send-new-pw.png %}
|
||||
|
||||
### Remove Send Passwords
|
||||
|
||||
@@ -47,4 +47,4 @@ Toggle the **Hide my email address from recipients** option to remove your email
|
||||
|
||||
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%}
|
||||
{% image send/send-hidden-text.png Receiving a hidden-text Send%}
|
||||
|
||||
@@ -12,7 +12,7 @@ Losing access to your secondary device(s) (e.g. a Mobile device with an installe
|
||||
|
||||
What to do when you've lost access to your secondary device(s) depends on whether you've saved your [Two-step Login Recovery Code]({% link _articles/two-step-login/two-step-recovery-code.md %}). If you're unsure, remember that Recovery Codes need to be actively saved (i.e. Bitwarden won't save it anywhere *for you*) and look something like this:
|
||||
|
||||
{% image /two-step/recoverycode.png Sample Recovery Code %}
|
||||
{% image two-step/recoverycode.png Sample Recovery Code %}
|
||||
|
||||
## Have a Recovery Code?
|
||||
|
||||
@@ -21,7 +21,7 @@ Excellent! If you have have your Recovery Code saved somewhere, you can use it t
|
||||
{% callout success %}
|
||||
Recovery Codes **won't disable Duo for Organizations**. You can tell that a Duo prompt is Organization-wide by the **(Organization)** header, as in the following screenshot:
|
||||
|
||||
{% image /two-step/duo/duo-orgs.png Duo (Organization)%}
|
||||
{% image two-step/duo/duo-orgs.png Duo (Organization)%}
|
||||
|
||||
If you're locked out of your Vault by a **Duo (Organization)** prompt, reach out to the Duo Administrator at your company for help bypassing the prompt.
|
||||
{% endcallout %}
|
||||
|
||||
@@ -31,7 +31,7 @@ Complete the following steps to enable Two-step Login using an authenticator app
|
||||
3. Select **Two-step Login** from the left-side menu.
|
||||
4. Locate the **Authenticator App** option and select the **Manage** button:
|
||||
|
||||
{% image /two-step/twostep-options-authoverlay.png Select the Manage button %}
|
||||
{% image two-step/twostep-options-authoverlay.png Select the Manage button %}
|
||||
You will be prompted to enter your Master Password to continue.
|
||||
5. Scan the QR code with your authenticator app of choice.
|
||||
|
||||
|
||||
@@ -56,7 +56,7 @@ To enable Two-step Login using Duo for your Personal Vault:
|
||||
1. Log in to your [Web Vault](https://vault.bitwarden.com){:target="\_blank"}.
|
||||
2. Select **Settings** from the top navigation bar.
|
||||
|
||||
{% image /two-step/wv-settingstab.png Select Settings %}
|
||||
{% image two-step/wv-settingstab.png Select Settings %}
|
||||
3. Select **Two-step Login** from the left-side Settings menu.
|
||||
4. Locate the **Duo** option and select the **Manage** button.
|
||||
|
||||
@@ -89,11 +89,11 @@ You must be an [Organization Owner]({% link _articles/organizations/user-types-a
|
||||
1. Log in to your [Web Vault](https://vault.bitwarden.com){:target="\_blank"}.
|
||||
2. Open your Organization and select **Settings** from the Organization navigation.
|
||||
|
||||
{% image /two-step/wv-orgsettingstab.png Select Settings %}
|
||||
{% image two-step/wv-orgsettingstab.png Select Settings %}
|
||||
3. Select **Two-step Login** from the left-side Settings menu.
|
||||
4. Locate the **Duo (Organization)** option and select the **Manage** button.
|
||||
|
||||
{% image /two-step/duo/enable-org.png Select Manage %}
|
||||
{% image two-step/duo/enable-org.png Select Manage %}
|
||||
|
||||
You will be prompted to enter your Master Password to continue.
|
||||
5. Enter the **Integration Key**, **Secret Key**, and **API Hostname** [retrieved from your Duo Admin Portal](#configure-duo).
|
||||
|
||||
@@ -25,7 +25,7 @@ Complete the following steps to enable Two-step Login using email:
|
||||
3. Select **Two-step Login** from the left-side menu.
|
||||
4. Locate the **Email** option and select the **Manage** button:
|
||||
|
||||
{% image /two-step/twostep-options-emailoverlay.png Select the Manage button %}
|
||||
{% image two-step/twostep-options-emailoverlay.png Select the Manage button %}
|
||||
You will be prompted to enter your Master Password to continue.
|
||||
5. Enter the email that you wish you receive verification codes and click the **Send Email** button.
|
||||
6. Check your inbox for the 6 digit verification code. Enter the code in the dialog box in your Web Vault and select the **Enable** button.
|
||||
|
||||
@@ -24,7 +24,7 @@ To get your Recovery Code from your [Web Vault](https://vault.bitwarden.com){:ta
|
||||
2. Select **Two-step Login** from the left-side Settings menu.
|
||||
3. Select the **View Recovery Code** button near the top of the screen. You'll be prompted to enter your Master Password, which will open a Recovery Code panel:
|
||||
|
||||
{% image /two-step/recoverycode.png Sample Recovery Code %}
|
||||
{% image two-step/recoverycode.png Sample Recovery Code %}
|
||||
|
||||
Save your Recovery Code in the way that makes the most sense for you. Believe it or not, printing your code and keeping it somewhere safe is one of the best ways to ensure that the code isn't vulnerable to theft or inadvertent deletion.
|
||||
|
||||
@@ -48,7 +48,7 @@ Once used, you'll need to:
|
||||
{% callout info %}
|
||||
Recovery Codes **won't disable Duo for Organizations**. You can tell that a Duo prompt is Organization-wide by the **(Organization)** header, as in the following screenshot:
|
||||
|
||||
{% image /two-step/duo/duo-orgs.png Duo (Organization)%}
|
||||
{% image two-step/duo/duo-orgs.png Duo (Organization)%}
|
||||
|
||||
If you're locked out of your Vault by a **Duo (Organization)** prompt, reach out to the Duo Administrator at your company for help bypassing the prompt.
|
||||
{% endcallout %}
|
||||
|
||||
7759
package-lock.json
generated
7759
package-lock.json
generated
File diff suppressed because it is too large
Load Diff
Reference in New Issue
Block a user