mirror of
https://github.com/bitwarden/help
synced 2025-12-06 00:03:30 +00:00
2021-08-18 Release Documentation (#708)
* Stage Providers (#691) * initial provider drafts * fix build errors * image overlays & alt-text * capitalize title * update /about-collections/ for providers * update /about-groups/ for provider users * updating 'sharing' for provider users * update /managing-users/ for provider users * provider - create org permissions fixes * update create org permissions * about-orgs compare to providers * temp remove pricing FAQ item * Update Staging w/ Latest (#695) * initial provider drafts * fix build errors * image overlays & alt-text * capitalize title * update /about-collections/ for providers * update /about-groups/ for provider users * updating 'sharing' for provider users * update /managing-users/ for provider users * provider - create org permissions fixes * update create org permissions * about-orgs compare to providers * temp remove pricing FAQ item * updates from cscharf & gtran review * updates from cscharf & gtran review * Update Staging w/ Latest Again (#696) * initial provider drafts * fix build errors * image overlays & alt-text * capitalize title * update /about-collections/ for providers * update /about-groups/ for provider users * updating 'sharing' for provider users * update /managing-users/ for provider users * provider - create org permissions fixes * update create org permissions * about-orgs compare to providers * temp remove pricing FAQ item * updates from cscharf & gtran review * updates from cscharf & gtran review * updates * Update Staging w/ Latest (#697) * initial provider drafts * fix build errors * image overlays & alt-text * capitalize title * update /about-collections/ for providers * update /about-groups/ for provider users * updating 'sharing' for provider users * update /managing-users/ for provider users * provider - create org permissions fixes * update create org permissions * about-orgs compare to providers * temp remove pricing FAQ item * updates from cscharf & gtran review * updates from cscharf & gtran review * updates * note on freeing up user seat * Update Staging w/ APR v1.0 (#698) * Update to Automatic Enrollment option * update for 'force change on login', image outstanding * reset via email updates, images outstanding * pre-release updates to admin pw reset * Update Staging w/ Latest (#699) * initial provider drafts * fix build errors * image overlays & alt-text * capitalize title * update /about-collections/ for providers * update /about-groups/ for provider users * updating 'sharing' for provider users * update /managing-users/ for provider users * provider - create org permissions fixes * update create org permissions * about-orgs compare to providers * temp remove pricing FAQ item * updates from cscharf & gtran review * updates from cscharf & gtran review * updates * note on freeing up user seat * Updates from recent product changes - title-cased buttons - access vault event + diagram in /article/providers/ * resolve conflict * Updating Staging w/ Latest (#701) * Update "share" -> "move" * resolve conflict * update /sharing/ refs * Update Staging w/ Latest (#702) * Bad link due to typo (#692) * release notes inital * update release notes and index.html to surface admin pw reset in popular articles Co-authored-by: Daniel Pedigo <dpedigo@gmail.com> * update diagram * additional FAQ items, edits from Gina, suggestion to provision 2nd Provider Admin * update CTA for signup * cli auth challenge draft (#706) * Update CLI doc for captcha error, rollback policies article * rollback pw reset article * rollback release notes * update move/share screenshots in provider content * update releasenotes date * faqs & feedback from rluibrand * redirect * resolve conflicts 1/3 * resolve conflicts 2/3 * test resolution for conflict * test resolution for conflict * hide deprecated articles & update links Co-authored-by: Daniel Pedigo <dpedigo@gmail.com>
This commit is contained in:
fred_the_tech_writer
committed by
GitHub
GitHub
parent
b5c2c8e600
commit
25bc445da1
@@ -129,7 +129,7 @@ For more detail, see our [CLI documentation]({% link _articles/miscellaneous/cli
|
||||
|
||||
## Export an Organization Vault
|
||||
|
||||
Organization [Admins and Owners]({% link _articles/organizations/user-types-access-control.md %}) can export their Organization Vault (i.e. all items [shared in Collections]({% link _articles/organizations/share-to-a-collection.md %})) from the Web Vault or CLI:
|
||||
Organization [Admins and Owners]({% link _articles/organizations/user-types-access-control.md %}) can export their Organization Vault (i.e. all items owned by the Organization) from the Web Vault or CLI:
|
||||
|
||||
<ul class="nav nav-tabs" id="myTab" role="tablist">
|
||||
<li class="nav-item" role="presentation">
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
layout: article
|
||||
title: Keyboard shortcuts
|
||||
title: Keyboard Shortcuts
|
||||
categories: [account-management]
|
||||
featured: false
|
||||
popular: false
|
||||
|
||||
@@ -171,9 +171,9 @@ Master password re-prompt **is not** an encryption mechanism. This feature is an
|
||||
|
||||
{% image manage-items/reprompt.gif Master Password Reprompt %}
|
||||
|
||||
## Share Vault Items
|
||||
## Move Items to an Organization
|
||||
|
||||
If you're a member of an [Organization]({{site.baseurl}}/article/about-organizations/), you can share Vault items with other members of your Organization. Learn more about [Organizations]({{site.baseurl}}/article/about-organizations/), [Collections]({{site.baseurl}}/article/about-collections), and [Sharing]({{site.baseurl}}/article/share-to-a-collection/).
|
||||
If you're a member of an [Organization]({{site.baseurl}}/article/about-organizations/), you can move Vault items to your Organization for sharing with other Organization members. Learn more about [Organizations]({{site.baseurl}}/article/about-organizations/), [Collections]({{site.baseurl}}/article/about-collections), and [Sharing]({{site.baseurl}}/article/sharing/).
|
||||
|
||||
## Clone Vault Items
|
||||
|
||||
|
||||
@@ -19,7 +19,7 @@ For more high-level information about **Organizations**, refer to the following
|
||||
|
||||
### Q: What's the difference between Organizations and Premium?
|
||||
|
||||
**A:** Organizations unlock access to secure sharing between users who are members of that Organization.
|
||||
**A:** Organizations enable secure sharing from Organizations to Organization users.
|
||||
|
||||
Premium Individual plans unlock premium password security and management features, including advanced 2FA options, the Bitwarden Authenticator (TOTP), encrypted file attachments, and more. Premium Individual does not include secure data sharing.
|
||||
|
||||
@@ -35,7 +35,7 @@ Paid Organizations (Families, Teams, or Enterprise) automatically include premiu
|
||||
|
||||
**A:** Invited users will receive an email asking them to join the Organization. First, make sure they have accepted the invitation. If they have, a **Admin** or **Owner** should navigate to **Manage** → **People**, hover over that user, open the gear dropdown, and select **Confirm**.
|
||||
|
||||
### Q: What events are auditing for my Organization?
|
||||
### Q: What events are audited for my Organization?
|
||||
|
||||
**A:** For a full list of what's included in Bitwarden Event Logs, see [Event Logs](https://bitwarden.com/help/article/event-logs/).
|
||||
|
||||
@@ -68,6 +68,6 @@ Alternatively, you can unshare items by moving them to a different Collection wi
|
||||
|
||||
**A:** Use the **Hide Passwords** option in the **Access Control** section when adding new users or editing existing ones in order to hide a given Collection's passwords and hidden fields from them. For more information, see [Access Control](https://bitwarden.com/help/article/user-types-access-control/#access-control).
|
||||
|
||||
### Q: Does an item I share with the Organization stay after I leave?
|
||||
### Q: Does an item I move to the Organization stay after I leave?
|
||||
|
||||
**A:** It does! When a user shares an item with an Organization, the Organization takes ownership of the item. Even if the user leaves the Organization or deletes their account, that item will remain in the Organization Vault.
|
||||
|
||||
76
_articles/faqs/providers-faqs.md
Normal file
76
_articles/faqs/providers-faqs.md
Normal file
@@ -0,0 +1,76 @@
|
||||
---
|
||||
layout: article
|
||||
title: Providers FAQs
|
||||
categories: [providers]
|
||||
featured: false
|
||||
popular: false
|
||||
hidden: false
|
||||
tags: []
|
||||
order: 08
|
||||
---
|
||||
|
||||
## Partner Program
|
||||
|
||||
### Q: Does the Partner Program include volume discounts for seats under management?
|
||||
|
||||
**A:** Bitwarden offers a reseller discount to partners based on cumulative seats under management in any Teams and Enterprise Organizations, including any created for use by reseller or MSP employees. To learn more about the discounting structure, please contact sales [here](https://bitwarden.com/contact/){:target="\_blank"}.
|
||||
|
||||
### Q: How are Client Organizations billed?
|
||||
|
||||
**A:** Currently, each Client Organization is billed separately using the payment method registered during [Client Organization creation]({{site.baseurl}}/article/client-org-setup/). In the future, we'll be developing functionality to aggregate billing across Client Organizations to improve the Provider experience.
|
||||
|
||||
### What customer support do MSPs receive?
|
||||
|
||||
**A:** All MSPs receive priority support from our 24/7 customer support team. [Contact Us](https://bitwarden.com/contact/){:target="\_blank"} for support.
|
||||
|
||||
## Provider Portal
|
||||
|
||||
### Q: What is the Provider Portal? Why should I use it?
|
||||
|
||||
**A:** The Provider Portal was designed to streamline multi-Organization control and administration for MSPs across their client's Bitwarden Organizations. Using the Provider Portal, MSPs can:
|
||||
|
||||
- View all clients under MSP management, onboard new and existing clients, access clients' Organization Vaults, and administer services for Teams and Enterprise Organizations.
|
||||
- Add internal staff as users, assign proper user roles, and delegate administrative duties.
|
||||
- View time-stamped actions made by users in the Provider Portal, including creation of new Client Organizations, invitation of new Provider users, and when Provider users access Client Organizations.
|
||||
|
||||
The Provider Portal is an all-in-one portal, designed to streamline client management and operations while increasing value for your clients.
|
||||
|
||||
### Q: Is there a startup or monthly fee for using the Provider Portal?
|
||||
|
||||
**A:** There is no fee for MSPs or their users to use the Provider Portal. It is provided, free of charge, as part of the Bitwarden Partner Program. If you would like to set up an Organization for use by your internal team, those seats will be billed at the discounted rate.
|
||||
|
||||
### Q: I'm already providing Bitwarden as a service for my clients, what do I need to do to move to the Provider Portal?
|
||||
|
||||
**A:** It's quick and easy! [Contact Us](https://bitwarden.com/contact/){:target="\_blank"} and a member of the Bitwarden team will issue you an invitation. Once in the Provider Portal, you can [add existing Client Organizations]({{site.baseurl}}/article/add-existing-client-org/) to begin centralizing client management.
|
||||
|
||||
### Q: How many clients can I manage through the Provider Portal?
|
||||
|
||||
**A:** There is no limit to the number of Client Organizations that can be managed within the Provider Portal.
|
||||
|
||||
### Q:What happens if I am locked out of my Provider Admin account?
|
||||
|
||||
**A:** Access to the Provider Portal is through your Bitwarden account. If you forget your Master Password, Bitwarden has no knowledge of, way to retrieve, or way to reset your Master Password and you will be unable to access the Provider Portal. **Bitwarden strongly recommends that you provision a second user with a Provider Admin role for failover purposes.**
|
||||
|
||||
## Deployment
|
||||
|
||||
### Q: What deployment options are available?
|
||||
|
||||
**A:** Access to the Bitwarden Provider Portal is available through the Bitwarden Cloud service. The Provider Portal is not supported for self-hosted environments at this time.
|
||||
|
||||
## Client Management
|
||||
|
||||
### Q: Is there a recommended workflow for onboarding new clients?
|
||||
|
||||
**A:** Yes! We've outlined one recommended workflow [here]({{site.baseurl}}/article/client-org-setup/).
|
||||
|
||||
### Q: How does an MSP access Client Organizations?
|
||||
|
||||
**A:** MSPs can access all Client Organizations under management from the Provider Portal. Learn more [here]({{site.baseurl}}/article/manage-client-orgs/).
|
||||
|
||||
### Q: Can an MSP administrator see or manage credentials for all clients?
|
||||
|
||||
**A:** Provider Admins and Service Users have the same privileges as Owners in the Client Organization. They can managed Vault items, Collections, Users, Groups, and other functions within the Organization. Provider Admins and Service Users cannot access or view a user's privately-owned Vault items.
|
||||
|
||||
### Q: Can we set default Enterprise Policies that apply to all clients?
|
||||
|
||||
**A:** Each Client Organization operates independently with individually configured policies. [Learn more about configuring Enterprise Policies]({{site.baseurl}}/article/policies/).
|
||||
@@ -69,7 +69,7 @@ You should also find out which Logins Firefox has already saved by selecting the
|
||||
|
||||
{% image features/firefox-delete.png Firefox Saved Logins %}
|
||||
|
||||
If you haven't already saved these passwords in Bitwarden, [export them]({{site.baseurl/article/import-from-firefox}}) for future import to Bitwarden. Once exported, you should {% icon fa-trash %} **Remove** these passwords from Firefox.
|
||||
If you haven't already saved these passwords in Bitwarden, [export them]({{site.baseurl}}/article/import-from-firefox) for future import to Bitwarden. Once exported, you should {% icon fa-trash %} **Remove** these passwords from Firefox.
|
||||
|
||||
{% endcapture %}
|
||||
{{ firefox | markdownify }}
|
||||
|
||||
@@ -10,7 +10,7 @@ order: 07
|
||||
|
||||
Any item can be designated as a **Favorite** allow quick access to your most used items.
|
||||
|
||||
Even items [shared from an Organization]({% link _articles/organizations/share-to-a-collection.md %}) can be designated a Favorite, but this will only impact how they appear in your Personal Vault (i.e. you won't make that item a Favorite for other users with access to the Organization or Collection).
|
||||
Even items [shared with you from an Organization]({% link _articles/organizations/sharing.md %}) can be designated a Favorite, but this will only impact how they appear in your Personal Vault (i.e. you won't make that item a Favorite for other users with access to the Organization or Collection).
|
||||
|
||||
{% callout success %}
|
||||
Items marked as a **Favorite** will appear at the top of your {% icon fa-lock %} **My Vault** view in Browser Extensions and Mobile Apps, and in the {% icon fa-star %} **Favorites** filter in your Web Vault and Desktop Apps.
|
||||
|
||||
@@ -8,7 +8,7 @@ tags: [categories, folders, sub-folders]
|
||||
order: 06
|
||||
---
|
||||
|
||||
Folders are structures used to organize your Personal Vault by gathering together Logins, Cards, Identities, and Secure Notes. Using Folders is a great way to make all Vault items easy to find. Any Vault item can be added to a Folder, including [shared items]({{site.baseurl}}/article/share-to-a-collection/).
|
||||
Folders are structures used to organize your Personal Vault by gathering together Logins, Cards, Identities, and Secure Notes. Using Folders is a great way to make all Vault items easy to find. Any Vault item can be added to a Folder, including [items shared with you from an Organization]({{site.baseurl}}/article/sharing/).
|
||||
|
||||
{% callout success %}
|
||||
Items added to a Folder will still appear in your Vault when {% icon fa-th %} **All Items** is selected from the Filter menu, and deleting a Folder **will not** delete the items in that Folder.
|
||||
@@ -108,7 +108,7 @@ You can edit an existing folder using `bw edit <folderId>` and delete one using
|
||||
{% callout info %}
|
||||
If you're a member of an Organization, **Collections** will be shown below your Folders in the Filters menu.
|
||||
|
||||
There are similarities between Folders and Collections. **Folders organize your Personal Vault** (but can include [shared items]({{site.baseurl}}/article/share-to-a-collection/)) and are unique to you, where Collections are shared between members of Organizations.
|
||||
There are similarities between Folders and Collections. **Folders organize your Personal Vault** (but can include [shared items]({{site.baseurl}}/article/sharing/)) and are unique to you, where Collections are shared between members of Organizations.
|
||||
{% endcallout %}
|
||||
|
||||
### Nested Folders
|
||||
@@ -222,5 +222,5 @@ If you're unfamiliar with using any of these parts, refer to our [CLI documentat
|
||||
</div>
|
||||
|
||||
{% callout success %}
|
||||
Items [shared from an Organization]({{site.baseurl}}/article/share-to-a-collection/) can be added to your personal Folders, and doing so will only impact how the item appears in your Personal Vault (i.e. adding an item to a Folder won't give anyone access to that Folder, or change whether it's in a Folder in their Vaults).
|
||||
Items [shared with you from an Organization]({{site.baseurl}}/article/sharing/) can be added to your personal Folders, and doing so will only impact how the item appears in your Personal Vault (i.e. adding an item to a Folder won't give anyone access to that Folder, or change whether it's in a Folder in their Vaults).
|
||||
{% endcallout %}
|
||||
|
||||
@@ -13,25 +13,25 @@ order: 06
|
||||
|
||||
Password managers like Bitwarden make it easy to store and access unique and secure passwords across all of your devices, keeping your online accounts safer than ever! Using Bitwarden, you won't need to dangerously repeat simple passwords or leave them exposed in unencrypted formats like spreadsheets, documents, or sticky notes.
|
||||
|
||||
**Bitwarden Organizations** add a layer of collaboration and sharing to password management for your family, team, or enterprise, allowing you to securely share common information like office wifi passwords, online credentials, or shared company credit cards. Secure sharing through Organizations is **safe** and **easy**.
|
||||
**Bitwarden Organizations** add a layer of collaboration and sharing to password management for your family, team, or enterprise, allowing you to securely share common information like office wifi passwords, online credentials, or shared company credit cards. Secure sharing of Organization-owned credentials is **safe** and **easy**.
|
||||
|
||||
This article will help you get started with a **free 2-person Organization** so you can experience secure sharing in no time.
|
||||
|
||||
### What are Organizations?
|
||||
|
||||
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:
|
||||
Bitwarden Organizations relate users and Vault items together for [secure sharing]({{site.baseurl}}/article/sharing/) of Logins, Notes, Cards, and Identities owned by the Organization. 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 %}
|
||||
|
||||
#### Comparing Organizations with Premium
|
||||
|
||||
The key thing to know is that **Organizations unlock access to secure sharing** between users. [Premium Individual plans]({{site.baseurl}}/article/about-bitwarden-plans/#premium-individual) unlock premium password security and management features, including advanced 2FA options, the Bitwarden Authenticator (TOTP), encrypted file attachments, and more, but Premium Individual **does not include secure data sharing.**
|
||||
The key thing to know is that Organizations enable **secure sharing from Organizations to users**. [Premium Individual plans]({{site.baseurl}}/article/about-bitwarden-plans/#premium-individual) unlock premium password security and management features, including advanced 2FA options, the Bitwarden Authenticator (TOTP), encrypted file attachments, and more, but Premium Individual **does not include secure data sharing.**
|
||||
|
||||
Paid Organizations (Families, Teams, or Enterprise) automatically include those premium features (advanced 2FA options, Bitwarden Authenticator (TOTP), etc.) for **every** user enrolled in the Organization.
|
||||
|
||||
## Setup Bitwarden Accounts
|
||||
|
||||
Free Bitwarden Organizations allow for 2 users to securely share data. You might use a free Organization to share with friend or partner, or to test Organizations before [upgrading to a different plan]({{site.baseurl}}/article/about-bitwarden-plans/).
|
||||
Free Bitwarden Organizations allow for 2 users to securely share Organization-owned credentials. You might use a free Organization to share with friend or partner, or to test Organizations before [upgrading to a different plan]({{site.baseurl}}/article/about-bitwarden-plans/).
|
||||
|
||||
Bitwarden provides applications on lots of devices, including Browser Extensions, Mobile Apps, Desktop Apps, and a CLI, but for the purposes of this guide we'll focus on the [Web Vault](https://vault.bitwarden.com){:target="\_blank"}. **The Web Vault provides the richest Bitwarden experience** for administering your Organization.
|
||||
|
||||
@@ -49,7 +49,7 @@ Once your account is created, log in to your [Web Vault](https://vault.bitwarden
|
||||
|
||||
### Sign up for Bitwarden again
|
||||
|
||||
In order to use your free 2-person Organization for secure sharing, you'll need to have 2 Bitwarden accounts to share between. Once your first Bitwarden account is setup, follow the same procedure (or help your friend or partner to do so) to setup the other account.
|
||||
In order to use your free 2-person Organization for secure sharing, you'll need to have 2 Bitwarden accounts. Once your first Bitwarden account is setup, follow the same procedure (or help your friend or partner to do so) to setup the other account.
|
||||
|
||||
{% callout success %}
|
||||
Bitwarden Organizations have a deep level of [user-level access controls]({{site.baseurl}}/article/user-types-access-control/). Whichever user you proceed to [setup your Organization](#setup-your-organization) with will be the **Owner**.
|
||||
@@ -74,7 +74,7 @@ Once created, you'll land in your Organization Vault, which is the central hub f
|
||||
|
||||
### 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:
|
||||
Collections are an important part of a Bitwarden Organization; they represent the logical grouping of Organization-owned 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 %}
|
||||
|
||||
@@ -131,27 +131,27 @@ Part of the magic of Bitwarden Organizations is that items that belong to you an
|
||||
|
||||
{% image organizations/personal-vault-org-enabled.png Organization-enabled Vault %}
|
||||
|
||||
[Collections](#get-to-know-collections) are a lot like [Folders]({{site.baseurl}}/article/folders/) in that they organize the shared items in your Vault. Like anything else in the **Filters** menu, selecting a Collection will filter listed Vault items down to only the ones in that Collection.
|
||||
[Collections](#get-to-know-collections) are a lot like [Folders]({{site.baseurl}}/article/folders/) in that they organize the Organization-owned items in your Vault. Like anything else in the **Filters** menu, selecting a Collection will filter listed Vault items down to only the ones in that Collection.
|
||||
|
||||
### Shared Items
|
||||
### Items Shared from an Organization
|
||||
|
||||
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:
|
||||
You probably don't have a [item shared from an organization](#share-a-login) yet, but when you do it will be displayed in your Vault with a {% icon fa-cube %} **Shared** 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.
|
||||
|
||||
## Share a Login
|
||||
## Move an Item to the Organization
|
||||
|
||||
The last step on the road to secure sharing is to create a shared a Vault item. An existing [Vault item]({{site.baseurl}}/article/managing-items/#add-a-vault-item) can be shared after it's created, but for this guide, we'll focus on creating a **new** shared Login from your Personal Vault:
|
||||
The last step on the road to secure sharing is to create an item and move it to the Organization so it can be shared. An existing [Vault item]({{site.baseurl}}/article/managing-items/#add-a-vault-item) can be moved to the Organization after it's created, but for this guide, we'll focus on creating a **new** Login from your Personal Vault:
|
||||
|
||||
1. On the {% icon fa-lock %} **My Vault** page, select the {% icon fa-plus %} **Add Item** button.
|
||||
2. Fill in all the relevant information for your new Login item (e.g. Username and Password). The item can be anything you want both yourself and the other Organization user to have access to, for example a family streaming account.
|
||||
3. In the **Ownership** section at the bottom of the Add Item Panel, select your Organization to designate the item for sharing.
|
||||
4. Select one or more **Collections** to share this item into. Generally, users of two-person Organizations setup access for both users for all Collections. In larger or more complex Organizations, which Collection you share the item into will determine who can access it.
|
||||
5. Select the **Save** button to finishing creating the shared item.
|
||||
4. Select one or more **Collections** to put this item into. Generally, users of two-person Organizations setup access for both users for all Collections. In larger or more complex Organizations, which Collection you put the item into will determine who can access it.
|
||||
5. Select the **Save** button to finishing creating the Organization-owned item.
|
||||
|
||||
This new shared item will be accessible to both yourself and the other Organization user! As long as both users can access the Collection it's in, it will appear for both in the Organization Vault and in the **My Vault** view alongside other personal Vault items.
|
||||
This new item will be accessible to both yourself and the other Organization user! As long as both users can access the Collection it's in, it will appear for both in the Organization Vault and in the **My Vault** view alongside other personal Vault items.
|
||||
|
||||
## Congratulations!
|
||||
|
||||
|
||||
@@ -4,6 +4,7 @@ title: Bitwarden 101 Video Series - Getting Started
|
||||
categories: [getting-started]
|
||||
featured: true
|
||||
popular: false
|
||||
hidden: true
|
||||
tags: [getting started, videos, bitwarden 101]
|
||||
order: 08
|
||||
---
|
||||
|
||||
@@ -126,6 +126,6 @@ To start a premium subscription:
|
||||
|
||||
Do you need to share passwords or other Vault items with your friends, family, team, or entire business?
|
||||
|
||||
Bitwarden Organizations let you do just that. We recommend trying out the functionality of password-sharing Organizations by starting a **free** 2-person Organization. To learn how, see [Get Started with an Organization]({% link _articles/getting-started/getting-started-organizations.md %}).
|
||||
Bitwarden Organizations let you do just that. We recommend trying out the functionality of password-sharing from Organizations by starting a **free** 2-person Organization. To learn how, see [Get Started with an Organization]({% link _articles/getting-started/getting-started-organizations.md %}).
|
||||
|
||||
Once you've tested an Organization, check out our [Bitwarden Plans and Pricing](https://bitwarden.com/pricing/business/) page to learn about the different Paid Organizations you might consider.
|
||||
|
||||
@@ -23,7 +23,7 @@ This guide is designed by our Product, Implementation, and Sales specialists at
|
||||
|2|Create Collections|Organization Owners + Admins|Create [Collections]({{site.baseurl}}/article/about-collections/), which gather items for secure sharing with Groups of users.|[Collections]({{site.baseurl}}/article/about-collections/)|0.25|
|
||||
|2| Create Groups|Organization Owners + Admins|Create [Groups]({{site.baseurl}}/article/about-groups), which gather users for scalable assignment of permissions and access to Collections.<br><br>If you decide to sync Groups and users from your Identity Provider or Directory Service, you may need to reconfigure user and Group assignments later.|[Groups]({{site.baseurl}}/article/groups/)|0.25|
|
||||
|2|Assign Groups to Collections|Organization Owners + Admins| Assign Groups to Collections, making shared items available to supersets of users. Test the *Read Only* and *Hide Password* options.|[Collections Assignment]({{site.baseurl}}/article/about-groups/#edit-collections-assignments)|.5|
|
||||
|2|Share items to Collections|Organization Owners + Admins|[Add items manually]({{site.baseurl}}/article/share-to-a-collection/#create-a-shared-item) or [import data]({{site.baseurl}}/article/import-to-org/) from another password management application.|[Sharing]({{site.baseurl}}/article/share-to-a-collection)<br><br>[Import to an Organization]({{site.baseurl}}/article/import-to-org/)|0.25|
|
||||
|2|Share items to Collections|Organization Owners + Admins|[Add items manually]({{site.baseurl}}/article/sharing/#create-an-organization-item) or [import data]({{site.baseurl}}/article/import-to-org/) from another password management application.|[Sharing]({{site.baseurl}}/article/sharing)<br><br>[Import to an Organization]({{site.baseurl}}/article/import-to-org/)|0.25|
|
||||
|2|Configure Enterprise Policies|Organization Owners + Admins|Enterprise Policies can be used to tailor your Bitwarden Organization to fit your security needs. **Enable and configure desired policies before user onboarding begins.**|[Enterprise Policies]({{site.baseurl}}/article/policies/)|0.1|
|
||||
|3|Add users to Groups|Organization Owners + Admins|Add a set of users to your Organization manually and assign them to different groups. With these users, you'll broadly test all pre-configured functionality **in the next step**, before moving on to advanced functions like Directory Connector.|[User Management]({{site.baseurl}}/article/managing-users/)<br><br>[Groups]({{site.baseurl}}/article/about-groups/)|0.5|
|
||||
|3|Download Bitwarden Client Applications|All users|All Organization members should download Bitwarden on an assortment of devices, login, and test access to shared items/Collections/Groups and application of applied Policies. **If you're self-hosting,** users will need to [connect each client to your server]({{site.baseurl}}/article/change-client-environment).|[Download Bitwarden](https://get.bitwarden.com/)|0.5|
|
||||
|
||||
@@ -25,6 +25,20 @@ Bitwarden believes source code transparency is an absolute requirement for secur
|
||||
|
||||
To be notified of Release Announcements, subscribe to the [Bitwarden Status RSS Feed](https://status.bitwarden.com/){:target="\_blank"}.
|
||||
|
||||
## 2021-08-18
|
||||
|
||||
{% callout success %}
|
||||
Interested in becoming a Provider? Contact us to get started for free:
|
||||
|
||||
<a role="button" class="btn btn-primary" href="https://bitwarden.com/contact" target="blank">Contact Us</a>
|
||||
{% endcallout %}
|
||||
|
||||
The latest release of Bitwarden is focused on enabling Managed Service Providers (MSPs) to support their customers' password management needs:
|
||||
|
||||
- **Provider Portal**: The Provider Portal allows Managed Service Providers (MSPs), Resellers, and other businesses to create and administer Organizations on behalf of customers. Using the Portal, Providers can seamlessly support credential management across multiple customers (see [here]({{site.baseurl}}/article/getting-started-providers/) for details).
|
||||
- **Share Verbiage Change**: We've updated the {% icon fa-share-alt %} **Share** button to {% icon fa-arrow-circle-o-right %} **Move to Organization** to make it cleared that shared items are owned by the Organization. Additionally, we've updated the "shared item" indicator ({% icon fa-share-alt %}) to match the Collections indicator ({% icon fa-cube %}).
|
||||
- **CLI `move` Command**: In keeping with the above item, the CLI `share` command has been changed to `move` (see [here]({{site.baseurl}}/article/cli/#move) for details).
|
||||
|
||||
## 2021-06-29
|
||||
|
||||
The Bitwarden team is happy to announce the rollout of Admin Password Reset, the latest feature purpose-built to help enterprises seeking to ensure password security at scale. This release includes:
|
||||
|
||||
@@ -46,7 +46,7 @@ Most Mobile Device Management (MDM) or Enterprise Mobility Management (EMM) solu
|
||||
To centrally configure the Desktop app for deployment, first complete the following steps on a single workstation:
|
||||
|
||||
1. Install the Desktop app. If you're using Windows, silent install Bitwarden using `installer.exe /S` (see [NSIS documentation](https://nsis.sourceforge.io/Docs/Chapter4.html#silent){:target="\_blank"}).
|
||||
2. Navigate to the Desktop app's locally stored settings. This directory is different depending on your OS (e.g. `%AppData%\Bitwarden` on Windows, `~/Library/Application Support/Bitwarden` on macOS). [Find your directory.]({{site.baseurl/article/data-storage/}})
|
||||
2. Navigate to the Desktop app's locally stored settings. This directory is different depending on your OS (e.g. `%AppData%\Bitwarden` on Windows, `~/Library/Application Support/Bitwarden` on macOS). [Find your directory.]({{site.baseurl}}/article/data-storage/)
|
||||
3. In the directory, open the `data.json` file.
|
||||
4. Edit `data.json` to configure the Desktop app as desired. In particular, create the following object to configure the app with your self-hosted Server URL:
|
||||
|
||||
|
||||
@@ -11,7 +11,7 @@ order:
|
||||
|
||||
This article contains **JumpCloud-specific** help for configuring Login with SSO via SAML 2.0. For help configuring Login with SSO for another IdP, refer to [SAML 2.0 Configuration]({{site.baseurl}}/article/configure-sso-saml/).
|
||||
|
||||
Configuration involves working simultaneously within the Bitwarden [Business Portal]({{site.baseurl//article/about-business-portal/}}) and the JumpCloud Portal. As you proceed, we recommend having both readily available and completing steps in the order they're documented.
|
||||
Configuration involves working simultaneously within the Bitwarden [Business Portal]({{site.baseurl}}/article/about-business-portal/) and the JumpCloud Portal. As you proceed, we recommend having both readily available and completing steps in the order they're documented.
|
||||
|
||||
## Open the Business Portal
|
||||
|
||||
|
||||
55
_articles/miscellaneous/cli-auth-challenges.md
Normal file
55
_articles/miscellaneous/cli-auth-challenges.md
Normal file
@@ -0,0 +1,55 @@
|
||||
---
|
||||
layout: article
|
||||
title: CLI Authentication Challenges
|
||||
categories: [miscellaneous]
|
||||
featured: false
|
||||
popular: false
|
||||
tags: [cli, captcha]
|
||||
---
|
||||
|
||||
The August 2021 release of Bitwarden (**2021-08-18**) introduced [Captcha](https://www.hcaptcha.com/about){:target="\_blank"} requirements to increase security against bot traffic. On the CLI, Captcha challenges are substituted with authentication challenges that can validated using your account's [Personal API Key]({{site.baseurl}}/article/personal-api-key) `client_secret`.
|
||||
|
||||
## Get your Personal API Key
|
||||
|
||||
To get your Personal API Key:
|
||||
|
||||
1. Log in to the [Web Vault](https://vault.bitwarden.com){:target="\_blank"} and select the **Settings** tab.
|
||||
2. From the **My Account** screen, scroll down to the **API Key** section.
|
||||
3. Select the **View API Key** button and enter your Master Password to validate access.
|
||||
4. From the **API Key** dialog box, copy the **client_secret:** value, which is a random string like `efrbgT9C6BogEfXi5pZc48XyJjfpR`.
|
||||
|
||||
## Answering Challenges
|
||||
|
||||
Depending on your preferences, you can [save an environment variable](#answer-challenges-with-an-environment-variable) to automatically pass authentication challenges or [manually enter](#using-the-prompt) your `client_secret` whenever a challenge is made:
|
||||
|
||||
{% callout success %}
|
||||
Aside from using environment variable, any possible challenge is automatically bypassed when using the `bw login --apikey` method. [Learn more]({{site.baseurl}}/article/cli/#using-an-api-key).
|
||||
{% endcallout %}
|
||||
|
||||
### Answer Challenges with an Environment Variable
|
||||
|
||||
Authentication challenges will look for a non-empty environment variables `BW_CLIENTSECRET` before prompting you to enter one manually. Saving this variable with the [retrieved client_secret value](#get-your-personal-api-key) will allow you to automatically pass authentication challenges. To save this environment variable:
|
||||
|
||||
{% icon fa-linux %} {% icon fa-apple %} Bash
|
||||
```
|
||||
export BW_CLIENTSECRET="client_secret"
|
||||
```
|
||||
|
||||
{% icon fa-windows %} PowerShell
|
||||
```
|
||||
env:BW_CLIENTSECRET="client_secret"
|
||||
```
|
||||
|
||||
{% callout warning %}
|
||||
If your `client_secret` is incorrect, you will receive an error. In most cases, this is because you have [rotated your API Key]({{site.baseurl}}/article/personal-api-key/#rotate-your-api-key) since saving the variable. [Use the above steps](#get-your-personal-api-key) to retrieve the correct value.
|
||||
{% endcallout %}
|
||||
|
||||
### Answer Challenges Manually
|
||||
|
||||
When an authentication challenge is made and no `BW_CLIENTSECRET` value is found, you will be prompted to manually enter your `client_secret` value:
|
||||
|
||||
{% image cli/cli-captcha-1-markup.png Login Prompt with Auth Challenge %}
|
||||
|
||||
{% callout warning %}
|
||||
If your `client_secret` is incorrect, you will receive an error. In most cases, this is because you have [rotated your API Key]({{site.baseurl}}/article/personal-api-key/#rotate-your-api-key) since saving the variable. [Use the above steps](#get-your-personal-api-key) to retrieve the correct value.
|
||||
{% endcallout %}
|
||||
@@ -21,7 +21,7 @@ Or, pass `--help` as an option on any `bw` command to see available options and
|
||||
```
|
||||
bw list --help
|
||||
|
||||
bw share --help
|
||||
bw move --help
|
||||
```
|
||||
|
||||
Most information you'll need can be accessed using `--help`, however this article replicates all that information and goes into greater depth on some topics.
|
||||
@@ -157,6 +157,10 @@ See [Appendices → Enums](#enums) for `<method>` values.
|
||||
|
||||
### Using an API key
|
||||
|
||||
{% callout success %}
|
||||
**Getting prompted for additional authentication** or getting a `Your authentication request appears to be coming from a bot.` error? Use your API Key `client_secret` to answer the authentication challenge. [Learn more]({{site.baseurl}}/article/cli-auth-challenges/).
|
||||
{% endcallout %}
|
||||
|
||||
Logging in with a [Personal API Key]({{site.baseurl}}/article/personal-api-key/) authenticates you with Bitwarden servers, syncs your Vault, but **does not unlock your Vault**. After logging in with an API key, you will be required to unlock your Vault using your Master Password. To log in with an API key use:
|
||||
|
||||
```
|
||||
@@ -479,18 +483,22 @@ bw list org-collections --organizationid 4016326f-98b6-42ff-b9fc-ac63014988f5
|
||||
You can `bw list` both `collections` and `org-collections`. `bw list collections` will list *all* Collections, agnostic of which Organization they belong to. `bw list org-collections` will list *only* Collections that belong to the Organization specified using `--organizationid`.
|
||||
{% endcallout %}
|
||||
|
||||
### share
|
||||
### move
|
||||
|
||||
The `share` command transfers a Vault item [to an Organization]({{site.baseurl}}/article/share-to-a-collection/):
|
||||
{% callout info %}
|
||||
**August 2021**: The `share` command has been changed to `move`. [Find out more]({{site.baseurl}}/article/release-notes).
|
||||
{% endcallout %}
|
||||
|
||||
The `move` command transfers a Vault item [to an Organization]({{site.baseurl}}/article/sharing/):
|
||||
|
||||
```
|
||||
bw share <itemid> <organizationid> [encodedJson]
|
||||
bw move <itemid> <organizationid> [encodedJson]
|
||||
```
|
||||
|
||||
The `share` command requires you to `encode` a Collection ID, and takes an **exact** `id` (the object to share) and an **exact** `organizationid` (the Organization to share the object to). For example:
|
||||
The `move` command requires you to `encode` a Collection ID, and takes an **exact** `id` (the object to share) and an **exact** `organizationid` (the Organization to share the object to). For example:
|
||||
|
||||
```
|
||||
echo '["bq209461-4129-4b8d-b760-acd401474va2"]' | bw encode | bw share ed42f44c-f81f-48de-a123-ad01013132ca dfghbc921-04eb-43a7-84b1-ac74013bqb2e
|
||||
echo '["bq209461-4129-4b8d-b760-acd401474va2"]' | bw encode | bw move ed42f44c-f81f-48de-a123-ad01013132ca dfghbc921-04eb-43a7-84b1-ac74013bqb2e
|
||||
```
|
||||
|
||||
Upon success, the updated item will be returned.
|
||||
|
||||
@@ -13,10 +13,10 @@ redirect_from:
|
||||
|
||||
## What are Collections?
|
||||
|
||||
Collections gather together Logins, Notes, Cards, and Identities for [secure sharing]({{site.baseurl}}/article/share-to-a-collection/) within an Organization. Think of Collections as Organization-equivalents to the [Folders]({{site.baseurl}}/article/folders/) used to organize a Personal Vault, with a few key differences:
|
||||
Collections gather together Logins, Notes, Cards, and Identities for [secure sharing]({{site.baseurl}}/article/sharing/) from an Organization. Think of Collections as Organization-equivalents to the [Folders]({{site.baseurl}}/article/folders/) used to organize a Personal Vault, with a few key differences:
|
||||
|
||||
- Organizations control access to shared items by assigning users or [Groups]({{site.baseurl}}/article/about-groups/) to Collections.
|
||||
- Shared items **must** be included in at least one Collection.
|
||||
- Organizations control access to Organization-owned items by assigning users or [Groups]({{site.baseurl}}/article/about-groups/) to Collections.
|
||||
- Organization-owned items **must** be included in at least one Collection.
|
||||
|
||||
### Using Collections
|
||||
|
||||
@@ -32,7 +32,7 @@ Other common methodologies include **Collections by Vendor or System** (i.e. use
|
||||
|
||||
## Create a Collection
|
||||
|
||||
Users with the [Manager role (or higher)]({{site.baseurl}}/article/user-types-access-control/) can create and manage Collections. To create a Collection:
|
||||
Organization [Managers (or higher)]({{site.baseurl}}/article/user-types-access-control/) and [Provider Users]({{site.baseurl}}/article/provider-users/provider-user-types) can create and manage Collections. To create a Collection:
|
||||
|
||||
1. Log in to your [Web Vault](https://vault.bitwarden.com){:target="\_blank"} and open your Organization.
|
||||
2. Open the **Manage** tab and select the {% icon fa-plus %} **New Collection** button:
|
||||
|
||||
@@ -29,7 +29,7 @@ Other common methodologies include **Collections by Vendor or System** (i.e. use
|
||||
|
||||
## Create a Group
|
||||
|
||||
Users with the [Admin role (or higher)]({{site.baseurl}}/article/user-types-access-control/#user-types) can create and manage Groups. To create a Group:
|
||||
Organization [Admins (or higher)]({{site.baseurl}}/article/user-types-access-control/#user-types) and [Provider Users]({{site.baseurl}}/article/provider-users/provider-user-types) can create and manage Groups. To create a Group:
|
||||
|
||||
1. Log in to your [Web Vault](https://vault.bitwarden.com){:target="\_blank"} and open your Organization.
|
||||
2. Open the **Manage** tab and select **Groups** from the left-hand menu.
|
||||
|
||||
@@ -13,13 +13,13 @@ redirect_from:
|
||||
|
||||
## What are Organizations?
|
||||
|
||||
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:
|
||||
Organizations relate Bitwarden users and Vault items together for [secure sharing]({{site.baseurl}}/article/sharing/) 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 %}
|
||||
|
||||
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:
|
||||
Members of an Organization will find shared items ({% icon fa-cube%}) 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/personal-vault-org-enabled.png Access shared items %}
|
||||
|
||||
### Types of Organizations
|
||||
|
||||
@@ -34,10 +34,14 @@ Bitwarden offers a variety of types of Organizations to meet your business's or
|
||||
|
||||
### Comparing Organizations with Premium
|
||||
|
||||
The key thing to know is that **Organizations unlock access to secure sharing** between users. [Premium Individual plans]({{site.baseurl}}/article/about-bitwarden-plans/#premium-individual) unlock premium password security and management features, including advanced 2FA options, the Bitwarden Authenticator (TOTP), encrypted file attachments, and more, but Premium Individual **does not include secure data sharing.**
|
||||
The key thing to know is that Organizations enable **secure sharing from Organizations to users**. [Premium Individual plans]({{site.baseurl}}/article/about-bitwarden-plans/#premium-individual) unlock premium password security and management features, including advanced 2FA options, the Bitwarden Authenticator (TOTP), encrypted file attachments, and more, but Premium Individual **does not include secure data sharing.**
|
||||
|
||||
Paid Organizations (Families, Teams, or Enterprise) automatically include those premium features (advanced 2FA options, Bitwarden Authenticator (TOTP), etc.) for **every** user enrolled in the Organization.
|
||||
|
||||
### Comparing Organizations with Providers
|
||||
|
||||
[Providers]({{site.baseurl}}/article/providers) are Vault-administration entities that allow businesses like Managed Service Providers (MSPs) to quickly create and administer **multiple Bitwarden Organizations** on behalf of business customers.
|
||||
|
||||
## Create an Organization
|
||||
|
||||
Organizations are created and managed from the [Web Vault](https://vault.bitwarden.com){:target="\_blank"}. If you're new to Bitwarden, [create an account](https://vault.bitwarden.com/#/register){:target="\_blank"} before you start your Organization, then proceed with these instructions:
|
||||
@@ -60,4 +64,4 @@ Organizations are created and managed from the [Web Vault](https://vault.bitward
|
||||
|
||||
{% callout success %}New Families, Teams, and Enterprise Organization have a 7 day free trial built in! We won't charge you until your trial is over, and you can cancel your subscription at any time from the Organization **Settings** tab.{% endcallout %}
|
||||
|
||||
Once you've created your Organization, create a [collection]({{site.baseurl}}/article/about-collections/), [invite users]({{site.baseurl}}/article/managing-users/), and [start sharing]({{site.baseurl}}/article/share-to-a-collection).
|
||||
Once you've created your Organization, create a [collection]({{site.baseurl}}/article/about-collections/), [invite users]({{site.baseurl}}/article/managing-users/), and [start sharing]({{site.baseurl}}/article/sharing).
|
||||
|
||||
@@ -4,7 +4,7 @@ title: Deploying Bitwarden as an MSP
|
||||
categories: [organizations]
|
||||
featured: false
|
||||
popular: false
|
||||
hidden: false
|
||||
hidden: true
|
||||
tags: [MSPs, Organizations, Collections, Groups]
|
||||
order: 16
|
||||
---
|
||||
|
||||
@@ -86,6 +86,12 @@ https://github.com/bitwarden/web/blob/master/src/app/services/event.service.ts
|
||||
https://github.com/bitwarden/web/blob/master/src/locales/en/messages.json
|
||||
{% endcomment %}
|
||||
|
||||
### Provider Events
|
||||
|
||||
When any of the above events is executed by a member of an [administering Provider]({{site.baseurl}}/article/providers/), the **User** column will record the name of the Provider. Additionally, a Provider-specific event will record whenever a member of an administering Provider accesses your Organization Vault:
|
||||
|
||||
`IMAGE PLACEHOLDER`
|
||||
|
||||
## Export Events
|
||||
|
||||
Exporting event logs will create a `.csv` of all events within the specified date range:
|
||||
|
||||
@@ -1,98 +0,0 @@
|
||||
---
|
||||
layout: article
|
||||
title: Collections & Groups Best Practices
|
||||
categories: []
|
||||
featured: true
|
||||
popular: false
|
||||
tags: [collections, groups, access control]
|
||||
order:
|
||||
---
|
||||
|
||||
As your organization’s use of Bitwarden grows, it helps to have users who can manage collections independently, without requiring access to everything within the organizational vault.
|
||||
|
||||
Managing collections and groups is a simple way to separate, grant, or limit access to vault items in Bitwarden, thereby controlling user visibility of resources.
|
||||
|
||||
A complete list of roles and access control can be seen in the help note [User Types and Access Control](https://bitwarden.com/help/article/user-types-access-control/), and a table is at the end of this post.
|
||||
|
||||
We will review the **Manager** use case and the capabilities that role has in creating and managing collections.
|
||||
|
||||
Before addressing collection management, let’s review **Collections**, **Groups**, and **Folders** within Bitwarden:
|
||||
|
||||
- A **Collection** within Bitwarden is a set of related items, such as login credentials, shared within an organization’s vault. The items are grouped together according to whatever classification structure the organization administrator chooses -- for example by department such as sales or operations, or type of account such as shipping, ecommerce, or social media. You can think of a collection as analogous to a folder, but for organizational items
|
||||
- A **Group** within Bitwarden is a set of authorized Bitwarden users -- in a business this could be Marketing, Sales, or Operations. Groups are available in Bitwarden Enterprise
|
||||
- For reference, a **Folder** is a set of items within a personal vault the same way that a **Collection** is a set of items in an organization vault. Folders are not part of this article on **Collections**
|
||||
|
||||
## The Manager Role within Bitwarden
|
||||
When a user is granted a Manager role by an organization Admin or Owner, they are given access to manage the collections of which they are a part. The Manager role has fewer permissions than that Owner or Admin roles.
|
||||
|
||||
In this example, our user is a manager of the following collections. Each of these collections represents numerous shared items.
|
||||
|
||||
- Customer Success
|
||||
- Employees
|
||||
- IT
|
||||
- Marketing
|
||||
- Sales
|
||||
|
||||
And this user can create a **New Collection** via the button on the top right
|
||||
|
||||
{% image collections/bitwarden-collections-manage.png %}
|
||||
|
||||
## Adding New Collections and Groups
|
||||
After clicking **New Collection**, the user is prompted to enter the Name and External ID.
|
||||
|
||||
From there the Manager of the collection can assign groups to the newly created collection.
|
||||
|
||||
{% callout info %}
|
||||
Groups are available in Bitwarden Enterprise
|
||||
{% endcallout % }
|
||||
|
||||
{% image collections/bitwarden-collections-add-new.png %}
|
||||
|
||||
For each Group added, additional options such as Hide Passwords and Read Only are available.
|
||||
|
||||
**Read Only**
|
||||
Selecting this option will prevent users assigned to this collection from adding new items, and editing or deleting existing items.
|
||||
|
||||
**Hide Passwords**
|
||||
This option hides passwords, TOTP seeds, and any custom fields of type hidden in this collection. This also disables the ability for an end-user to copy a password. In this configuration, an item may only be used with auto-fill.
|
||||
|
||||
{% callout warning %}
|
||||
Enabling hidden passwords prevents the easy copy and paste of hidden items, however it does not completely prevent user access to this information. Please treat hidden passwords as you would any shared credential.
|
||||
{% endcallout %}
|
||||
|
||||
### Adding items to a Collection
|
||||
When residing within the view of a collection in the web vault, new items will be saved within the collection.
|
||||
|
||||
Items within a personal vault can be shared with a collection as well. Simply click on the **Settings** icon in the web vault, or edit the item in the browser extension to share it with the appropriate collection.
|
||||
|
||||
**Unsharing items from a Collection**
|
||||
|
||||
Once an item has been shared with an organizational vault, it cannot be unshared back to a personal vault in a single step. This is an intentional design. Users must consider any item shared as being available for all authorized users until that item is both unshared AND the password is changed.
|
||||
|
||||
The recommended procedure to unshare an item is:
|
||||
|
||||
- Clone the item in the organization vault
|
||||
- Collection Owners or Admins can share back to their personal vaults
|
||||
- Collection Managers can share within a private collection
|
||||
- Delete the original organizational item
|
||||
- Change the password on the cloned item now in a private collection
|
||||
|
||||
## Adding Individuals to a Collection
|
||||
Managers can also add individual users to collections via the **Settings** icon next to a created collection.
|
||||
|
||||
|
||||
{% image collections/bitwarden-collections-settings-add-users.png %}
|
||||
|
||||
After selecting the Users option, a list of individuals within the organization will appear.
|
||||
|
||||
{% image collections/bitwarden-collections-add-users.png %}
|
||||
|
||||
With these capabilities in place, individual employees empowered as Managers will be able to create their own new collections, and add groups and users to those collections. They also have the ability to manage collections created by another manager.
|
||||
|
||||
{% callout info %}
|
||||
Managers do not have access to change the composition of Groups. For that access, Admin or Owner roles are required. For example, if a Manager creates a collection of **Design Services** and adds the **Marketing** group to have access, and a user is removed from the Marketing group by the Admin, then that user will no longer have access to the Design Services collection.
|
||||
{% endcallout %}
|
||||
|
||||
### Table of User Roles and Access
|
||||
|
||||
{% image collections/user-roles-access-control-table.png %}
|
||||
@@ -10,10 +10,10 @@ order: 05
|
||||
|
||||
## Manage User Seats
|
||||
|
||||
Bitwarden [Teams and Enterprise Organizations]({{site.baseurl}}/article/about-organizations/#types-of-organizations) allow you to add or remove user seats on-the-fly to best fit your business's needs. Only the [Organization Owner]({{site.baseurl}}/article/user-types-access-control/#user-types) can add and remove seats, as this directly affects your billing.
|
||||
Bitwarden [Teams and Enterprise Organizations]({{site.baseurl}}/article/about-organizations/#types-of-organizations) allow you to add or remove user seats on-the-fly to best fit your business's needs. Only an [Organization Owner]({{site.baseurl}}/article/user-types-access-control/#user-types) or [Provider Service User]({{site.baseurl}}/article/provider-users/#provider-user-types) can add and remove seats, as this directly affects billing.
|
||||
|
||||
{% callout info %}
|
||||
If you have a [Free or Families Organization]({{site.baseurl}}/article/about-organizations/#types-of-organizations), your user seats are pre-loaded and fixed at 2 and 6, respectively. Proceed to [Onboard Users](#onboard-users).
|
||||
If you have a [Free or Families Organization]({{site.baseurl}}/article/about-organizations/#types-of-organizations), your user seats are pre-loaded and fixed at 2 and 6, respectively.
|
||||
{% endcallout %}
|
||||
|
||||
### Add Seats
|
||||
|
||||
@@ -81,7 +81,7 @@ Once created, you'll land in your Organization Vault, which is the central hub f
|
||||
|
||||
Bitwarden Organizations manage users and data in a scalable and secure fashion. Managing users and data on an individual basis is inefficient for large businesses and can leave room for error. To solve this, Organizations provide Collections and [Groups](#groups).
|
||||
|
||||
**Collections** gather together Logins, Notes, Cards, and Identities for [secure sharing]({{site.baseurl}}/article/share-to-a-collection/) within an Organization:
|
||||
**Collections** gather together Logins, Notes, Cards, and Identities for [secure sharing]({{site.baseurl}}/article/sharing/) within an Organization:
|
||||
|
||||
{% image organizations/collections-graphic-1.png Using Collections %}
|
||||
|
||||
|
||||
@@ -4,7 +4,7 @@ title: Sharing
|
||||
categories: [organizations]
|
||||
featured: false
|
||||
popular: false
|
||||
hidden: false
|
||||
hidden: true
|
||||
tags: [sharing, how to]
|
||||
order: 04
|
||||
---
|
||||
|
||||
94
_articles/organizations/sharing.md
Normal file
94
_articles/organizations/sharing.md
Normal file
@@ -0,0 +1,94 @@
|
||||
---
|
||||
layout: article
|
||||
title: Sharing
|
||||
categories: [organizations]
|
||||
featured: false
|
||||
popular: false
|
||||
hidden: false
|
||||
tags: [sharing, how to]
|
||||
order: 04
|
||||
redirect_from:
|
||||
- /article/share-to-a-collection/
|
||||
---
|
||||
|
||||
{% callout info %}
|
||||
In order to share items you need to be a member of an Organization. Learn more about [Organizations]({% link _articles/organizations/about-organizations.md %}) or learn how to [start your own two-person Organization]({{site.baseurl}}/article/getting-started-organizations/).
|
||||
{% endcallout %}
|
||||
|
||||
Sharing items with Bitwarden means moving them into an Organization and Collection, a structure used to gather together Logins, Notes, Cards, and Identities for access by multiple users. There are a few different ways you can create Organization items for sharing:
|
||||
|
||||
## Move an Item to an Organization
|
||||
|
||||
Organization members can move items to any assigned Collection(s) unless they're given [**Read Only** access]({% link _articles/organizations/user-types-access-control.md %}) to that Collection. Items can only be moved to Organizations **from the Web Vault**:
|
||||
|
||||
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 %}
|
||||
|
||||
2. From the dropdown, select the {% icon fa-arrow-circle-o-right %} **Move to Organization** option.
|
||||
3. On the **Move to Organization** screen:
|
||||
|
||||
- Choose the **Organization** to share this item with.
|
||||
- Select one or more **Collections** to share this item into. You must select _at least_ one Collection.
|
||||
|
||||
4. Click **Save** to finishing moving this item for sharing.
|
||||
|
||||
Moving an item to an Organization **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-cube %} **Shared** icon next to its name:
|
||||
|
||||
{% image /organizations/collection-shared-item.png Shared Item icon %}
|
||||
|
||||
## Create an Organization Item
|
||||
|
||||
Organization members can create new items directly for any assigned Collection(s) unless they're given [**Read Only** access](https://bitwarden.com/help/article/user-types-access-control/) to that Collection. Shared items can only be created **from the Web Vault**, either in your My Vault view or in the Organization view:
|
||||
|
||||
<ul class="nav nav-tabs" id="myTab" role="tablist">
|
||||
<li class="nav-item" role="presentation">
|
||||
<a class="nav-link active" id="pertab" data-bs-toggle="tab" data-target="#personal" role="tab" aria-controls="pertab" aria-selected="true">My Vault View</a>
|
||||
</li>
|
||||
<li class="nav-item" role="presentation">
|
||||
<a class="nav-link" id="orgtab" data-bs-toggle="tab" data-target="#organization" role="tab" aria-controls="orgtab" aria-selected="false">Organization View</a>
|
||||
</li>
|
||||
</ul>
|
||||
<div class="tab-content" id="clientsContent">
|
||||
<div class="tab-pane show active" id="personal" role="tabpanel" aria-labelledby="pertab">
|
||||
{% capture personal %}
|
||||
|
||||
#### From the My Vault view
|
||||
|
||||
To create a new shared item:
|
||||
|
||||
1. On the {% icon fa-lock %} **My Vault** page, select the {% icon fa-plus %} **Add Item** button.
|
||||
2. Fill in all the relevant information for the new Vault item.
|
||||
3. In the **Ownership** section at the bottom of the Add Item panel, choose the Organization you want to share this item with.
|
||||
4. Select one or more **Collections** to share this item into. You must select _at least_ one Collection.
|
||||
5. Select the **Save** button to finishing creating the 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-cube %} **Shared** icon next to its name:
|
||||
|
||||
{% image /organizations/collection-shared-item.png Shared Item icon %}
|
||||
|
||||
{% endcapture %}
|
||||
{{ personal | markdownify }}
|
||||
|
||||
</div>
|
||||
<div class="tab-pane" id="organization" role="tabpanel" aria-labelledby="orgtab">
|
||||
{% capture organization %}
|
||||
|
||||
#### From the Organization view
|
||||
|
||||
To create a new shared item:
|
||||
|
||||
1. On your Organization's {% icon fa-lock %} **Vault** tab, select the {% icon fa-plus %} **Add Item** button.
|
||||
2. Fill in all the relevant information for the new Vault item.
|
||||
3. The Ownership of the item is automatically set to the Organization when you use this method, so all you need to do is select one or more **Collections** to share this item into. You must select _at least_ one Collection.
|
||||
4. Select the **Save** button to finishing creating the 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-cube %} **Shared** icon next to its name:
|
||||
|
||||
{% image /organizations/collection-shared-item.png Shared Item icon %}
|
||||
|
||||
{% endcapture %}
|
||||
{{ organization | markdownify }}
|
||||
|
||||
</div>
|
||||
</div>
|
||||
@@ -16,9 +16,9 @@ As your renewal date approaches, Bitwarden recommends that you validate the paym
|
||||
{% callout warning %}
|
||||
If we cannot process your payment method, or if you have cancelled your subscription, your Organization will be disabled. For **self-hosted customers**, there is a 2 month grace period between expiration of your [license]({{site.baseurl}}/article/licensing-on-premise/#organization-license) and disabling of your Organization. In either case, a disabled Organization will result in the following:
|
||||
|
||||
**Shared Vault Items**
|
||||
**Organization-owned Vault Items**
|
||||
|
||||
[Owners]({{site.baseurl}}/article/user-types-access-control/) will retain access to [shared Vault items]({{site.baseurl}}/article/share-to-a-collection), however all other users will lose access to these items. Shared Vault items and existing [Collections]({{site.baseurl}}/article/about-collections/) **will not be deleted**.
|
||||
[Owners]({{site.baseurl}}/article/user-types-access-control/) will retain access to [shared Vault items]({{site.baseurl}}/article/sharing), however all other users will lose access to these items. Organization Vault items and existing [Collections]({{site.baseurl}}/article/about-collections/) **will not be deleted**.
|
||||
|
||||
**Organization Users**
|
||||
|
||||
|
||||
@@ -8,7 +8,7 @@ hidden: false
|
||||
tags: [account, individual, organization, premium, subscription]
|
||||
order: 03
|
||||
---
|
||||
This article will guide existing individual Bitwarden users ([**Free**](https://bitwarden.com/help/article/about-bitwarden-plans/#free-individual) or [**Premium**](https://bitwarden.com/help/article/about-bitwarden-plans/#premium-individual)) through the process of transitioning to an Organizations plan ([**Free**](https://bitwarden.com/help/article/about-bitwarden-plans/#free-organizations), [**Families**](https://bitwarden.com/help/article/about-bitwarden-plans/#families-organizations), [**Teams**](https://bitwarden.com/help/article/about-bitwarden-plans/#teams-organizations), or [**Enterprise**](https://bitwarden.com/help/article/about-bitwarden-plans/#enterprise-organizations)) in order to start securely sharing data between friends, family, co-workers, a department, or an entire company.
|
||||
This article will guide existing individual Bitwarden users ([**Free**](https://bitwarden.com/help/article/about-bitwarden-plans/#free-individual) or [**Premium**](https://bitwarden.com/help/article/about-bitwarden-plans/#premium-individual)) through the process of transitioning to an Organizations plan ([**Free**](https://bitwarden.com/help/article/about-bitwarden-plans/#free-organizations), [**Families**](https://bitwarden.com/help/article/about-bitwarden-plans/#families-organizations), [**Teams**](https://bitwarden.com/help/article/about-bitwarden-plans/#teams-organizations), or [**Enterprise**](https://bitwarden.com/help/article/about-bitwarden-plans/#enterprise-organizations)) in order to start securely sharing data from Organizations with friends, family, co-workers, a department, or an entire company.
|
||||
|
||||
## Start Your Organization
|
||||
|
||||
@@ -66,4 +66,4 @@ Now that you've created your Organization, we recommend that you:
|
||||
|
||||
- [Invite Users to Your Organization](https://bitwarden.com/help/article/managing-users)
|
||||
- [Create a Collection](https://bitwarden.com/help/article/about-collections/#create-a-collection)
|
||||
- [Share Items to a Collection](https://bitwarden.com/help/article/share-to-a-collection/)
|
||||
- [Share Items to a Collection](https://bitwarden.com/help/article/sharing/)
|
||||
|
||||
29
_articles/providers/add-existing-client-org.md
Normal file
29
_articles/providers/add-existing-client-org.md
Normal file
@@ -0,0 +1,29 @@
|
||||
---
|
||||
layout: article
|
||||
title: Add Existing Organizations
|
||||
categories: [providers]
|
||||
featured: false
|
||||
popular: false
|
||||
hidden: false
|
||||
tags: []
|
||||
order: 05
|
||||
---
|
||||
|
||||
MSPs, Resellers, and other Bitwarden Partners that are already administering Organizations on behalf of their clients can add pre-existing Organizations to their Provider Portal.
|
||||
|
||||
When Bitwarden detects that a [Provider Admin's]({{site.baseurl}}/article/provider-users/#provider-user-types) account is the **Owner of a non-Provider Organization**, the Provider Portal will display an {% icon fa-plus %} **Add Existing Organization** button:
|
||||
|
||||
{% image /providers/add-existing-client-1.png %}
|
||||
|
||||
Selecting the {% icon fa-plus %} **Add Existing Organization** button prompts you to select the Organization to add to the Provider:
|
||||
|
||||
{% image /providers/add-existing-client-2.png %}
|
||||
|
||||
Once added, the Organization will appear in the {% icon fa-bank %} **Clients** list alongside all other Client Organizations.
|
||||
|
||||
{% callout success %}
|
||||
**Once you've added the existing Organization to the Provider**, you (the Provider Admin and Organization Owner) can be removed from the Organization. Doing so will free up the User Seat previously taken up by your account. As a member of the Provider, you will retain all permission over the Client Organization:
|
||||
|
||||
1. Organizations may not be Owner-less, so [add a backup Owner to the Organization]({{site.baseurl}}/article/managing-users/#invite).
|
||||
2. Once the new Owner is Invited, Accepted, and Confirmed, ask them to [remove you from the Organization]({{site.baseurl}}/article/managing-users/#offboard-users).
|
||||
{% endcallout %}
|
||||
67
_articles/providers/client-org-setup.md
Normal file
67
_articles/providers/client-org-setup.md
Normal file
@@ -0,0 +1,67 @@
|
||||
---
|
||||
layout: article
|
||||
title: Start a Client Organization
|
||||
categories: [providers]
|
||||
featured: false
|
||||
popular: false
|
||||
hidden: false
|
||||
tags: []
|
||||
order: 04
|
||||
---
|
||||
|
||||
This article will walk you through the [creation of a Client Organization](#create-a-client-organization) and outline a typical [setup procedure](#initial-setup-procedure) for getting started administering a customer's Organization.
|
||||
|
||||
## Create a Client Organization
|
||||
|
||||
{% callout success %}
|
||||
**Already have an Organization setup for your customer?** You can [add an existing Organization to the Provider Portal]({{site.baseurl}}/article/providers-faqs/#q-can-i-add-an-existing-organizations-to-my-provider).
|
||||
{% endcallout %}
|
||||
|
||||
To create a Client Organization you must be a [Provider Admin]({{site.baseurl}}/article/provider-users/#provider-user-types):
|
||||
|
||||
1. Navigate to the Provider Portal and select the {% icon fa-plus %} **New Client Organization** button:
|
||||
|
||||
{% image providers/provider-add-client.png Create a Client Organization %}
|
||||
2. On the New Client Organization screen, enter an **Organization Name**, **Billing Email**, and **Client Owner Email**.
|
||||
|
||||
{% callout info %}An invitation will automatically be sent to the **Client Owner Email** to join the Organization as an [Owner]({{site.baseurl}}/article/user-types-access-control).{% endcallout %}
|
||||
3. From the **Choose Your Plan** list, select the [type of Organization]({{site.baseurl}}/article/about-bitwarden-plans/#compare-the-plans-1) to create.
|
||||
|
||||
{% callout success %}Teams and Enterprise Organizations include premium features for all enrolled users.{% endcallout %}
|
||||
4. Set the following options for the Organization:
|
||||
|
||||
- **User Seats**: Specify the number of User Seats you need for the Client Organization. You can always add more seats later.
|
||||
- **Additional Storage (GB)**: Organizations come with 1GB of encrypted [storage for attachments]({{site.baseurl}}/article/attachments/). Add additional storage for $0.33 per GB per month.
|
||||
- **Billing Cadence**: Choose whether you'd like to be billed for this Organization Annually or Monthly.
|
||||
|
||||
5. Once you're happy with the Organization, enter your **Payment Information** and select **Submit**.
|
||||
5. Select **Submit** to finishing creating the Organization.
|
||||
|
||||
Once created, navigating to the Client Organization from the Provider Portal will bring you to the Organization Vault, from which you can fully complete [initial setup](#initial-setup-procedure) and engage in [ongoing administration]({{site.baseurl}}/article/manage-client-orgs/):
|
||||
|
||||
{% image providers/client-org-manage.png Client Organization Vault %}
|
||||
|
||||
## Initial Setup Procedure
|
||||
|
||||
With your newly-created Client Organization, you're ready to start building the perfect solution for your customer. Exact setup will be different for each Client Organization depending on your customers' needs, but typically will involve the following steps:
|
||||
|
||||
1. **Create Collections**. A good first step is to [create a set of Collections]({{site.baseurl}}/article/about-collections/#create-a-collection), which provide an organizing structure for the Vault items you'll add to the Vault in the next step.
|
||||
|
||||
Common Collections patterns include **Collections by Department** (i.e. users in 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 %}
|
||||
2. **Populate the Organization Vault**. Once the structure of how you'll store Vault items is in place, you can begin populating the Organization with your client's Logins, Notes, Cards, and Identities.
|
||||
|
||||
{% callout success %}You can [create shared items from scratch]({{site.baseurl}}/article/sharing/#create-a-shared-item), but we recommend [importing a file that contains all their Vault items]({{site.baseurl}}/article/import-to-org/).{% endcallout %}
|
||||
3. **Configure Enterprise Policies**. Before beginning the user management portion of setup, [configure Enterprise Policies]({{site.baseurl}}/article/policies/) in order to set rules-of-use for things like [Master Password complexity]({{site.baseurl}}/article/policies/#master-password), [use of Two-step Login]({{site.baseurl}}/article/policies/#two-step-login), and [Admin Password Reset]({{site.baseurl}}/article/admin-reset/).
|
||||
|
||||
{% callout info %}Enterprise Policies are **only available to Enterprise Organizations**.{% endcallout %}
|
||||
4. **Setup Login with SSO**. If your customer uses Single Sign-On (SSO) to authenticate with other applications, [connect Bitwarden with their IdP]({{site.baseurl}}/article/about-sso/) to allow authentication with Bitwarden using end-users' SSO credentials.
|
||||
5. **Create User Groups**. For Teams and Enterprise Organizations, [create a set of Groups]({{site.baseurl}}/article/about-groups/#create-a-group) for scalable permissions assignment. When you start adding users, add them to Groups to have each user automatically inherit the Group's configured permissions (e.g. access to which Collections).
|
||||
|
||||
One common Group-Collection pattern is to create **Groups by Department** and **Collections by Function**, for example:
|
||||
|
||||
{% image organizations/collections-graphic-2.png %}
|
||||
6. **Start Inviting Users**. Now that the infrastructure for securely and scalably sharing credentials is in place for your client, you can begin [inviting users to the Organization]({{site.baseurl}}/article/managing-users/#onboard-users). To ensure the security of the Organization, Bitwarden applies a 3-step process for onboarding new users, Invite → Accept → Confirm.
|
||||
|
||||
{% callout success %}**If your customer uses directory service** (Active Directory, an LDAP, Okta, etc.), use [Directory Connector]({{site.baseurl}}/article/directory-sync/) to automatically sync Organization users from the source directory and automatically issue invitations.{% endcallout %}
|
||||
106
_articles/providers/getting-started-providers.md
Normal file
106
_articles/providers/getting-started-providers.md
Normal file
@@ -0,0 +1,106 @@
|
||||
---
|
||||
layout: article
|
||||
title: Get Started with Provider Portal
|
||||
categories: [providers]
|
||||
featured: false
|
||||
popular: false
|
||||
hidden: false
|
||||
tags: []
|
||||
order: 02
|
||||
redirect_from:
|
||||
- /article/deploying-bitwarden-as-a-msp/
|
||||
---
|
||||
|
||||
{% callout success %}
|
||||
Interested in becoming a Provider? Contact us to get started for free:
|
||||
|
||||
<a role="button" class="btn btn-primary" href="https://bitwarden.com/contact" target="blank">Contact Us</a>
|
||||
{% endcallout %}
|
||||
|
||||
## Why Bitwarden Providers?
|
||||
|
||||
Managed Service Providers (MSPs), Resellers, and other businesses often need a way to quickly create and easily administer Bitwarden Organizations on behalf of business customers. **Providers** are administration entities that allow those businesses to create and manage [Client Organizations](#client-organization) through the **Provider Portal**.
|
||||
|
||||
The Provider Portal is an all-in-one management experience that enables Providers to manage customers’ Bitwarden Organizations at scale. The Provider Portal streamlines administration tasks by centralizing a dedicated space to access and support each client, or to create a new one:
|
||||
|
||||
{% image providers/provider.png Provider Portal %}
|
||||
|
||||
### Start a Provider
|
||||
|
||||
[Contact Us](https://bitwarden.com/contact){:target="\_blank"} to sign up for the Provider Program. After you register, a member of the Bitwarden team will contact you and issue an invitation to start a Provider:
|
||||
|
||||
{% image providers/provider-invitation.png Provider Invitation %}
|
||||
|
||||
Selecting the **Setup Provider Now** button will prompt you to log in to Bitwarden and fill out some Provider details:
|
||||
|
||||
{% image providers/provider-enrollment.png Provider Setup %}
|
||||
|
||||
### Onboard Users
|
||||
|
||||
As the creator of the Provider, you'll be automatically given [Provider Admin]({{site.baseurl}}/provider-users/#provider-user-types) status, allowing you to fully manage all aspects of the Provider and all [Client Organizations](#client-organizations). Bitwarden strongly recommends that you provision a second Provider Admin for failover purposes.
|
||||
|
||||
Now, begin adding your employees as [Service Users]({{site.baseurl}}/article/provider-users/#provider-user-types), which will allow them to fully administer all Client Organizations and create new ones or manage the Provider itself:
|
||||
|
||||
1. **Invite Users**. From the Provider Portal {% icon fa-sliders %} **Manage** tab, invite users as Service Users (or invite additional Provider Admins):
|
||||
|
||||
{% image providers/provider-adduser.png %}
|
||||
2. **Instruct Users to Accept Invites**. Invited users will receive an email from Bitwarden inviting them to join the Provider. Inform users that they should expect an invitation and that they will need to **Log In** with an existing Bitwarden account or **Create Account** to proceed:
|
||||
|
||||
{% image providers/provider-accept-invite.png %}
|
||||
3. **Confirm Accepted Invitations**. To complete the secure onboarding of your Provider users, confirm accepted invitations from the Provider Portal {% icon fa-sliders %} **Manage** tab:
|
||||
|
||||
{% image providers/provider-confirm.png %}
|
||||
|
||||
With an assembled team of Service Users, you're ready to start setting up [Client Organizations](#client-organizations).
|
||||
|
||||
## Client Organizations
|
||||
|
||||
Client Organizations are any [Organization]({{site.baseurl}}/article/about-organizations/) that is attached to or administered by a Provider. To your customers, there's no difference between a "Client" Organization and a "regular" Organization except for who is conducting administration.
|
||||
|
||||
Organizations relate Bitwarden users and Vault items together for [secure sharing]({{site.baseurl}}/article/sharing/) of Logins, Cards, Notes, and Identities. Organizations have a unique Vault, where Provider Service Users can manage the Organization's items, users, and settings:
|
||||
|
||||
{% image providers/client-org.png %}
|
||||
|
||||
Members of a Client Organization (i.e. your customer's end-users) will find shared items ({% icon fa-cube %}) 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/personal-vault-org-enabled.png End-user Vault %}
|
||||
|
||||
### Create a Client Organization
|
||||
|
||||
To create a new Client Organization, you must be a [Provider Admin]({{site.baseurl}}/article/provider-users/#provider-user-types). Navigate to the {% icon fa-bank %} **Clients** tab of the Provider Portal and select the {% icon fa-plus %} **New Client Organization** button:
|
||||
|
||||
{% image providers/provider-add-client.png Create a Client Organization %}
|
||||
|
||||
### Setup the Client Organization
|
||||
|
||||
With your newly-created Client Organization, start building the perfect solution for your customer. Exact setup will be different for each Client Organization based on your customers' needs, but will typically involve:
|
||||
|
||||
1. **Create Collections**. A good first step is to [create a set of Collections]({{site.baseurl}}/article/about-collections/#create-a-collection), which provide an organizing structure for the Vault items you'll add to the Vault in the next step.
|
||||
|
||||
Common Collections patterns include **Collections by Department** (i.e. users in 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 %}
|
||||
2. **Populate the Organization Vault**. Once the structure of how you'll store Vault items is in place, you can begin populating the Organization with your client's Logins, Notes, Cards, and Identities.
|
||||
|
||||
{% callout success %}You can [create shared items from scratch]({{site.baseurl}}/article/sharing/#create-a-shared-item), but we recommend [importing a file that contains all their Vault items]({{site.baseurl}}/article/import-to-org/).{% endcallout %}
|
||||
3. **Configure Enterprise Policies**. Before beginning the user management portion of setup, [configure Enterprise Policies]({{site.baseurl}}/article/policies/) in order to set rules-of-use for things like [Master Password complexity]({{site.baseurl}}/article/policies/#master-password), [use of Two-step Login]({{site.baseurl}}/article/policies/#two-step-login), and [Admin Password Reset]({{site.baseurl}}/article/admin-reset/).
|
||||
|
||||
{% callout info %}Enterprise Policies are **only available to Enterprise Organizations**.{% endcallout %}
|
||||
4. **Setup Login with SSO**. If your customer uses Single Sign-On (SSO) to authenticate with other applications, [connect Bitwarden with their IdP]({{site.baseurl}}/article/about-sso/) to allow authentication with Bitwarden using end-users' SSO credentials.
|
||||
5. **Create User Groups**. For Teams and Enterprise Organizations, [create a set of Groups]({{site.baseurl}}/article/about-groups/#create-a-group) for scalable permissions assignment. When you start adding users, add them to Groups to have each user automatically inherit the Group's configured permissions (e.g. access to which Collections).
|
||||
|
||||
One common Group-Collection pattern is to create **Groups by Department** and **Collections by Function**, for example:
|
||||
|
||||
{% image organizations/collections-graphic-2.png %}
|
||||
|
||||
### Invite Client Users
|
||||
|
||||
With the infrastructure for securely and scalably sharing credentials in place, you can begin inviting users to the Organization. Onboarding users to Bitwarden can be accomplished in two ways, depending on the size of your customer:
|
||||
|
||||
1. **For smaller customers**, you can send email invitations to users from the Organization Vault's {% icon fa-sliders %} **Manage** tab:
|
||||
|
||||
{% image organizations/org-people-invite.png %}
|
||||
|
||||
2. **For larger customers** who leverage a directory service (Active Directory, LDAP, Okta, etc.), use [Directory Connector]({{site.baseurl}}/article/directory-sync) to sync Organization users from the source directory and automatically issue invitations.
|
||||
|
||||
Regardless of whether you've invited users from the Organization Vault or using Directory Connector, the same 3-step process (Invite → Accept → Confirm) that you followed when [onboarding Provider users](#onboard-users) will apply here as well.
|
||||
38
_articles/providers/manage-client-orgs.md
Normal file
38
_articles/providers/manage-client-orgs.md
Normal file
@@ -0,0 +1,38 @@
|
||||
---
|
||||
layout: article
|
||||
title: Ongoing Administration
|
||||
categories: [providers]
|
||||
featured: false
|
||||
popular: false
|
||||
hidden: false
|
||||
tags: []
|
||||
order: 06
|
||||
---
|
||||
|
||||
To access a [Client Organization]({{site.baseurl}}/article/providers/#client-organizations) as a [Service User]({{site.baseurl}}/article/provider-users/#provider-user-types), select **Provider** from the top navigation and select your Provider from the Providers list. In the Provider Portal, select the Client Organization to administer from the {% icon fa-bank %} **Clients** tab:
|
||||
|
||||
{% image providers/provider-as-serviceuser.png Provider Portal %}
|
||||
|
||||
Once in the Organization Vault you can fully administer the Client Organization, including the following important tasks:
|
||||
|
||||
|Task|Description|Resources|
|
||||
|----|-----------|---------|
|
||||
|Add and Remove Users|Onboard and offboard users from Bitwarden as they join and leave the customers' Organization.|[User Onboarding]({{site.baseurl}}/article/managing-users/#onboard)<br><br>[User Offboarding]({{site.baseurl}}/article/managing-users/#offboard)|
|
||||
|Change User Permissions|When end-users change roles, change their permissions as appropriate.|[User Types and Access Control]({{site.baseurl}}/article/user-types-access-control/)|
|
||||
|Add and Remove User Seats|As the customers' business grows, manage the number of user seats for the Client Organization.|[Manage User Seats]({{site.baseurl}}/article/managing-users/#manage-user-seats)|
|
||||
|Reset Users' Master Passwords|If enabled, use Admin Password Reset to recover end-user accounts if they forget their Master Password.|[Admin Password Reset]({{site.baseurl}}/article/admin-reset)|
|
||||
|Create & Share Vault Items|Add and share new Vault items on-the-fly when users need access to new systems.|[Sharing]({{site.baseurl}}/article/sharing/)|
|
||||
|Secure one-time Sharing|Use Bitwarden for secure one-time sharing of credentials, documents, and more.|[Create a Send]({{site.baseurl}}/article/create-send)|
|
||||
|Monitor Vault Health|Use Organization Vault Health Reports and Event Logs to keep an eye on the overall health of the Client Organization.|[Vault Health Reports]({{site.baseurl}}/article/reports/)<br><br>[Event Logs]({{site.baseurl}}/article/events/)|
|
||||
|Manage Billing|Make changes to the billing information for the Client Organization, if you ever need to.|[Update Billing Info]({{site.baseurl}}/article/update-billing-info/#update-billing-information-for-organizations)|
|
||||
|
||||
Additionally, **if your Service Users help to train customers' end-users to use Bitwarden**, the following resources may be helpful:
|
||||
|
||||
|Task|Description|Resources|
|
||||
|----|-----------|---------|
|
||||
|User Registration|Help end-users register for Bitwarden accounts.|[Register](https://vault.bitwarden.com/#/register)|
|
||||
|Watch Training Videos|Pass along some of the trainings we've conducted in the past.|[Getting Started with Bitwarden](https://bitwarden.com/getting-started)|
|
||||
|Help users import their data|If permitted by your customer, give users instructions for importing their personal data to Bitwarden.|[Import Data to your Vault]({{site.baseurl}}/article/import-data/)|
|
||||
|Help setup Two-step Login|Give users instructions to help facilitate setup of Two-step Login.|[Two-step Login Methods]({{site.baseurl}}/article/setup-two-step-login/)|
|
||||
|Demonstrate Bitwarden apps|Help users understand the benefits of Bitwarden mobile apps, browser extensions, and other apps.|[Getting Started Guides]({{site.baseurl}}/getting-started/)|
|
||||
|Register for Demos|Encourage Power Users to learn independently by attending a Weekly Demo.|[Bitwarden Events](https://www.crowdcast.io/bitwarden)|
|
||||
37
_articles/providers/provider-events.md
Normal file
37
_articles/providers/provider-events.md
Normal file
@@ -0,0 +1,37 @@
|
||||
---
|
||||
layout: article
|
||||
title: Provider Event Logs
|
||||
categories: [providers]
|
||||
featured: false
|
||||
popular: false
|
||||
hidden: false
|
||||
tags: []
|
||||
order: 07
|
||||
---
|
||||
|
||||
## What are Event Logs?
|
||||
|
||||
Event logs are timestamped records of events that occur within your Provider. Event logs for the Provider are accessible only to [Provider Admins]({{site.baseurl}}/article/provider-users/) from the {% icon fa-sliders %} **Manage** tab of the Provider Portal:
|
||||
|
||||
{% image providers/provider-events.png Provider Event Logs %}
|
||||
|
||||
Selecting the **Export** button will create a `.csv` of all events within the specified date range:
|
||||
|
||||
{% image providers/provider-events-export.png Export Event Logs %}
|
||||
|
||||
### Events
|
||||
|
||||
Event Logs record several different types of events for Providers. The Event Logs screen captures a **Timestamp** for the event, client app information including the application type and IP (accessed by hovering over the {% icon fa-globe %} globe icon), the **User** connected to the event, and an **Event** description. Provider Events include:
|
||||
|
||||
- Invited user *user-identifier*
|
||||
- Confirmed user *user-identifier*
|
||||
- Edited user *user-identifier*
|
||||
- Removed user *user-identifier*
|
||||
- Accessed *organization-identifier* organization vault.
|
||||
- Created organization *organization-identifier* (triggered when [a new Organization is created within Provider]({{site.baseurl}}/article/client-org-setup/#create-a-client-organization))
|
||||
- Added organization *organization-identifier* (triggered when [an existing Organization is added to Provider]({{site.baseurl}}/article/providers-faqs/#q-can-i-add-an-existing-organizations-to-my-provider))
|
||||
- Removed organization *organization-identifier*
|
||||
|
||||
{% callout success %}
|
||||
Provider Events do not currently roll up the events logged for each [Client Organization]({{site.baseurl}}/article/providers/#client-organizations). Provider users can access Organization Event Logs from the Client Organization's Vault. [Learn more]({{site.baseurl}}/article/event-logs/).
|
||||
{% endcallout %}
|
||||
79
_articles/providers/provider-users.md
Normal file
79
_articles/providers/provider-users.md
Normal file
@@ -0,0 +1,79 @@
|
||||
---
|
||||
layout: article
|
||||
title: Provider Users
|
||||
categories: [providers]
|
||||
featured: false
|
||||
popular: false
|
||||
hidden: false
|
||||
tags: []
|
||||
order: 03
|
||||
---
|
||||
|
||||
## Onboard Provider Users
|
||||
|
||||
To ensure the secure administration of your Client Organizations, Bitwarden applies a 3-step process for onboarding a new Provider member, [Invite](#invite) → [Accept](#accept) → [Confirm](#confirm).
|
||||
|
||||
### Invite
|
||||
|
||||
To invite users to your Provider:
|
||||
|
||||
1. Log in to the [Web Vault](https://vault.bitwarden.com){:target="\_blank"} and open your Provider.
|
||||
2. Open the {% icon fa-sliders %} **Manage** tab and select **People** from the left-hand menu.
|
||||
3. Select the {% icon fa-plus %} **Invite User** button:
|
||||
|
||||
{% image /providers/provider-adduser.png Invite Provider Users %}
|
||||
4. On the Invite User panel:
|
||||
|
||||
- Enter the **Email** address where new users should receive their invites. You can add up to 20 users at a time by comma-separating email addresses.
|
||||
- Select the **User Type** to be applied to this batch of users. [User Type](#provider-user-types) will determine what access these users will have to the Provider. **Both User Types** will be able to fully administer any [Client Organization]({{site.baseurl}}/article/client-orgs/).
|
||||
5. Click **Save** to invite the designated users to join the Provider.
|
||||
|
||||
{% 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 /providers/provider-resend-invite.png Resend Invitations %}
|
||||
{% endcallout %}
|
||||
|
||||
### Accept
|
||||
|
||||
Invited users will receive an email from Bitwaden inviting them to join the Provider. Clicking the link in the email will open a Bitwarden invitations window. **Log In** with an existing Bitwarden account or **Create Account** to accept the invitation:
|
||||
|
||||
{% image /providers/provider-accept-invite.png Email Invitation %}
|
||||
|
||||
### Confirm
|
||||
|
||||
To confirm accepted invitations to your Provider:
|
||||
|
||||
1. Log in to the [Web Vault](https://vault.bitwarden.com){:target="\_blank"} and open your Provider.
|
||||
2. Open the {% icon fa-sliders %} **Manage** tab and select **People** from the left-hand menu.
|
||||
3. Select any `Accepted` users and use the {% icon fa-cog %} gear dropdown to {% icon fa-check %} **Confirm Selected**:
|
||||
|
||||
{% image /providers/provider-confirm.png Confirm Provider Users %}
|
||||
4. On the panel that appears, verify that the [fingerprint phrases]({{site.baseurl}}/article/fingerprint-phrase) for new users match those they can find in their **Settings** → **My Account** screen.
|
||||
|
||||
Each fingerprint phrase is unique to its account, and ensures a final layer of oversight in securely adding users. If they match, select **Confirm**.
|
||||
|
||||
## Offboard Users
|
||||
|
||||
To remove users from your Provider:
|
||||
|
||||
1. Log in to the [Web Vault](https://vault.bitwarden.com){:target="\_blank"} and open your Provider.
|
||||
2. Open the {% icon fa-sliders %} **Manage** tab and select **People** from the left-hand menu.
|
||||
3. Select the users you want to remove from the Provider and use the {% icon fa-cog %} gear dropdown to {% icon fa-times %} **Remove**:
|
||||
|
||||
{% image /providers/provider-removeuser.png Remove Provider Users %}
|
||||
|
||||
## Provider User Types
|
||||
|
||||
{% callout success %}
|
||||
**Managing a Client Organization's users?** Organizations have a set of [User Types and Access Controls]({{site.baseurl}}/article/user-types-access-control/) that are distinct from Provider User Types.
|
||||
{% endcallout %}
|
||||
|
||||
Bitwarden Provider Users can be granted one of two User Types to manage their access to the Provider. **Both User Types will be able to fully administer any Client Organization.** Bitwarden strongly recommends that you provision a second user with a Provider Admin role for failover purposes.
|
||||
|
||||
You can set User Types when you [invite](#invite) Provider users, or at any time from the **Manage** → **People** screen in your Provider Portal. User Types include:
|
||||
|
||||
|Role|Description|
|
||||
|----|-----------|
|
||||
|Service User|Service Users can access and manage all [Client Organizations]({{site.baseurl}}/article/client-orgs/), including:<br><br>- Access shared items stored in the Organization Vault<br>- Add, edit, or remove items from all Collections<br>- Create or delete Collections<br>- Assign Users and User Groups to Collections<br>- Assign Users to User Groups<br>- Create or delete User Groups<br>- Invite and confirm new users<br>- Manage Enterprise Policies<br>- View Event Logs<br>- Export Organization Vault data<br>- Manage Password Reset<br>- Manage Billing, Subscription, and Integrations|
|
||||
|Provider Admin|Provider Admins manage all aspects of the Provider and all Client Organizations. Provider admins can do all of the above, plus:<br><br>- Create new Client Organizations<br>- Add existing Organizations to the Provider<br>- Invite and confirm new Service Users and Provider Admins<br>- View Provider Event Logs<br>- Edit Provider Settings|
|
||||
53
_articles/providers/providers.md
Normal file
53
_articles/providers/providers.md
Normal file
@@ -0,0 +1,53 @@
|
||||
---
|
||||
layout: article
|
||||
title: Provider Portal Overview
|
||||
categories: [providers]
|
||||
featured: false
|
||||
popular: false
|
||||
hidden: false
|
||||
tags: []
|
||||
order: 01
|
||||
---
|
||||
|
||||
{% callout success %}
|
||||
Interested in becoming a Provider? Contact us to get started for free:
|
||||
|
||||
<a role="button" class="btn btn-primary" href="https://bitwarden.com/contact" target="blank">Contact Us</a>
|
||||
{% endcallout %}
|
||||
|
||||
## What are Providers?
|
||||
|
||||
Providers are administration entities in Bitwarden that allow Managed Service Providers (MSPs), Resellers, and other businesses to create and fully manage multiple [Client Organizations](#client-organizations) on behalf of individual business customers. Client Organization management is easily accessible through the **Provider Portal**:
|
||||
|
||||
### What is the Provider Portal
|
||||
|
||||
The Provider Portal is an all-in-one management experience that enables Providers to manage customers' Bitwarden Organizations at scale. The Provider Portal streamlines administration tasks by centralizing a dedicated space to access and support each client, or to create a new one:
|
||||
|
||||
{% image providers/provider.png Provider Portal %}
|
||||
|
||||
Providers are built with two distinct [user types]({{site.baseurl}}/provider-users/#user-types):
|
||||
|
||||
- **Service Users** can fully administer [Client Organizations](#client-organizations).
|
||||
- **Provider Admins** can administer [Client Organizations](#client-organizations) and administer the Provider itself, including adding new Service Users to the team.
|
||||
|
||||
## Client Organizations
|
||||
|
||||
Client Organizations are any [Organization]({{site.baseurl}}/article/about-organizations/) that is attached to or administered by a [Provider](#what-are-providers). To your customers, there's no difference between a "Client" Organization and a "regular" Organization except for who is conducting administration. All Provider members have **full** access to all Client Organizations:
|
||||
|
||||
{% image providers/provider-diagram.png Structure of a Provider %}
|
||||
|
||||
{% callout info %}
|
||||
**As denoted in the above diagram**, if Providers want to use an [Organization]({{site.baseurl}}/article/about-organizations) to manage their own credentials, they **should not** include it as a Client Organization that's administered by the Provider.
|
||||
|
||||
Creating an independent Organization for this case will ensure users can be given the appropriate [user types and access controls]({{site.baseurl}}/article/user-types-access-control) over credentials.
|
||||
{% endcallout %}
|
||||
|
||||
Organizations relate Bitwarden users and Vault items together for [secure sharing]({{site.baseurl}}/article/sharing/) of Logins, Cards, Notes, and Identities. Organizations have a unique Vault, where Provider Service Users can manage the Organization's items, users, and settings:
|
||||
|
||||
{% image /providers/client-org.png Client Organization Vault %}
|
||||
|
||||
Members of a Client Organization (i.e. your customer's end-users) will find shared items ({% icon fa-cube %}) 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/personal-vault-org-enabled.png End-user Vault %}
|
||||
|
||||
Once you've filled out the [Provider Registration form](#) and been setup with a Provider by a member of the Bitwarden team, [start a Client Organization]({{site.baseurl}}/article/client-org-setup).
|
||||
5
_categories/providers.md
Normal file
5
_categories/providers.md
Normal file
@@ -0,0 +1,5 @@
|
||||
---
|
||||
layout: category
|
||||
title: Provider Portal
|
||||
featured: true
|
||||
---
|
||||
@@ -34,6 +34,7 @@ collections:
|
||||
- two-step-login.md
|
||||
- hosting.md
|
||||
- organizations.md
|
||||
- providers.md
|
||||
- directory-connector.md
|
||||
- login-with-sso.md
|
||||
- security.md
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
<h4 class="card-header"><i class="fa fa-diamond"></i> What's Popular</h4>
|
||||
<div class="card-body">
|
||||
<p class="card-text"><i class="fa fa-file-o"></i> <a href="{{site.baseurl}}/article/import-from-lastpass">Import Data from Lastpass</a></p>
|
||||
<p class="card-text"><i class="fa fa-file-o"></i> <a href="{{site.baseurl}}/article/create-send">Create a Send</a></p>
|
||||
<p class="card-text"><i class="fa fa-file-o"></i> <a href="{{site.baseurl}}/article/admin-reset">Admin Password Reset</a></p>
|
||||
<p class="card-text"><i class="fa fa-file-o"></i> <a href="{{site.baseurl}}/article/setup-two-step-login">Two-step Login Methods</a></p>
|
||||
<p class="card-text"><i class="fa fa-file-o"></i> <a href="{{site.baseurl}}/article/forgot-master-password">I Forgot my Master Password</a></p>
|
||||
</div>
|
||||
|
||||
BIN
images/cli/cli-captcha-1-markup.png
Normal file
BIN
images/cli/cli-captcha-1-markup.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 295 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 27 KiB After Width: | Height: | Size: 21 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 34 KiB After Width: | Height: | Size: 29 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 221 KiB After Width: | Height: | Size: 83 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 13 KiB After Width: | Height: | Size: 14 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 45 KiB After Width: | Height: | Size: 36 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 94 KiB After Width: | Height: | Size: 51 KiB |
BIN
images/organizations/pwreset-temporary.png
Normal file
BIN
images/organizations/pwreset-temporary.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 131 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 57 KiB After Width: | Height: | Size: 45 KiB |
BIN
images/providers/add-existing-client-1.png
Normal file
BIN
images/providers/add-existing-client-1.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 40 KiB |
BIN
images/providers/add-existing-client-2.png
Normal file
BIN
images/providers/add-existing-client-2.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 43 KiB |
BIN
images/providers/client-org-manage.png
Normal file
BIN
images/providers/client-org-manage.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 33 KiB |
BIN
images/providers/client-org.png
Normal file
BIN
images/providers/client-org.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 33 KiB |
BIN
images/providers/provider-accept-invite.png
Normal file
BIN
images/providers/provider-accept-invite.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 23 KiB |
BIN
images/providers/provider-add-client.png
Normal file
BIN
images/providers/provider-add-client.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 36 KiB |
BIN
images/providers/provider-adduser.png
Normal file
BIN
images/providers/provider-adduser.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 38 KiB |
BIN
images/providers/provider-as-serviceuser.png
Normal file
BIN
images/providers/provider-as-serviceuser.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 35 KiB |
BIN
images/providers/provider-confirm.png
Normal file
BIN
images/providers/provider-confirm.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 57 KiB |
BIN
images/providers/provider-diagram.png
Normal file
BIN
images/providers/provider-diagram.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 72 KiB |
BIN
images/providers/provider-enrollment.png
Normal file
BIN
images/providers/provider-enrollment.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 29 KiB |
BIN
images/providers/provider-events-export.png
Normal file
BIN
images/providers/provider-events-export.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 37 KiB |
BIN
images/providers/provider-events.png
Normal file
BIN
images/providers/provider-events.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 59 KiB |
BIN
images/providers/provider-invitation.png
Normal file
BIN
images/providers/provider-invitation.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 32 KiB |
BIN
images/providers/provider-removeuser.png
Normal file
BIN
images/providers/provider-removeuser.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 50 KiB |
BIN
images/providers/provider-resend-invite.png
Normal file
BIN
images/providers/provider-resend-invite.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 44 KiB |
BIN
images/providers/provider.png
Normal file
BIN
images/providers/provider.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 39 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 30 KiB After Width: | Height: | Size: 35 KiB |
10
index.html
10
index.html
@@ -52,8 +52,12 @@ title: Help Center
|
||||
<div class="icon-wrapper text-center align-items-center justify-content-around">
|
||||
<a class="icon-link" href="{{site.baseurl}}/article/getting-started-organizations">
|
||||
<img src="images/landing/organizations.png">
|
||||
<p class="font-weight-bold">Get Started with Organizations</p>
|
||||
<p class="font-weight-bold">Bitwarden Organizations</p>
|
||||
</a>
|
||||
<a class="icon-link" href="{{site.baseurl}}/article/getting-started-providers">
|
||||
<img src="images/landing/msp.png">
|
||||
<p class="font-weight-bold">Bitwarden Providers</p>
|
||||
</a>
|
||||
<a class="icon-link" href="{{site.baseurl}}/article/proof-of-concept">
|
||||
<img src="images/landing/poc-guide.png">
|
||||
<p class="font-weight-bold">Proof-of-Concept Checklist</p>
|
||||
@@ -66,10 +70,6 @@ title: Help Center
|
||||
<img src="images/landing/security.png">
|
||||
<p class="font-weight-bold">Security & Compliance</p>
|
||||
</a>
|
||||
<a class="icon-link" href="{{site.baseurl}}/article/deploying-bitwarden-as-a-msp">
|
||||
<img src="images/landing/msp.png">
|
||||
<p class="font-weight-bold">Bitwarden for MSPs</p>
|
||||
</a>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
Reference in New Issue
Block a user