Show TOC

Example documentationPermission Examples Locate this document in the navigation structure

 

The following examples illustrate the use of the permission inheritance model. Follow the examples sequentially to understand how the rules and activities described in the Permission Inheritance Model section affect permission inheritance.

Step 1

The following figure illustrates the permission inheritance within a basic hierarchy of objects in the Portal Catalog:

This graphic is explained in the accompanying text.

  • Folder A and D have assigned permissions. Folder B, Folder C, Role 1, and Page 1 do not have assigned permissions and ultimately inherit their permissions from Folder A.

  • Any changes made to the permissions of Folder A are immediately reflected in Folder B, Folder C, Role 1, and Page 1.

  • Any new objects or folders created in the Portal Catalog under Folder A, Folder B or Folder C will inherit the permissions set for Folder A.

Step 2

In the following figure, Folder B has now been assigned its own permissions:

This graphic is explained in the accompanying text.

  • Folder C, Role 1, and Page 1 now inherit their permissions from their closest ancestor that has assigned permissions: Folder B.

  • Any changes made to the permissions of Folder A are not passed to Folder B, Folder C, Role 1, or Page 1.

  • Any changes made to the permissions of Folder B are passed to Folder C, Role 1, and Page 1.

Step 3

In the following figure, Role 1 has now been assigned its own permissions:

This graphic is explained in the accompanying text.

  • Any changes made to the permissions of Folder A or Folder B are not inherited by Role 1.

  • The permissions of Role 1 are not reflected in nor affect Page 1.

  • Any changes made to the permissions of Folder B are passed only to Folder C and Page 1.

Step 4a

In the following figure, the permissions of Role 1 have now been reset (using the Restore Inheritance option in the Permission Editor):

This graphic is explained in the accompanying text.

  • Role 1 now inherits the permissions of its closest ancestor that has permissions assigned to it: Folder B.

  • Any changes made to the permissions of Folder B are immediately reflected in Role 1.

Step 4b

In the following figure, the permissions of all child objects for Folder A have now been reset (using the Reset Child Permissions option in the Permission Editor):

This graphic is explained in the accompanying text.

  • Folder B, Folder C, Role 1 and Page 1 now inherit the permissions of their closest ancestor that has permissions assigned to it: Folder A.