Start a Client Organization

This article will walk you through the creation of a client organization and outline a typical setup procedure for getting started administering a customer's organization.

To create a client organization you must be a Provider admin:

1. Navigate to the Provider Portal and select the  New client organization button:

   

2. On the New Client Organization screen, enter an Organization name, Billing email, and Client owner email.

   Hinweis

   An invitation will automatically be sent to the Client owner email to join the organization as an owner.

3. From the Choose Your Plan list, select the type of organization to create.

   Tipp

   Teams and Enterprise organizations include premium features for all enrolled users.

4. Set the following options for the organization:

   • User seats: Specify the number of user seats you need for the client organization. Seats will be added if you exceed this number, unless you specify a limit.

   • Additional storage (GB): Organizations come with 1GB of encrypted storage for 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 are happy with the organization, enter your Payment Information and select Submit.

6. 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 and engage in ongoing administration:

With your newly-created client organization, you are 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, which provide an organizing structure for the vault items you will add to the vault in the next step.

   Common collections patterns include Collections by Department (for example, users in the client's Marketing Team are assigned to a Marketing collection) or Collections by Function (such as users from the client's Marketing Team are assigned to a Social Media collection):

   

2. Populate the organization vault. Once the structure of how you will store vault items is in place, you can begin populating the organization with your client's logins, notes, cards, and identities.

   Tipp

   You can create shared items from scratch, but we recommend importing a file that contains all their vault items.

3. Configure enterprise policies. Before beginning the user management portion of setup, configure enterprise policies in order to set rules-of-use for things such as master password complexity, use of two-step login, and admin password reset.

   Hinweis

   Enterprise Policies are only available to Enterprise organizations.

4. Setup login with SSO. If your customer uses single sign-on (SSO) to authenticate with other applications, connect Bitwarden with their IdP to allow authentication with Bitwarden using end-users' SSO credentials.

5. Create user groups. For Teams and Enterprise organizations, create a set of groups for scalable permissions assignment. When you start adding users, add them to groups to have each user automatically inherit the group's configured permissions (such as access to specific collections).

   One common group-collection pattern is to create Groups by Department and Collections by Function, for example:

   

6. Start inviting users. Now that the infrastructure for the secure and scalable sharing of credentials is in place for your client, you can begin inviting users to the organization. To ensure the security of the organization, Bitwarden applies a three-step process for onboarding new users, Invite → Accept → Confirm.

   Tipp

   If your customer uses directory service or IdP (active directory, an LDAP, Okta, and more), use SCIM or Directory Connector to automatically sync organization users from the source directory and automatically issue invitations.