mirror of
https://github.com/bitwarden/help
synced 2025-12-06 00:03:30 +00:00
organization articles
This commit is contained in:
1
.publish
Submodule
1
.publish
Submodule
Submodule .publish added at d205980607
16
_articles/organizations/collections.md
Normal file
16
_articles/organizations/collections.md
Normal file
@@ -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.
|
||||
38
_articles/organizations/managing-users.md
Normal file
38
_articles/organizations/managing-users.md
Normal file
@@ -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 %}
|
||||
14
_articles/organizations/what-is-an-organization.md
Normal file
14
_articles/organizations/what-is-an-organization.md
Normal file
@@ -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.
|
||||
5
_categories/organizations.md
Normal file
5
_categories/organizations.md
Normal file
@@ -0,0 +1,5 @@
|
||||
---
|
||||
layout: category
|
||||
title: Organizations
|
||||
featured: true
|
||||
---
|
||||
@@ -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)
|
||||
"<a href=\"images/#{src}\" target=\"_blank\">
|
||||
<img class=\"img-responsive img-thumbnail\" src=\"images/#{src}\" />
|
||||
src = @markup.strip
|
||||
"<a href=\"/images/#{src}\" target=\"_blank\">
|
||||
<img class=\"img-responsive img-thumbnail\" src=\"/images/#{src}\" />
|
||||
</a>"
|
||||
end
|
||||
end
|
||||
|
||||
BIN
images/collection-listing.png
Normal file
BIN
images/collection-listing.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 88 KiB |
BIN
images/invite-modal.png
Normal file
BIN
images/invite-modal.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 56 KiB |
BIN
images/org-people-options.png
Normal file
BIN
images/org-people-options.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 25 KiB |
BIN
images/user-accept.png
Normal file
BIN
images/user-accept.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 95 KiB |
Reference in New Issue
Block a user