Overview

Jive uses a permissions inheritance model where the sub-Spaces inherit the permissions from their parent Space as a starting point. These permissions can then be further modified as needed by the administrators after disabling inheritance.

Description

Whenever a new Space is created in Jive, it inherits permissions from its parent Space or uses those permissions as a starting point if the administrators want to set up custom permissions. The inheritance relationship between Spaces means that any changes to the permissions of the parent Space will automatically change the permissions for the sub-Spaces that are inheriting its permissions.

A Default Space (or the Root Space) typically called community is provided as a starting place for the new Spaces regardless of where they are in the hierarchy. The Default Space cannot contain content but it is used as a permissions template from which all sub-Spaces inherit permissions unless otherwise configured.

Permissions Inheritance Example

In the example above:

• The Products Space is inheriting the permissions from the Default Space.
• The permissions inheritance was broken between the Default Space and the Human Resources Space as the permissions needed to be customized for this Space.
• There was a sub-Space Benefits created under the Human Resources Space which inherits the permissions from the Human Resources Space.
• The Benefits Space does not inherit permissions from the Default Space.

Things to Remember

• The Default Space (or the Root Space) is the parent Space for all new Spaces at the top level. You can customize the Default Space permissions to represent a permission set that is commonly used when creating new Spaces.
• A new Space can begin with the Default Space permissions as a starting point only by disabling inheritance after creation.
• A new Space can begin with the Default Space permissions as a starting point regardless of where the new Space is being created in the hierarchy.
• Inheritance between a Space and its parent Space can be re-established at any point. Doing this removes any customizations made to the permissions in the sub-Space.
• A new Space can also begin with no permissions set.

Related Articles

• Standard Permission Levels
• Managing Space Permissions
• Re-Establishing Permission Inheritance Between Spaces
• Creating User Overrides for Spaces