This article provides information on the use of 'User Groups' in Jive to assign permissions to multiple users at once.
You can define a group of users to assign them a variety of permissions quickly. Forming user groups that reflect the kinds of access you need to grant is a convenient way to manage people's access to application features. You define such groups in your Jive community itself, in an external user identity system (such as an LDAP system), or the application database. Additionally, three system-defined user groups are available by default.
For more information about user groups, see Managing User Groups.
System-Defined User Groups
The application includes three user groups that are defined by the system. These are an excellent place to start when managing permissions that are in effect across the community. After you have figured out how you want to apply permissions for these broad groups, you can start assigning permissions to user groups you create. Below is an introduction to the system-defined user groups.
This group includes anyone who visits the site, including anonymous users. Think about what you want people to be able to do anonymously, but weigh that against the need to engage people to encourage them to participate. Note that users who only view content are not counted among the number of users your license provides for. Please also note that administrators of internal communities are not allowed to modify permissions on the 'Everyone' group.
All Registered Users
This group includes people who have entered registration information and logged in for access. Use this group when you want to ensure that certain kinds of access go only to people who have an account on the system.
All External Contributor Users
This group includes external users who are not members of the community but have some access to community resources. For more information about external users, see Managing External Groups.
Your (Custom) User Groups
You can also set up custom user groups. Jive recommends that these groups should reflect your community's structure. There could be relatively few user groups, with separate groups for those who manage, moderate, and administer the community. Or there could be many, for example, groups representing departments in your organization, people with specific privileges (such as blogging), and virtual teams within the organization, etc.