Portfolio Permissions

What's New

Many organizations have historically used Portfolio-flagged Projects to manage hierarchical permissions and data access. With new Portfolios, permission inheritance required Workflow Rules to enable inheritance. 

Now, Portfolio permission inheritance to sub-items - Programs and Projects - is aligned with inheritance in older Project + Sub-Project hierarchies.

Editors and Viewers of a Portfolio will get the same permission access levels on the Portfolio's Programs and Projects, without needing additional configuration. 


Example: A Program with (1) directly granted permissions and (2) inherited Viewer Permission for Drivers and Planning Systems User Groups, and a user with Execs profile from the parent Portfolio


See also Portfolios

Have more questions? Submit a request