A user group makes managing permissions easier by gathering users into one group. For example, you might create a user group called "hr_users" and add user accounts for people in the human resources department. The existence of user groups isn't visible in the application's user interface.
User groups are made up of members and admins. Unless they have access to the Admin Console, members typically aren't aware that they're in a user group. The account simply defines (at least partly) their access to the application's features. Group admins have access to the area of the Admin Console through which they can manage settings and membership for a group they're administering. By default, they get to this feature by directing their browser to a URL as described in Starting the Admin Console. Unless they have other types of admin access, they'll only be able to access account management pages for the account they're administering.
Be sure to see Managing User Accounts and User Groups for overview information on how accounts work.
Note that if your community uses an external database (such as LDAP or Active Directory) to manage user identities, you won't by default be able to use the Admin Console to edit information managed there. Also, it's possible for your community to use an external data store for user account information, but not for user groups (which you can instead create and manage with the Admin Console). For more information about using LDAP or Active Directory with Jive, take a look at the ) LDAP and Active Directory Guide.
Try defining user groups before launching the community. For example, you can group users according to employee job function or department. User and Group permissions can be assigned on a space or sub-space basis.
If you want Admins to have the same permissions (if any) granted to a user group, then you need to also add them to the Group Member list. When admins are not added to the Group Members list, they only have permission to add or remove users from the Group Members and Group Admins lists, and they do not have the permissions (if any) assigned to the user group.
To edit the membership list for an existing user group
Group settings are simple, including the group's name and description, along with group properties. You can edit a group's settings in the Admin Console by going to the Group Summary page, then clicking the group's name.
Group properties are simple name-value pairs that programmers can use to work with the group in their code. Group properties are often used as a way to keep track of extra information about the group. For example, if groups are defined based on company departments, each could have a departmentID property whose value is the department's internal billing ID. A group can have multiple properties. When you're working with properties, remember that entering the name and value for an existing property will update that property's value to the one you entered.