Moderation inheritance works differently depending on the content's container.
Here's how moderation inheritance works in places:
- Groups inherit the moderation settings of the system container (also known as the root container or the Jive Community) and are moderated by the Global Moderator(s), if there is one, and if not, by the Full Access user(s).
- Projects inherit the moderation settings of their container space or sub-space and are moderated by the Space Moderator(s), if there is one, and if not, by the Global Moderator(s). If there is no Global Moderator, the application will send the moderation request to the Full Access user(s).
Note: Projects inherit the moderation settings of their container space or sub-space except
in the case of 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 Who Moderates What? and What Cannot Be Moderated?
The following illustration shows how moderation inheritance works and the order in which moderators are notified:
