Stopping Inheritance

Note: This is an advanced option and should be used with caution!

You can add security rows on objects without stopping the inheritance. For example, map1 inherits a security row with Edit permission for the R&D group. In map1 properties, you add a new security row that grants R&D with Admin permission. Now R&D has combined permissions of both Edit and Admin.

However, it may be desirable to start a new inheritance string. For example, R&D admin wants to have full control of all security settings for R&D portfolios and items. The topmost portfolio in the R&D tree is portfolio R&D. In this case, you should stop inheritance for portfolio R&D, and define the security entirely on the portfolio.

In the scenario described above, all other portfolios, items, deliverables, documents, and data of R&D still continue to inherit their security settings from R&D (directly or indirectly), but changes made on the items and portfolios root folder have no effect on them.

To stop security inheritance:

  1. In the Security tab of the Wizard, uncheck the Inheriting settings from checkbox.

    A dialog box appears.

  2. To copy all security rows that were previously inherited, click Copy. To remove all inherited permissions, click Remove.

Related Topics

Hierarchies and Inheritance

Defining a Security Policy

Defining a Security Policy on a Root Folder

Inheriting from the Home Folder/Portfolio

Security Settings on Objects

Resetting Permissions



Legal Notices | Your Privacy Rights
Copyright © 1998, 2020

Last Published Thursday, December 10, 2020