1
0
mirror of https://github.com/bitwarden/help synced 2025-12-15 15:53:53 +00:00
Files
help/_articles/organizations/about-collections.md
fred_the_tech_writer 899c14476d Organizations rev (#265)
* Organizations revisions initial commit.

* API doc updates

* Fix absolute link causing build failure.

* Add import to org article, and downstream order changes.

* Bitwarden 101 videos: 1st steps toward proliferating these throughout /help.

* Added 'Create Your Account' article, which references B101 Videos.

* About SSO redirect & promote importing for orgs up the list

* Create Org FAQs & trim Feature FAQs accordingly.

* Image for Org FAQs

* Move 'About the Business Portal' to Orgs category, and re-order accordingly.

* Final edits.

* Update to API doc.

* Returned missing getting-started-organizations article
2020-11-06 14:43:15 -05:00

2.8 KiB

layout, title, categories, featured, popular, tags, order, redirect_from
layout title categories featured popular tags order redirect_from
article About Collections
organizations
true false
collections
access control
best practices
02
/article/collections/

What are Collections?

Collections are structures used by Organizations to gather together Logins, Notes, Cards, and Identities for sharing, similar to the Folders you might use in your Personal Vault. Organizations control access to shared items by assigning users to Collections. Unlike Folders, items in the Organization Vault must be placed in one or more Collections.

Users with the User Type Manager or higher can create Collections, manage items in each Collection, and manage the users with access to each Collection. For more information, see User Types and Access Control.

Create a Collection by navigating to your Organization, opening the Manage tab, and selecting the New Collection button. For help creating a Collection, see Create a Collection.

{% image organizations/collection-list-overlay.png Select New Collection %}

Collections Best Practices

Collections are designed to associate related Logins, Notes, Cards, and Identities. You can organize your Collections however best fits your needs, but some common methodologies include:

  • Collections by Department (i.e. users from your Marketing Team are assigned to a Marketing Collection)
  • Collections by Function (i.e. users from your Marketing Team are assigned to a Social Media Collection)

{% image /organizations/collections-graphic-1.png Using Collections %}

For Teams and Enterprise Organizations, using Groups alongside Collections provides a deeper level of access control and scalability to sharing resources. When you create a Group, you can gather users from common departments and assign access to Collections at the Group-level instead of the individual-level. For more information, see About Groups.

A common Collection-Group methodology is to create Groups by Department and Collections by Function, for example:

{% image /organizations/collections-graphic-2.png Using Collections with Groups%}

Other common methodologies include:

  • Collections by Vendor or System (i.e. users in an Engineering Group are assigned to a AWS Credentials Collection)
  • Groups by Locality (i.e. users are assigned to a US Employees Group or UK Employees Group)

Next Steps

To get started using Collections, we recommend that you: