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.
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)
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:
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)
To get started using Collections, we recommend that you: