diff --git a/.publish b/.publish new file mode 160000 index 00000000..d2059806 --- /dev/null +++ b/.publish @@ -0,0 +1 @@ +Subproject commit d20598060759b97f4a71927acef41c802e992a9b diff --git a/_articles/organizations/collections.md b/_articles/organizations/collections.md new file mode 100644 index 00000000..03e62709 --- /dev/null +++ b/_articles/organizations/collections.md @@ -0,0 +1,16 @@ +--- +layout: article +title: Collections +categories: [Organizations] +featured: true +popular: false +tags: [] +--- + +Collections allow you to group related logins within your organization that your wish to share. A simple personal organization for a family may only want to have one or two collections (ex. Parents and Kids), while a larger organization like a company may have many collections (ex. each department such as Sales, IT, Developers, Dev Ops, etc). + +{% image collection-listing.png %} + +When you add a new user to your organization, you can associate that user to one or more collections within your organization. Once the user has access to your organization, any logins that are placed into that user's associated collections will be available in their vault. When associating a user to a particular collection, you can also decide whether or not that user has write access to logins contained within it. Selecting the **Read Only** option will ensure that the user cannot edit any logins within that particular collection (they can just view and use them). + +Note that collections are different than folders. Collections are a way to organize logins and limit user access within an organization’s vault while folders are a way for individual users to organize logins within their own personal vault. An individual user may wish to further organize the logins being shared with them in their own vault into a personalized folder structure that makes sense just for them. \ No newline at end of file diff --git a/_articles/organizations/managing-users.md b/_articles/organizations/managing-users.md new file mode 100644 index 00000000..764e97e2 --- /dev/null +++ b/_articles/organizations/managing-users.md @@ -0,0 +1,38 @@ +--- +layout: article +title: Managing organization users +categories: [Organizations] +featured: true +popular: false +tags: [] +--- + +## Onboarding Users + +Adding new users to your organization involves a three step process: invite, accept, and confirm. + +To **invite** a user to your organization simply enter their email address, select what type of user they are (normal user, admin, or owner) and select the collection(s) that they should have access to (you can change this later by editing the user). You can also designate a user as having access to all items for the organization and collection assignment will not be necessary. + +{% alert info %} +Enterprise organizations can sync their existing user directory with their bitwarden organization to automatically invite new users into bitwarden. +{% endalert %} + +{% image invite-modal.png %} + +Once you invite a user they will receive an email where they will need to click a link to **accept** the invitation. After clicking the accept link the user will be prompted to create a new bitwarden account or log into the an existing account registered at that email address. + +{% image user-accept.png %} + +After the user has successfully accepted the organization invite, an organization admin will then need to **confirm** the user from the same area in the web vault that you invited the user from (Organization Admin -> People). Only after the user is confirmed will they then have access to that organization and the items being shared with them. + +{% image org-people-options.png %} + +## Removing Users + +{% alert info %} +Enterprise organizations can sync their existing user directory with their bitwarden organization to automatically remove users when they are disabled or deleted from the directory. +{% endalert %} + +To remove a user from your organization, select the **Remove** option from the options menu for that user. Once a user is removed from your organization, they will no longer have access to any shared logins. + +{% image org-people-options.png %} diff --git a/_articles/organizations/what-is-an-organization.md b/_articles/organizations/what-is-an-organization.md new file mode 100644 index 00000000..1cba2ae1 --- /dev/null +++ b/_articles/organizations/what-is-an-organization.md @@ -0,0 +1,14 @@ +--- +layout: article +title: What are organizations? +categories: [Organizations] +featured: true +popular: false +tags: [] +--- + +A bitwarden organization is an entity that relates users together that want to share logins. An organization could be a family, team, company, or any other type of group that desires to share logins in bitwarden. + +An individual user account can create and/or belong to many different organizations, allowing you to manage your logins from a single account. + +You can create a new bitwarden organization from the [web vault](https://vault.bitwarden.com) or request that an admin of an existing organization send you an invite. \ No newline at end of file diff --git a/_categories/organizations.md b/_categories/organizations.md new file mode 100644 index 00000000..a6f2b1c0 --- /dev/null +++ b/_categories/organizations.md @@ -0,0 +1,5 @@ +--- +layout: category +title: Organizations +featured: true +--- diff --git a/_plugins/image.rb b/_plugins/image.rb index 3c70f710..be949e9a 100644 --- a/_plugins/image.rb +++ b/_plugins/image.rb @@ -1,15 +1,10 @@ module Jekyll module Tags - class ImageTag < Liquid::Block - def initialize(tag_name, src) - super - src.strip! - @src = src - end - + class ImageTag < Liquid::Tag def render(context) - " - + src = @markup.strip + " + " end end diff --git a/images/collection-listing.png b/images/collection-listing.png new file mode 100644 index 00000000..ea6aa8e3 Binary files /dev/null and b/images/collection-listing.png differ diff --git a/images/invite-modal.png b/images/invite-modal.png new file mode 100644 index 00000000..ac5a3194 Binary files /dev/null and b/images/invite-modal.png differ diff --git a/images/org-people-options.png b/images/org-people-options.png new file mode 100644 index 00000000..a6643fac Binary files /dev/null and b/images/org-people-options.png differ diff --git a/images/user-accept.png b/images/user-accept.png new file mode 100644 index 00000000..d32d062f Binary files /dev/null and b/images/user-accept.png differ