Groups

A group is a collection of users who share a common organizational or functional responsibility. When a user is a member of a group, the user automatically inherits all user roles assigned to the group, as well as any roles granted to the group within specific security domains.

Groups Configuration

Groups are stored in the repository at /hippo:configuration/hippo:groups, as child nodes of hipposys:groupfolders. Group folders can be nested, similar to user folders. Each group is represented by a single node, with the node name matching the group name. Group members are listed in the multi-valued property hipposys:members, referencing each member by their user node name.

Note:
The group node type includes a hipposys:groups property, but nested groups are not supported.

You can manage groups directly in the CMS or synchronize them with an external source such as LDAP. For groups managed in the CMS, use the hipposys:group node type. For groups managed externally, use the hipposys:externalgroup node type. The hipposys:securityprovider property identifies the security provider for the group. For CMS-managed groups, this value is internal.

To mark a group as a system group, set the hipposys:system property to true. System groups are protected and do not appear in the CMS setup management UI.

Node Type Definitions

hipposys:group

[hipposys:group] > nt:base
- hipposys:securityprovider (string) = 'internal' mandatory autocreated
- hipposys:system (boolean)
- hipposys:members (string) multiple
- hipposys:groups (string) multiple
- hipposys:description (string)
- hipposys:userroles (string) multiple
copy

Name	Type	Required	Description
node name	String	yes	The group name.
hipposys:system	Boolean	no	Indicates if the group is a system group. System groups are hidden from group management in Bloomreach Content.
hipposys:members	String	yes	The usernames of users who are members of the group. Each value contains one username.
hipposys:groups	String	no	Not used or implemented.
hipposys:description	String	no	Description of the group.
hipposys:userroles	String	no	User roles assigned to the group.

hipposys:externalgroup

[hipposys:externalgroup] > hipposys:group
- hipposys:syncdate (date)
- * (string)
copy

hipposys:groupsfolder

[hipposys:groupfolder] > nt:base
+ * (hipposys:group) = hipposys:group
+ * (hipposys:groupfolder) = hipposys:groupfolder
copy

Example Group Configuration

/hippo:configuration:
  /hippo:groups:
    /admin:
      jcr:primaryType: hipposys:group
      hipposys:members: [ admin ]
      hipposys:userroles: [ xm.default-user.system-admin ]
    /mygroup:
      jcr:primaryType: hipposys:group
      hipposys:members: [ ann, robbert, mary ]
      hipposys:userroles: [ my.author ]
copy

Default Provided Groups

name	userrole	members	system	description
author	xm.default-user.author		no	Members can edit content.
editor	xm.default-user.editor		no	Members can edit and (de)publish content.
webmaster	xm.default-user.webmaster		no	Members can edit HST configuration and configure channels.
admin	xm.default-user.system-admin xm.repository-browser.user		no	Members have all privileges.
cms-admin	xm.default-user.cms-admin		no	Members have CMS administrative privileges.
everybody		*	yes	Every logged-in user is automatically a member of this group.