mirror of
https://github.com/bitwarden/help
synced 2026-01-10 04:23:24 +00:00
Promote to Master (#748)
* initial commit
* adding quotes for the array error
* Create Gemfile
* Create Gemfile.lock
* add .nvmrc and .node-version
* removed /article from URL
* update links to work with netlify
* more fixed links
* link fixes
* update bad links
* Update netlify.toml
toml test for redirects
* article redirect
* link fixes
* Update index.html
* Update netlify.toml
* Update _config.yml
* Update netlify.toml
* Update netlify.toml
* Update netlify.toml
* Update netlify.toml
* Update netlify.toml
* add article back into URL for launch
* Update netlify.toml
* Update netlify.toml
* add order to categories front matter
* Update netlify.toml
* update
* sidemenu update
* Revert "sidemenu update"
This reverts commit 5441c3d35c.
* update order prop
* Navbar updates per Gary and compiler warnings
* font/style tweaks
* Update sidebar.html
* Stage Release Documentation (#739)
* initial drafts
* rewrite Custom Fields article to prioritize new context-menu option & better organize ancillary information
* edit
* edit
* Custom Field Context Menu & CAPTCHA item in release notes
* SSO relink event
* update rn
* small edits
* improve release notes titles
* fix side menu
* Edits courtest of mportune!
* update order
* link fixes
* link cleanup
* image updates and a link
* fix trailing slash
Co-authored-by: DanHillesheim <79476558+DanHillesheim@users.noreply.github.com>
This commit is contained in:
fred_the_tech_writer
committed by
GitHub
GitHub
parent
63f78e8979
commit
906e2ca0dd
@@ -5,7 +5,7 @@ categories: [organizations]
|
||||
featured: false
|
||||
popular: false
|
||||
tags: [organizations, business portal, sso, policies]
|
||||
order: 12
|
||||
order: "12"
|
||||
---
|
||||
## What is the Business Portal?
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@ categories: [organizations]
|
||||
featured: true
|
||||
popular: false
|
||||
tags: [collections, access control, best practices]
|
||||
order: 02
|
||||
order: "02"
|
||||
redirect_from:
|
||||
- /article/collections/
|
||||
- /article/create-collections/
|
||||
@@ -32,7 +32,7 @@ Other common methodologies include **Collections by Vendor or System** (i.e. use
|
||||
|
||||
## 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:
|
||||
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:
|
||||
|
||||
@@ -5,7 +5,7 @@ categories: [organizations]
|
||||
featured: true
|
||||
popular: false
|
||||
tags: [groups, access control]
|
||||
order: 03
|
||||
order: "03"
|
||||
redirect_from:
|
||||
- /article/groups/
|
||||
- /article/create-groups/
|
||||
@@ -29,7 +29,7 @@ Other common methodologies include **Collections by Vendor or System** (i.e. use
|
||||
|
||||
## 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:
|
||||
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.
|
||||
|
||||
@@ -5,7 +5,7 @@ categories: [organizations]
|
||||
featured: true
|
||||
popular: true
|
||||
tags: [organizations]
|
||||
order: 01
|
||||
order: "01"
|
||||
redirect_from:
|
||||
- /article/what-is-an-organization/
|
||||
- /article/create-an-organization/
|
||||
@@ -23,7 +23,7 @@ Members of an Organization will find shared items ({% icon fa-cube%}) in their *
|
||||
|
||||
### Types of Organizations
|
||||
|
||||
Bitwarden offers a variety of types of Organizations to meet your business's or family's needs. For feature-by-feature breakdowns of each Organization type, see [About Bitwarden Plans](https://bitwarden.com/help/article/about-bitwarden-plans/).
|
||||
Bitwarden offers a variety of types of Organizations to meet your business's or family's needs. For feature-by-feature breakdowns of each Organization type, see [About Bitwarden Plans]({{site.baseurl}}/article/about-bitwarden-plans/).
|
||||
|
||||
|Type|Description|
|
||||
|----|-----------|
|
||||
@@ -40,7 +40,7 @@ Paid Organizations (Families, Teams, or Enterprise) automatically include those
|
||||
|
||||
### 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.
|
||||
[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
|
||||
|
||||
@@ -64,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/sharing).
|
||||
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/).
|
||||
|
||||
@@ -5,11 +5,11 @@ categories: [organizations]
|
||||
featured: true
|
||||
popular: false
|
||||
tags: [master password, reset, administrator, owner]
|
||||
order: 15
|
||||
order: "15"
|
||||
---
|
||||
|
||||
{% callout info %}
|
||||
Admin Password Reset is available for **Enterprise Organizations** on a current plan. Like Login with SSO, Password Reset is not available to [Classic 2019 Enterprise Organizations]({{site.baseurl}}/article/2020-plan-updates).
|
||||
Admin Password Reset is available for **Enterprise Organizations** on a current plan. Like Login with SSO, Password Reset is not available to [Classic 2019 Enterprise Organizations]({{site.baseurl}}/article/2020-plan-updates/).
|
||||
{% endcallout %}
|
||||
|
||||
## What is Admin Password Reset?
|
||||
@@ -32,12 +32,12 @@ The key pair is generated and encrypted client-side upon creation of a new Organ
|
||||
- Upgrades from one Organization type to another.
|
||||
{% endcallout %}
|
||||
|
||||
When a member of the Organization [enrolls](#automatic-enrollment) in Admin Password Reset, that user's [encryption key]({{site.baseurl}}/article/account-encryption-key) is encrypted with the Organization's public key. The result is stored as the **Password Reset Key**.
|
||||
When a member of the Organization [enrolls](#automatic-enrollment) in Admin Password Reset, that user's [encryption key]({{site.baseurl}}/article/account-encryption-key/) is encrypted with the Organization's public key. The result is stored as the **Password Reset Key**.
|
||||
|
||||
When an Admin Password Reset action is taken:
|
||||
|
||||
1. The Organization private key is decrypted with the Organization symmetric key.
|
||||
2. The user's **Reset Password Key** is decrypted with the decrypted Organization private key, resulting in the users's [encryption key]({{site.baseurl}}/article/account-encryption-key).
|
||||
2. The user's **Reset Password Key** is decrypted with the decrypted Organization private key, resulting in the users's [encryption key]({{site.baseurl}}/article/account-encryption-key/).
|
||||
3. The user's encryption key and Master Password hash are replaced with a *new* encryption key and *new* Master Password hash, seeded from a new Master Password.
|
||||
4. The user's new encryption key is encrypted with the Organization's public key, replacing the previous **Password Reset Key** with a new one.
|
||||
|
||||
@@ -67,7 +67,9 @@ Users will need to [self-enroll](#self-enroll-in-password-reset) or [be auto-enr
|
||||
|
||||
### Automatic Enrollment
|
||||
|
||||
Enabling the Automatic Enrollment policy option will automatically enroll new users in Admin Password Reset when their [invitation to the Organization is accepted]({{site.baseurl}}/article/managing-users/#accept). Users already in the Organization will not be retroactively enrolled in Admin Password Reset, and will be required to [self-enroll](#self-enroll-in-password-reset).
|
||||
Enabling the Automatic Enrollment policy option will automatically enroll new users in Admin Password Reset when their [invitation to the Organization is accepted]({{site.baseurl}}/article/managing-users/#accept) and will prevent them from [withdrawing](#withdraw-enrollment) from Admin Password Reset.
|
||||
|
||||
Users already in the Organization will not be retroactively enrolled in Admin Password Reset, and will be required to [self-enroll](#self-enroll-in-password-reset).
|
||||
|
||||
{% callout success %}
|
||||
If you're automatically enrolling Organization members in Admin Password Reset, we **highly recommend notifying them of this feature**. Many Bitwarden Organization users store personal credentials in their Personal Vault, and should be made aware that Admin Password Reset could allow an administrator to access their Personal Vault.
|
||||
@@ -87,7 +89,7 @@ Once enrolled, you can **Withdraw** from Password Reset from the same dropdown u
|
||||
|
||||
{% image organizations/pwreset-withdraw.png Withdraw from Password Reset %}
|
||||
|
||||
Manually changing your Master Password or [rotating your encryption key]({{site.baseurl}}/article/account-encryption-key/) **will not** withdraw you from Admin Password Reset.
|
||||
Users in Organizations that have enabled the [Automatic Enrollment](#automatic-enrollment) policy option **will not be allowed to withdraw** from Admin Password Reset. Additionally, manually changing your Master Password or [rotating your encryption key]({{site.baseurl}}/article/account-encryption-key/) **will not** withdraw you from Admin Password Reset.
|
||||
|
||||
## Reset a Master Password
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@ categories: [organizations]
|
||||
featured: true
|
||||
popular: false
|
||||
tags: [organizations events event logs audit access control]
|
||||
order: 13
|
||||
order: "13"
|
||||
---
|
||||
|
||||
## What are Event Logs?
|
||||
@@ -14,14 +14,14 @@ Event Logs are timestamped records of events that occur within your Organization
|
||||
|
||||
{% image organizations/event-logs-updated.png Event Logs %}
|
||||
|
||||
Events Logs are [exportable](#export-events) and accessible from the `/events` endpoint of the [Bitwarden Public API](https://bitwarden.com/help/article/public-api/).
|
||||
Events Logs are [exportable](#export-events) and accessible from the `/events` endpoint of the [Bitwarden Public API]({{site.baseurl}}/article/public-api/).
|
||||
|
||||
## Events
|
||||
|
||||
Event Logs record roughly 40 different types of events. The Event Logs screen captures a **Timestamp** for the event, client app information including application type and IP (accessed by hoving over the {% icon fa-globe %} globe icon), the **User** connected to the event, and an **Event** description.
|
||||
|
||||
{% callout info %}
|
||||
Each **Event** is associated with type code (`1000`, `1001`, etc.) that identifies the action captured by the event. Type codes are used by the [Bitwarden Public API](https://bitwarden.com/help/article/public-api/) to identify the action documented by an event.
|
||||
Each **Event** is associated with type code (`1000`, `1001`, etc.) that identifies the action captured by the event. Type codes are used by the [Bitwarden Public API]({{site.baseurl}}/article/public-api/) to identify the action documented by an event.
|
||||
{% endcallout %}
|
||||
|
||||
All Event types are listed below, with their corresponding type codes:
|
||||
@@ -77,6 +77,7 @@ All Event types are listed below, with their corresponding type codes:
|
||||
- *user-identifier* enrolled in Master Password Reset. (`1506`)
|
||||
- *user-identifier* withdrew from Master Password Reset. (`1507`)
|
||||
- Master Password was reset for *user-identifier*. (`1508`)
|
||||
- Reset SSO link for user *user-identifier*. (`1509`)
|
||||
- Edited organization settings. (`1600`)
|
||||
- Purged organization vault. (`1601`)
|
||||
- Organization Vault access by a managing [Provider]({{site.baseurl}}/article/providers/). (`1603`)
|
||||
@@ -112,7 +113,7 @@ Edited organization settings.,fa-globe,Web Vault - Chrome,9876dcba-65ed-87fe-19h
|
||||
|
||||
## API Responses
|
||||
|
||||
Accessing Event Logs from the `/events` endpoint of the [Bitwarden Public API](https://bitwarden.com/help/article/public-api/) will return a JSON response like the following:
|
||||
Accessing Event Logs from the `/events` endpoint of the [Bitwarden Public API]({{site.baseurl}}/article/public-api/) will return a JSON response like the following:
|
||||
|
||||
```
|
||||
{
|
||||
@@ -151,4 +152,4 @@ Once you have the unique ID for each member, group, and collection, you can now
|
||||
- Collections
|
||||
- Groups
|
||||
|
||||
After gathering this data, you can join rows on their unique Ids to build a reference to all parts of your Bitwarden Organization. For more information on using the Bitwarden CLI, see [The Bitwarden command-line tool (CLI)](https://bitwarden.com/help/article/cli/).
|
||||
After gathering this data, you can join rows on their unique Ids to build a reference to all parts of your Bitwarden Organization. For more information on using the Bitwarden CLI, see [The Bitwarden command-line tool (CLI)]({{site.baseurl}}/article/cli/).
|
||||
|
||||
@@ -5,17 +5,17 @@ categories: [organizations]
|
||||
featured: true
|
||||
popular: false
|
||||
tags: [organizations, import]
|
||||
order: 08
|
||||
order: "08"
|
||||
---
|
||||
|
||||
Bitwarden provides a data import tool for easy migration from any password management solution to your Organization Vault. You can also use the data import tool to import from one Bitwarden Organization to another, or to import a Bitwarden [Encrypted Export]({% link _articles/importing/encrypted-export.md %}).
|
||||
Bitwarden provides a data import tool for easy migration from any password management solution to your Organization Vault. You can also use the data import tool to import from one Bitwarden Organization to another, or to import a Bitwarden [Encrypted Export]({{site.baseurl}}/article/encrypted-export/).
|
||||
|
||||
For a full list of supported import formats, see [What file formats does Bitwarden support for import?]({{site.baseurl}}/article/import-faqs/#q-what-file-formats-does-bitwarden-support-for-import), or refer to one of these articles for guidance on the most popular solutions:
|
||||
|
||||
- [Import from LastPass]({% link _articles/importing/import-from-lastpass.md %})
|
||||
- [Import from 1Password]({% link _articles/importing/import-from-1password.md %})
|
||||
- [Import from Firefox]({% link _articles/importing/import-from-firefox.md %})
|
||||
- [Import from Google Chrome]({% link _articles/importing/import-from-chrome.md %})
|
||||
- [Import from LastPass]({{site.baseurl}}/article/import-from-lastpass/)[Import from LastPass]({{site.baseurl}}/article/import-from-lastpass/)[Import from LastPass]({{site.baseurl}}/article/import-from-lastpass/)[Import from LastPass]({{site.baseurl}}/article/import-from-lastpass/)
|
||||
- [Import from 1Password]({{site.baseurl}}/article/import-from-1password/)
|
||||
- [Import from Firefox]({{site.baseurl}}/article/import-from-firefox/)
|
||||
- [Import from Google Chrome]({{site.baseurl}}/article/import-from-chrome/)
|
||||
|
||||
{% callout info %}
|
||||
**The above listed articles** describe importing to a Personal Bitwarden Vault. While the guidance for exporting from each solution will be appropriate, it's important to know that importing to an Organization is a slightly different procedure and is [documented below](#import-to-your-organization).
|
||||
@@ -35,7 +35,7 @@ Importing data to Bitwarden **can only be done from the** [**Web Vault**](https:
|
||||
{% callout warning %}Import to Bitwarden can't check whether items in the file to import are duplicative of items in your Vault. This means that **importing multiple files will create duplicative** Vault items if an item is already in the Vault and in the file to import.{% endcallout %}
|
||||
5. Select the **Import Data** button to complete your import.
|
||||
|
||||
Currently, file attachments are not included in Bitwarden import operations and will need to be uploaded to your Vault manually. For more information, see [File Attachments]({% link _articles/features/attachments.md %}).
|
||||
Currently, file attachments are not included in Bitwarden import operations and will need to be uploaded to your Vault manually. For more information, see [File Attachments]({{site.baseurl}}/article/attachments/).
|
||||
|
||||
## Length-related Import Errors
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@ categories: [organizations]
|
||||
featured: true
|
||||
popular: false
|
||||
tags: []
|
||||
order: 05
|
||||
order: "05"
|
||||
---
|
||||
|
||||
## Manage User Seats
|
||||
@@ -41,13 +41,13 @@ Removing user seats will adjust your future billing totals. The next charge will
|
||||
To ensure the security of your Organization, Bitwarden applies a 3-step process for onboarding a new member, [Invite](#invite) → [Accept](#accept) → [Confirm](#confirm).
|
||||
|
||||
{% callout success %}
|
||||
Teams and Enterprise Organizations can sync Bitwarden to an existing user directory to automatically add or remove new users using the [**Bitwarden Directory Connector**]({{site.baseurl}}/article/directory-sync).
|
||||
Teams and Enterprise Organizations can sync Bitwarden to an existing user directory to automatically add or remove new users using the [**Bitwarden Directory Connector**]({{site.baseurl}}/article/directory-sync/).
|
||||
{% endcallout %}
|
||||
|
||||
### Invite
|
||||
|
||||
{% callout success %}
|
||||
**For Enterprise Organizations**, we recommend configuring [Enterprise Policies]({{site.baseurl}}/article/policies) prior to inviting users to ensure compliance on-entrance to your Organization.
|
||||
**For Enterprise Organizations**, we recommend configuring [Enterprise Policies]({{site.baseurl}}/article/policies/) prior to inviting users to ensure compliance on-entrance to your Organization.
|
||||
{% endcallout %}
|
||||
|
||||
To invite users to your Organization:
|
||||
@@ -86,7 +86,7 @@ To confirm accepted invitations into your Organization:
|
||||
3. Select any `Accepted` users and use the {% icon fa-cog %} gear dropdown to {% icon fa-check %} **Confirm Selected**:
|
||||
|
||||
{% image organizations/org-people-options-overlay.png Confirm an Accepted user %}
|
||||
3. Verify that the [fingerprint phrase]({{site.baseurl}}/article/fingerprint-phrase) on your screen matches the one your new member can find in **Settings** → **My Account**:
|
||||
3. Verify that the [fingerprint phrase]({{site.baseurl}}/article/fingerprint-phrase/) on your screen matches the one your new member can find in **Settings** → **My Account**:
|
||||
|
||||
{% image fingerprint-phrase.png Sample Fingerprint Phrase %}
|
||||
|
||||
@@ -109,4 +109,4 @@ To remove users from your Organization:
|
||||
Depending on the particulars of your implementation, you may be able to use one of the following methods to delete a Bitwarden user account that belongs to an offboarded user:
|
||||
|
||||
1. If you're self-hosting Bitwarden, an authorized admin can delete the account from the [System Administrator Portal]({{site.baseurl}}/article/admin-portal/).
|
||||
2. If the account has an `@yourcompany.com` email address that your company controls, you can use the [delete without logging in](https://vault.bitwarden.com/#/recover-delete){:target="\_blank"} tool and confirm deletion within the `@yourcompany.com` inbox. For more information, see [Delete an Account Without Logging In](https://bitwarden.com/help/article/delete-your-account/#without-logging-in).
|
||||
2. If the account has an `@yourcompany.com` email address that your company controls, you can use the [delete without logging in](https://vault.bitwarden.com/#/recover-delete){:target="\_blank"} tool and confirm deletion within the `@yourcompany.com` inbox. For more information, see [Delete an Account Without Logging In]({{site.baseurl}}/article/delete-your-account/#without-logging-in).
|
||||
|
||||
@@ -6,7 +6,7 @@ featured: true
|
||||
popular: false
|
||||
hidden: false
|
||||
tags: [onboarding]
|
||||
order: 10
|
||||
order: "10"
|
||||
redirect_from:
|
||||
- /article/employee-onboarding-and-succession-white-paper/
|
||||
---
|
||||
@@ -33,7 +33,7 @@ The Bitwarden vision is to imagine a world where no one gets hacked. We carry th
|
||||
For Bitwarden, [different plans]({{site.baseurl}}/article/about-bitwarden-plans/) and options are connected and complementary, all originating in our vision of a hack-free world. Empowering everyone at work **and** at home with password management gets us one step closer to that goal.
|
||||
{% endcallout %}
|
||||
|
||||
A key aspect of Bitwarden is that, unlike many software applications, everything in every a Vault is [end-to-end encrypted]({{site.baseurl}}/article/what-encryption-is-used/). To maintain this security model, every person using Bitwarden must have a unique account with a unique [Master Password]({{site.baseurl}}/article/master-password). Master Passwords should be **strong** and **memorable**.
|
||||
A key aspect of Bitwarden is that, unlike many software applications, everything in every a Vault is [end-to-end encrypted]({{site.baseurl}}/article/what-encryption-is-used/). To maintain this security model, every person using Bitwarden must have a unique account with a unique [Master Password]({{site.baseurl}}/article/master-password/). Master Passwords should be **strong** and **memorable**.
|
||||
|
||||
Each user is in charge of their Master Password. Bitwarden is a Zero-knowledge encryption solution, meaning that the team at Bitwarden, as well as Bitwarden systems themselves, have no knowledge of, way to retrieve, or way to reset any Master Password.
|
||||
|
||||
@@ -49,7 +49,7 @@ Security everywhere means security anywhere, so the best password managers provi
|
||||
|
||||
### Users' Personal Vaults
|
||||
|
||||
Anyone who creates a Bitwarden account will have their own Personal Vault. Accessible from any client application, Personal Vaults are unique to each user and only that user holds the key to access it, using a combination of their Email Address and Master Password. Personal accounts, and the personal [Vault items]({{site.baseurl}}/article/managing-items/) stored therein, are the account owners responsibility. Organization [Owners, Admins, and Managers]({{site.baseurl}}/article/user-types-access-control) cannot see any other user's Personal Vault by design, guaranteeing someone's personal data remains their own.
|
||||
Anyone who creates a Bitwarden account will have their own Personal Vault. Accessible from any client application, Personal Vaults are unique to each user and only that user holds the key to access it, using a combination of their Email Address and Master Password. Personal accounts, and the personal [Vault items]({{site.baseurl}}/article/managing-items/) stored therein, are the account owners responsibility. Organization [Owners, Admins, and Managers]({{site.baseurl}}/article/user-types-access-control/) cannot see any other user's Personal Vault by design, guaranteeing someone's personal data remains their own.
|
||||
|
||||
{% image ../images/onboarding-succession/bitwarden-individual-personal-vault.png Personal Vaults %}
|
||||
|
||||
@@ -60,7 +60,7 @@ Families, Teams, and Enterprise Organizations automatically provide members indi
|
||||
|
||||
Personal Vaults are an instrumental component of the [Bitwarden approach](#the-bitwarden-approach). Employees use a range of credentials every day, personally and professionally, and **habits formed in one area typically become habits in the other**. In our view, employees that use proper security practices in their personal lives will carry over that good behavior to their professional lives, **protecting your business** in the process.
|
||||
|
||||
Using the same tool in both areas helps that habit form faster and easier. Enterprise Organizations have the option to [configure policies](#), including to disable Personal Vaults.
|
||||
Using the same tool in both areas helps that habit form faster and easier. Enterprise Organizations have the option to [configure policies](#enterprise-policies), including to disable Personal Vaults.
|
||||
{% endcallout %}
|
||||
|
||||
## Bitwarden Organizations
|
||||
@@ -73,7 +73,7 @@ Anyone can start an Organization directly from the Web Vault:
|
||||
|
||||
{% image organizations/new-org-button-overlay.png Create New Organization %}
|
||||
|
||||
Once created, you'll land in your Organization Vault, which is the central hub for all things sharing and Organization administration. Whoever launches the Organization will be the [Owner]({{site.baseurl}}/article/user-types-access-control), giving them full control to oversee the **Vault**, to **Manage** users, [Collections](#), [Groups](#), and [Policies](#), to use a suite of Bitwarden **Tools**, and to configure the Organization's **Settings**:
|
||||
Once created, you'll land in your Organization Vault, which is the central hub for all things sharing and Organization administration. Whoever launches the Organization will be the [Owner]({{site.baseurl}}/article/user-types-access-control/), giving them full control to oversee the **Vault**, to **Manage** users, [Collections](#collections), [Groups](#groups), and [Policies](#enterprise-policies), to use a suite of Bitwarden **Tools**, and to configure the Organization's **Settings**:
|
||||
|
||||
{% image getting-started/org-vault.png Organization Vault %}
|
||||
|
||||
@@ -116,7 +116,7 @@ Bitwarden takes an enterprise-friendly approach to sharing at scale. Users can b
|
||||
|
||||
### Offboarding Users
|
||||
|
||||
At Bitwarden, we see sharing of credentials as a vital aspect to getting work done efficiently and securely. We also recognize that once a credential is shared, it is *technically* possible for the recipient to keep it. For that reason, secure onboarding using appropriate [role-based access controls](#comprehensive-role--based-access-controls) and [implementing policies](#) plays an important role in facilitating secure offboarding.
|
||||
At Bitwarden, we see sharing of credentials as a vital aspect to getting work done efficiently and securely. We also recognize that once a credential is shared, it is *technically* possible for the recipient to keep it. For that reason, secure onboarding using appropriate [role-based access controls](#comprehensive-role--based-access-controls) and [implementing policies](#enterprise-policies) plays an important role in facilitating secure offboarding.
|
||||
|
||||
Offboarding users from Bitwarden involves removing users from your Organization, and like onboarding can be done [directly from the Web Vault](#adding-users) or in automated fashion [using the Directory Connector](#directory-connector).
|
||||
|
||||
@@ -127,8 +127,8 @@ Alice is a **Manager** in your Organization, which is hosted on the Bitwarden Cl
|
||||
|**Client Applications**|Uses Bitwarden on Mobile and a Browser Extension personally and professionally, and the Web Vault for occasional Organization-related work.|
|
||||
|**Email & Master Password**|Logs in to Bitwarden using `alice@company.com` and `p@ssw0rD`.|
|
||||
|**Personal Items**|Stores assorted personal items, including Logins and Credit Cards, in her Personal Vault.|
|
||||
|**Permissions in the Organization**|As a [Manager]({{site.baseurl}}/articles/user-types-access-control/), Jane can manage many aspects of Collections.|
|
||||
|**Two-step Login**|Uses Organization-wide [Duo 2FA]({{site.baseurl}}/article/setup-two-step-login-duo).|
|
||||
|**Permissions in the Organization**|As a [Manager]({{site.baseurl}}/article/user-types-access-control/), Jane can manage many aspects of Collections.|
|
||||
|**Two-step Login**|Uses Organization-wide [Duo 2FA]({{site.baseurl}}/article/setup-two-step-login-duo/).|
|
||||
|**Created Collections**|Created a Collection for her team, "Jane's Team Collection".|
|
||||
|**Shared Items**|Created and shared several Vault items that are owned by by the Organization and reside in her team's Collection.|
|
||||
|
||||
@@ -199,7 +199,7 @@ The **Personal Ownership** policy, for example, fits into earlier discussion reg
|
||||
|
||||
### Event Logs
|
||||
|
||||
Bitwarden Organizations include access to [Event Logs]({{site.baseurl}}/article/event-logs), which can be viewed directly from the Web Vault or [exported to be analyzed]({{site.baseurl}}/article/event-logs/#siem-and-external-systems-integrations) within security information and event management (SIEM) systems like Splunk. Event Logs include information about:
|
||||
Bitwarden Organizations include access to [Event Logs]({{site.baseurl}}/article/event-logs/), which can be viewed directly from the Web Vault or [exported to be analyzed]({{site.baseurl}}/article/event-logs/#siem-and-external-systems-integrations) within security information and event management (SIEM) systems like Splunk. Event Logs include information about:
|
||||
|
||||
- User-Item interactions
|
||||
- Changes made to Vault items
|
||||
@@ -208,7 +208,7 @@ Bitwarden Organizations include access to [Event Logs]({{site.baseurl}}/article/
|
||||
- Much, much more
|
||||
|
||||
{% callout success%}
|
||||
In addition to these benefits, customers appreciate the ability to tightly integrate Bitwarden into their existing systems. Bitwarden offers a robust public [API](https://bitwarden.com/help/api/) and a fully-featured command line interface ([CLI](https://bitwarden.com/help/article/cli/)) for further integration into existing Organization workflows.
|
||||
In addition to these benefits, customers appreciate the ability to tightly integrate Bitwarden into their existing systems. Bitwarden offers a robust public [API]({{site.baseurl}}/api/) and a fully-featured command line interface ([CLI]({{site.baseurl}}/article/cli/)) for further integration into existing Organization workflows.
|
||||
{% endcallout %}
|
||||
|
||||
### Self-hosting
|
||||
|
||||
@@ -5,7 +5,7 @@ categories: [organizations]
|
||||
featured: true
|
||||
popular: false
|
||||
tags: [organizations, videos, bitwarden 101]
|
||||
order: 17
|
||||
order: "17"
|
||||
---
|
||||
|
||||
## Bitwarden 101 - Organizations
|
||||
|
||||
@@ -6,7 +6,7 @@ featured: true
|
||||
popular: false
|
||||
hidden: false
|
||||
tags: [organizations, enterprise, policies]
|
||||
order: 14
|
||||
order: "14"
|
||||
---
|
||||
|
||||
## What are Enterprise Policies?
|
||||
@@ -24,7 +24,7 @@ Bitwarden highly recommends setting Enterprise Policies prior to inviting users
|
||||
Policies can be set in two locations:
|
||||
|
||||
- In your Organization, open the **Manage** tab and select **Policies** from the left menu.
|
||||
- Navigate to the Business Portal, and select the **Policies** button. For more information, see [About the Business Portal](https://bitwarden.com/help/article/about-business-portal/).
|
||||
- Navigate to the Business Portal, and select the **Policies** button. For more information, see [About the Business Portal]({{site.baseurl}}/article/about-business-portal/).
|
||||
|
||||
## Available Policies
|
||||
|
||||
@@ -87,7 +87,7 @@ Users who are removed as a result of this policy will be notified via email, and
|
||||
|
||||
### Single Sign-On Authentication
|
||||
|
||||
Enabling the **Single Sign-On Authentication** policy will require non-Owner/non-Admin users to log in with Enterprise Single Sign-On. For more information, see [Using SSO]({{site.baseurl}}/article/using-sso/#login-using-sso).
|
||||
Enabling the **Single Sign-On Authentication** policy will require non-Owner/non-Admin users to log in with Enterprise Single Sign-On. For more information, see [Access Your Vault using SSO]({{site.baseurl}}/article/sso-access-your-vault/).
|
||||
|
||||
{% callout info %}
|
||||
The **Single Organization** policy must be enabled before activating this policy.
|
||||
@@ -107,7 +107,7 @@ Vault Items that were created prior to the implementation of this policy or prio
|
||||
|
||||
### Disable Send
|
||||
|
||||
Enabling the **Disable Send** policy will prevent non-Owner/non-Admin users from creating or editing a Send using [Bitwarden Send]({% link _articles/send/about-send.md %}). Users subject to this policy will still be able to delete existing Sends that have not yet reached their [Deletion Date]({% link _articles/send/send-lifespan.md %}).
|
||||
Enabling the **Disable Send** policy will prevent non-Owner/non-Admin users from creating or editing a Send using [Bitwarden Send]({{site.baseurl}}/article/about-send/). Users subject to this policy will still be able to delete existing Sends that have not yet reached their [Deletion Date]({{site.baseurl}}/article/send-lifespan/).
|
||||
|
||||
A banner is displayed to users in the Send view and on opening any existing Send to indicate that a policy is restricting them to only deleting Sends.
|
||||
|
||||
@@ -117,15 +117,15 @@ Enabling the **Send Options** policy will allow Owners and Admins to specify opt
|
||||
|
||||
|Option|Description|
|
||||
|------|-----------|
|
||||
|Do not allow users to hide their email address|Enabling this option disables the [Hide Email option]({{site.baseurl}}/article/send-privacy/#hide-email), meaning that all [received Sends]({{site.baseurl}}/article/receive-send) will include whom they are sent from.|
|
||||
|Do not allow users to hide their email address|Enabling this option disables the [Hide Email option]({{site.baseurl}}/article/send-privacy/#hide-email), meaning that all [received Sends]({{site.baseurl}}/article/receive-send/) will include whom they are sent from.|
|
||||
|
||||
### Master Password Reset
|
||||
|
||||
Enabling the **Master Password Reset** policy will allow Owners and Admins to use [Password Reset]({{site.baseurl}}/article/admin-reset/) to reset the master password of enrolled users. By default, users will need to [self-enroll in Password Reset]({{site.baseurl}}/article/admin-reset/#self-enroll-in-password-reset), however the [Automatic Enrollment](#automatic-enrollment) option can be used to automatically enroll invited users:
|
||||
Enabling the **Master Password Reset** policy will allow Owners and Admins to use [Password Reset]({{site.baseurl}}/article/admin-reset/) to reset the master password of enrolled users. By default, users will need to [self-enroll in Password Reset]({{site.baseurl}}/article/admin-reset/#self-enroll-in-password-reset), however the [Automatic Enrollment](#automatic-enrollment) option can be used to force automatic enrollment of invited users:
|
||||
|
||||
#### Automatic Enrollment
|
||||
|
||||
Enabling the **Automatic Enrollment** option will automatically enroll new users in Password Reset when their [invitation to the Organization is accepted]({{site.baseurl}}/article/managing-users/#accept).
|
||||
Enabling the **Automatic Enrollment** option will automatically enroll new users in Password Reset when their [invitation to the Organization is accepted]({{site.baseurl}}/article/managing-users/#accept) and prevent them from withdrawing.
|
||||
|
||||
{% callout info %}
|
||||
Users already in the Organization will not be retroactively enrolled in Password Reset, and will be required to [self-enroll]({{site.baseurl}}/article/admin-reset/#self-enroll-in-password-reset).
|
||||
|
||||
@@ -5,7 +5,7 @@ categories: [organizations]
|
||||
featured: true
|
||||
popular: false
|
||||
tags: [public api, oas, organizations]
|
||||
order: 16
|
||||
order: "16"
|
||||
---
|
||||
|
||||
The Bitwarden Public API provides Organizations a suite of tools for managing members, collections, groups, event logs, and policies.
|
||||
@@ -16,12 +16,12 @@ For automating **management of Vault items**, we recommend using the [CLI]({{sit
|
||||
|
||||
The Public API is a RESTful API with predictable resource-oriented URLs, accepts JSON-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs.
|
||||
|
||||
The Public API is compatible with the OpenAPI Specification (OAS3) and publishes a compliant [`swagger.json`](https://bitwarden.com/help/api/specs/public/swagger.json) definition file. Explore the OpenAPI Specification using the Swagger UI:
|
||||
- For Public Cloud-hosted instances: [https://bitwarden.com/help/api/](https://bitwarden.com/help/api/){:target="\_blank"}
|
||||
The Public API is compatible with the OpenAPI Specification (OAS3) and publishes a compliant [`swagger.json`]({{site.baseurl}}/api/specs/public/swagger.json) definition file. Explore the OpenAPI Specification using the Swagger UI:
|
||||
- For Public Cloud-hosted instances: [https://bitwarden.com/help/api/]({{site.baseurl}}/api/){:target="\_blank"}
|
||||
- For Self-hosted instances: https://your.domain.com/api/docs/
|
||||
|
||||
{% callout info %}
|
||||
Access to the Bitwarden Public API is available customers on the following plans, **Classic 2019 Enterprise Organizations**, current **Enterprise Organizations**, and current **Teams Organizations**. For more information, see [About Bitwarden Plans](https://bitwarden.com/help/article/about-bitwarden-plans/#compare-the-plans-1).
|
||||
Access to the Bitwarden Public API is available customers on the following plans, **Classic 2019 Enterprise Organizations**, current **Enterprise Organizations**, and current **Teams Organizations**. For more information, see [About Bitwarden Plans]({{site.baseurl}}/article/about-bitwarden-plans/#compare-the-plans-1).
|
||||
{% endcallout %}
|
||||
|
||||
## Endpoints
|
||||
@@ -134,5 +134,5 @@ The Bitwarden Public API uses conventional HTTP response codes to indicate the s
|
||||
## Further Reading
|
||||
|
||||
For more information about using the Bitwarden Public API, see the following articles:
|
||||
- [Bitwarden Public API OAS Specification](https://bitwarden.com/help/api/){:target="\_blank"}
|
||||
- [Event Logs](https://bitwarden.com/help/article/event-logs/)
|
||||
- [Bitwarden Public API OAS Specification]({{site.baseurl}}/api/){:target="\_blank"}
|
||||
- [Event Logs]({{site.baseurl}}/article/event-logs/)
|
||||
|
||||
@@ -6,20 +6,20 @@ featured: false
|
||||
popular: false
|
||||
hidden: false
|
||||
tags: [sharing, how to]
|
||||
order: 04
|
||||
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/).
|
||||
In order to share items you need to be a member of an Organization. Learn more about [Organizations]({{site.baseurl}}/article/about-organizations/) 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**:
|
||||
Organization members can move items to any assigned Collection(s) unless they're given [**Read Only** access]({{site.baseurl}}/article/user-types-access-control/) 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:
|
||||
|
||||
@@ -39,7 +39,7 @@ Moving an item to an Organization **will transfer ownership to the Organization*
|
||||
|
||||
## 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:
|
||||
Organization members can create new items directly for any assigned Collection(s) unless they're given [**Read Only** access]({{site.baseurl}}/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">
|
||||
|
||||
@@ -5,7 +5,7 @@ categories: [organizations]
|
||||
featured: true
|
||||
popular: false
|
||||
tags: [user types, access control]
|
||||
order: 06
|
||||
order: "06"
|
||||
---
|
||||
|
||||
Users in Bitwarden Organizations can be granted a variety of User Types and Access Controls in order to manage their permissions and access. You can set User Types and Access Controls when you [invite users to your Organization]({{site.baseurl}}/article/managing-users/), or at any time from the **Manage** → **People** screen in your Organization:
|
||||
|
||||
Reference in New Issue
Block a user