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.2 KiB
layout, title, categories, featured, popular, tags, order, redirect_from
| layout | title | categories | featured | popular | tags | order | redirect_from | ||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| article | About Groups |
|
true | false |
|
03 |
|
What are Groups?
Groups are structures used by Organizations to together individual users, and provide a scalable way to assign access (including assigning Collections) by configuring Access Controls at the Group-level instead of at the individual-level.
{% callout info %} Groups are currently available to Teams Organizations and Enterprise Organizations. {% endcallout %}
When onboarding new users, add them to a Group to have them automatically inherit that Group's Access Controls configuration.
Users with the User Type Admin or higher can create Groups, assign users to each Group, and construct Group-Collection associations. For more information, see User Types and Access Control.
Create a Group by navigating to your Organization, opening the Manage tab, and selecting the New Group button. For help creating a Group, see Create a Group.
{% image /organizations/groups-newgroup.png Select New Group %}
Groups Best Practices
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.
A common Group-Collection methodology is to create Groups by Department and Collections by Function, for example:
{% image /organizations/collections-graphic-2.png Using 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 Groups, we recommend that you: