Subgroup

Key point: A streamlined way to manage multiple users across different groups, allowing you to add or remove entire sets of users at once.

A subgroup is a collection of users that can be managed as a single unit within PageSeeder, allowing you to efficiently assign multiple people to projects or resources. Any group in PageSeeder can be used as a subgroup.

When you add a subgroup to another group (called a supergroup), all members of the subgroup automatically gain access to the supergroup’s resources according to defined permission rules.

Only one level of subgroups is processed, so a subgroup of a subgroup is not considered part of the supergroup. For example if group A has a subgroup B and group B has a subgroup C, then C is not part of A.

Common use case

Consider a team that works on multiple projects within your organization. Instead of individually adding each team member to every project group, you can create a “Team” subgroup once and add it to each group as needed.

When a new team member joins, you add them to the “Team” subgroup, and they automatically gain access to all projects where the team is involved.

Similarly, when someone leaves, removing them from the subgroup instantly revokes their access across all related projects. This streamlined management saves time and reduces the risk of forgetting to add or remove users from specific groups.

Permission inheritance

When adding a subgroup, you have two options for how members inherit permissions:

  • Inherit the same roles and preferences as the subgroup (except moderator becomes manager and moderator & approver becomes approver); or
  • Override existing roles and preferences from the subgroup.

If a user is a member of multiple subgroups then:

  • PageSeeder applies the role with the highest permission level.
  • The notification setting with the highest frequency is displayed, but all notification types are still applied (for example, a member could receive both normal (immediate) and daily (digest) notification).
  • The member’s email is visible to other members if it’s set to be displayed in at least one subgroup.

If a user is also a direct member of the supergroup, their role and preferences in the supergroup override any settings from the subgroups.

Member details fields from subgroups are only displayed if they have the same details type name as that of the supergroup, the same owner, and the details configuration file has the shared="true" attribute.