80a0b17ac6
* jekyll redirect from * Organizations rev (#262) * 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. * Dchoi/bootstrap upgrade (#264) * bootstrap 4 upgrade and cleanup update gulp tasks * bootstrap package updates * renaming file convention * general outline of help outline * bitwarden help cleanup * article cleanup * article general styling complete * bootstrap help page upgrades * sidebar updates * Dchoi/bootstrap upgrade (#267) * bootstrap 4 upgrade and cleanup update gulp tasks * bootstrap package updates * renaming file convention * general outline of help outline * bitwarden help cleanup * article cleanup * article general styling complete * bootstrap help page upgrades * sidebar updates * toc dynamic and more updates * fix callout conditions * sidebar collapse functionality added * sidebar header toggle functionality * sidebar article fixes * Update sidebar.html Fix sidebar Release Notes link. * Update releasenotes.md Remove unnecessary category tag. * Delete release-notes.md Remove unnecessary category. * Update why-choose-bitwarden-for-your-team.md Test table image differentiation * Update why-choose-bitwarden-for-your-team.md Second image differentiation test * removed links from category breadcrumb and replaced with badges Co-authored-by: fred_the_tech_writer <69817454+fschillingeriv@users.noreply.github.com>
2.5 KiB
layout, title, categories, featured, popular, tags, order, redirect_from
| layout | title | categories | featured | popular | tags | order | redirect_from | ||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| article | Create a Collection |
|
true | false |
|
05 |
|
This article will guide you through the process of creating a Collection. For more information about Collections, see About Collections.
Create A Collection
Complete the following steps to create a collection:
-
Login to your Web Vault{:target="_blank"} and open your Organization.
-
In your Organization, open the Manage tab and select Collections from the left menu.
-
On the Collections screen, select the New Collection button.
{% image organizations/collection-list-overlay.png Select New Collection %}
-
On the Add Collection screen:
- Enter a Name for your Collection.
- Enter an External Id for your Collection. External ids are used to link resources to external systems, like user directories.
- (Teams and Enterprise Organizations) Set the Group Access configuration for your Collection, including which Groups should be allowed to access this Collection. For more information, see About Groups.
-
Select Save to finish creating your Collection.
Create Nested Collections
Collections be "nested" in order to logically organize them within your Vault. There's no limit to the depth with which you can nest Collections, but creating too many levels may interfere with your Vault's interface.
{% callout info %} Nested Collections are designed for in-Vault display purposes only. Nested Collections will not not inherit access or permissions from their "parent" Collection. {% endcallout %}
{% image organizations/collection-nested.png Nested Collection %}
To create a nested Collection, give your new Collection a Name that includes the "parent" Collection followed by a forward slash (/) delimiter, for example Collection 1/Collection 1a.
If there is no Collection with the corresponding "parent" name or if you don't have access to the "parent", the Collection won't nest and instead it's title will be displayed in-full.
{% image organizations/collection-nested-create.png Create a nested Collection %}
Next Steps
Now that you've created a Collection, we recommend that you: