bitwarden/help
1
0
Fork 0
mirror of https://github.com/bitwarden/help synced 2025-12-11 05:43:20 +00:00
Code Issues Releases Wiki Activity

renaming articles

Browse Source
This commit is contained in:
Kyle Spearrin
2018-10-29 15:12:20 -04:00
parent b03c600b94
commit b74dc04999
3 changed files with 7 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
_articles/features/folders.md
View File

@@ -1,10 +1,10 @@
---
layout: article
title: Folders
title: Organizing your vault with folders
categories: [features]
featured: false
popular: false
tags: [categories]
tags: [categories, folders, sub-folders]
---
Folders are a great way to categorize items in your Bitwarden vault.

6
_articles/organizations/collections.md
View File

@@ -1,17 +1,17 @@
---
layout: article
title: Collections
title: Controlling vault access with collections
categories: [organizations]
featured: true
popular: false
tags: []
tags: [collections, sub-collections, access control]
---
Collections allow you to group related items that are being shared from your organization's vault. 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. Servers, Social Media Accounts, Executives, etc).
{% image organizations/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 items 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 add, edit, or delete any items within that particular collection (they can just view and use them).
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 items 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 add, edit, or delete any items within that particular collection (they can just view and use them). You can also associate [user groups]({% link _articles/organizations/groups.md %}) to collections in the same way.
{% note %}
Collections are different than [folders]({% link _articles/features/folders.md %}). Collections are a way to organize items and control user access within an organization’s vault while folders are a way for individual users to organize items within their own personal vault. An individual user may wish to further organize the items being shared with them in their own vault into a personalized folder structure that makes sense just for them.

4
_articles/organizations/groups.md
View File

@@ -4,10 +4,10 @@ title: User groups
categories: [organizations]
featured: true
popular: false
tags: []
tags: [groups, access control]
---
In addition to collections, groups are a way for organizations to further control user access. They are particularly useful to larger organizations where user access can be difficult to manage.
In addition to [collections]({% link _articles/organizations/collections.md %}), groups are a way for organizations to further control user access. They are particularly useful to larger organizations where user access can be difficult to manage.
{% note %}
User groups are only available to enterprise organizations.