Issue Summary

In new navigation, users navigate using by using hierarchy level, such as enterprise, portfolio, program, etc..

Some user, who would have a level, let's say Portfolio, entirely disabled in permission, but have pages that are shared from another hierarchy level, would have the portfolio menu enabled, when intentionally the user should not have access

Steps to Reproduce

1. Have a user with Portfolio permission disabled
2. Have for this user another level enabled, such as TEAM- Stories
3. Notice that when logging as the user, Portfolio level is visible from the menubar
4. If the team level shared item TEAM-Stories is disabled, you can notice the portfolio item in menubar disappearing entirely

Expected Results

Ideally , a level should appear only if the hierarchy specific items are enabled
Example for portfolio:

• Portfolio specific pages and report are enabled = trigger portfolio menubar item
• If program level only is enabled = does not trigger portfolio menubar item

Actual Results

Items from other hierarchy level, or "Shared" would trigger the appearance of another hierarchy level in menubar, even if that hierarchy permission is entirely disabled in the role

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available