Restoring Permission Inheritance 

Use

Based on the permission inheritance model, folders and unit objects in the Portal Catalog inherit the permissions of their parent folder, unless they have their own explicitly assigned permissions.

When you assign permissions directly to a folder or object, the permission inheritance between the folder/object and its parent folder become disconnected. In such cases, any future changes you make to permissions of the parent folder are no longer passed to the object or sub-folder with the assigned permissions. For more details and examples, see Permission Inheritance Model.

The Permission Editor allows you to reset assigned permissions in different directions, based on the hierarchy of objects in the Portal Catalog. You may:

·        Restore permission inheritance from a selected folder to all its child objects.

Once you have removed manually assigned permissions, all child objects inherit the permissions assigned to the selected folder.

This action is recursive, including sub-folders and respective child objects. If the selected folder contains more than one object, you cannot choose to which child object permissions are reset—permissions will be reset for all objects under that folder.

·        Restore permission inheritance from a selected object or sub-folder back to its parent folder.

You can select a folder or object and remove permissions that are explicitly assigned to it. Once you have removed manually assigned permissions, the selected folder or object will inherit the permissions assigned to its parent folder.

As a result of this change, the permissions of child objects and sub-folders in the selected folder may also be indirectly affected. If child objects and sub-folders inherit their permissions from the selected folder, they will now inherit the new permissions of the selected folder.

You cannot directly modify the permission of a particular PCD object assigned as a child object (non-unit object) to another PCD object, such as an iView in a portal page or a portal page in a role. Non-unit child objects always inherit permissions from their parent object.

 

Prerequisites

·        You must have owner administration permission to restore and reset permission inheritance.

 

Procedure

Reset Permissions to Objects in a Folder:

...

       1.      Open a folder in the Permission Editor. See Launching the Permission Editor.

       2.      In the Permission Editor, choose Reset Child Permissions.

Resetting Permission Inheritance from an Object/Folder to its Parent Folder

...

       1.      Open the object or folder in the Permission Editor. See Launching the Permission Editor.

       2.      In the Permission Editor, choose Restore Inheritance.

§         If the parent folder of the selected object or sub-folder does not contain assigned permissions, it will inherit the permissions of the closest ancestor (folder) that has permissions assigned to it.

§         To display the permissions the current object's closest ancestor that does have permissions assigned to it, choose Permission Source in the tools area at the bottom.

§         If you restore inheritance for a given object and as a result its permission changes to a setting other than owner permission, the Permission Editor will automatically revert to read-only mode, and you will not be able to make further changes.

For examples of restoring permission inheritance, see steps 4a and 4b in Permission Examples.