Changes
Page history
vault: explain collections (tpo/tpa/team#42186)
authored
Nov 26, 2025
by
anarcat
Show whitespace changes
Inline
Side-by-side
service/vault.md
View page @
b2e3167c
...
...
@@ -105,6 +105,37 @@ Create new Folders or Collections using the **"New"** button.
-
[
Folders
](
https://bitwarden.com/help/folders/
)
-
[
Collections
](
https://bitwarden.com/help/about-collections/
)
## Sharing a secret with other users
The primary way to share secrets with other users is through the
[
Collections
](
https://bitwarden.com/help/about-collections/
)
feature. A "Collection" is like a "Folder" in the
sense that it organizes items in a nested structure, but contrarily to
a Folder, it allows you to grant access for specific sets to specific
groups or users.
Say you want to share a password with your team. The first step will
be to create a new Collection for your team, if it doesn't already
exist. For this, you:
1.
click the
**New**
(top right) button and select
**Collection**
2.
pick a correct name for the collection (e.g. "Foo admins" for the
admins of the service "Foo" or "Bar team" for everyone in the
team "Bar")
3.
nest the collection under the right collection, typically, "Foo
admins" would be nested under the "Bar team", for example, this
will grant access to everyone under the parent collection!
4.
For more advanced access control, click the
**Access**
tab where
you can grant users or groups the permission to "View items" by
selecting them in the
**Select groups and members**
drop down
5.
Click
**save**
The two crucial steps are steps 3 and 4, which determine who will have
access to the secret. Typically, passwords should be shared with teams
and simply picking the right Collection when creating a password.
It's only if you want to give access to a single user or a new,
perhaps ad-hoc, team that you will need to create a new Collection.
# How-to
## Add a user
...
...
...
...