Moderation inheritance in groups and spaces
Moderation inheritance works differently depending on the container of the content.
Here's how moderation inheritance works in places:
- Groups inherit the moderation settings of the root container (also known as the system container or a Jive community) and are moderated by global moderators, if there is one, and if not, by the Full Access users.
- Projects inherit the moderation settings of their container space or sub-space and are moderated by space moderators, if there is one, and if not, by the global moderators. If there are no global moderators, the application will send the moderation request to the Full Access users.
Note: Projects inherit the moderation settings of their parent space or sub-space. The
exception is status updates posted in projects, which are moderated the same way as
status updates posted in a group.
For a complete list of content types and the places where you can and cannot enable moderation, see Moderation rules and notification hierarchy and Moderation overview.
The following illustration shows how moderation inheritance works and the order in which moderators are notified:
