1
0
mirror of https://github.com/bitwarden/help synced 2025-12-06 00:03:30 +00:00
Files
help/_articles/organizations/policies.md
fred_the_tech_writer 535ea72847 Release Updates (#474)
* Send Staging (#447)

* - js for in-page tabs
- send category early drafts of articles
- send images

* fix scrolling on tab

* send web vault

* mobile image

* redone 'receive send' article

* send from browser ext & mobile

* send work

* improvements to 'about'

* send additions

* so much send

* lotsa send

* all send all the time

* ain't nothin but a send thang

* cli

* send cli

* simple cli sends in /create-send/

* simple disable & delete in /send-lifespan/

* send desktop screenshots

* send final cleanup

* cli final cleanup

* send edits

* fix

* send final touches

* fixed links & non-send updates

* new import message documentation, several import articles condensed to use tabs, U2F support for Edge, excluded domains article, remove in innacurate note on emergency accesss

* Firefox Attachment Workflow + Date Picker for custom timestamps

* safari attach file Send req

* excluded domains addition

* fix tab titles

* release notes

* unlock articles

* link to status feed

* small typos

* test

* updated release notes

* lastpass article form fill rewrites

* import to org & personal clarifications

* send self-hosting, safari web extension edits, and release notes
2021-03-11 11:58:16 -05:00

5.5 KiB

layout, title, categories, featured, popular, hidden, tags, order
layout title categories featured popular hidden tags order
article Enterprise Policies
organizations
true false false
organizations
enterprise
policies
14

What are Enterprise Policies?

Enterprise Polices enable Enterprise Organizations to enforce security rules for all users, for example mandating use of Two-step Login.

Enterprise Policies can be set by users with the User Type Admin or Owner.

{% callout warning %} Bitwarden highly recommends setting Enterprise Policies prior to inviting users to your Organization. Some Policies will remove non-compliant users on enabling, and some are not retroactively enforceable. {% endcallout %}

Setting Enterprise Policies

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.

Available Policies

Two-Step Login

Enabling the Two-step Login policy will require non-Owner/non-Admin users to use any two-step login method to access their Vaults.

{% callout warning %} Users in the Organization who do not have two-step login enabled will be removed from the Organization when you enable this policy.

Users who are removed as a result of this policy will be notified via email, and must be re-invited to the Organization.

  • Existing users will not be able to accept the invitation until two-step login is enabled for their Vault.
  • New users will be automatically setup with email-based two-step login, but can change this at any time. {% endcallout %}

Master Password

Enabling the Master Password policy will enforce a configurable set of minimum requirements for users' Master Password strength. Organizations can enforce:

  • Minimum Master Password complexity
  • Minimum Master Password length
  • Types of characters required

Password complexity is calculated on a scale from 0 (Weak) to 4 (Strong). Bitwarden calculates password complexity using the zxcvbn library.

{% callout warning %} Existing non-compliant users will not have their Master Passwords changed when this policy is enabled, nor will they be removed from the Organization. The next time this group of users changes their Master Password, this policy will be enforced. {% endcallout %}

Password Generator

Enabling the Password Generator policy will enforce a configurable set of minimum requirements for any user-generated passwords. Organizations can enforce:

  • Password , Passphrase, or User Preference

For Passwords:

  • Minimum Password Length
  • Minimum Number (0-9) count
  • Minimum Special Character (!@#$%^&*) count
  • Types of characters required

For Passphrases:

  • Minimum number of words
  • Whether to capitalize
  • Whether to include numbers

{% callout warning %} Existing non-compliant passwords will not be changed when this policy is enabled, nor will the items be removed from the Organization. When changing or generating a password after this policy is enabled, configured policy rules will be enforced.

A banner is displayed to users on the Password Generator screen to indicate that a policy will affect their generator settings. {% endcallout %}

Single Organization

Enabling the Single Organization policy will restrict non-Owner/non-Admin members of your Organization from being able to join other Organizations, or from creating other Organizations.

{% callout warning %} Users in the Organization who are members of multiple Organizations will be removed from the Organization when you enable this policy.

Users who are removed as a result of this policy will be notified via email, and must be re-invited to the Organization. Users will not be able to be confirmed to the Organization until they have removed themselves from all other Organizations. {% endcallout %}

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 Access Your Vault using SSO.

{% callout info %} The Single Organization policy must be enabled before activating this policy.

As a result, you must disable the Single Sign-On Authentication policy before you can disable the Single Ownership policy. {% endcallout %}

Personal Ownership

Enabling the Personal Ownership policy will require non-Owner/non-Admin users to save Vault Items to an Organization by disabling personal ownership of Vault items for organization users.

A banner is displayed to users on the Add Item screen indicating that a policy will affect their ownership options.

{% callout info %} Vault Items that were created prior to the implementation of this policy or prior to joining the Organization will remain in the user's personal Vault. {% endcallout %}

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 %}).

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.