* 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>
5.8 KiB
layout, title, categories, featured, popular, hidden, tags, order
| layout | title | categories | featured | popular | hidden | tags | order | |
|---|---|---|---|---|---|---|---|---|
| article | Start a Client Organization |
|
false | false | false | 04 |
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.
Create a Client Organization
{% callout success %} Already have an Organization setup for your customer? You can add an existing Organization to the Provider Portal. {% endcallout %}
To create a Client Organization you must be a Provider Admin:
-
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 %}
-
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.{% endcallout %}
-
From the Choose Your Plan list, select the type of Organization to create.
{% callout success %}Teams and Enterprise Organizations include premium features for all enrolled users.{% endcallout %}
-
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. 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.
-
Once you're happy with the Organization, enter your Payment Information and select Submit.
-
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:
{% 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:
-
Create Collections. A good first step is to create a set of Collections, 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 %}
-
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, but we recommend importing a file that contains all their Vault items.{% endcallout %}
-
Configure Enterprise Policies. Before beginning the user management portion of setup, configure Enterprise Policies in order to set rules-of-use for things like Master Password complexity, use of Two-step Login, and Admin Password Reset.
{% callout info %}Enterprise Policies are only available to Enterprise Organizations.{% endcallout %}
-
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.
-
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 (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 %}
-
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. 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 to automatically sync Organization users from the source directory and automatically issue invitations.{% endcallout %}