Problem:

We have heard from customers and developer advocates that our current navigation mechanism does not fit the needs of developers, nor for admins who are responsible for the dev experience.

Currently, developers are provided with the following

1. they are brought into the developer perspective the first time they log in
2. we provide a set of default navigation items along with 2 pre-pinned resources
3. users are allowed to add/remove pinned resources from the nav (which are listed in the order they are added)

What specifically have we heard from customers?

1. Admins want the ability to set the default nav for all of their developers.  Example scenario - if Pods is something that developers access frequently, why force all of the devs to customize their nav, when the admin could make a single modification to impact all developers
2. Admins want the ability to hide the Admin Perspective for Developers
3. ** we have also heard that some privileged users would like to "hide" the Developer Perspective

Goal:

Provide the following:

1. Admins should be able to customize the default set of nav items for the developer perspective(non priv user), but still allow the user to customize
2. Admins should be able to customize the default set of nav items for a developer (non priv user), but disallow customization by the developer
3. Admins should be able to hide the admin perspective for a developer (non priv user), but still allow the user to customize
4. Admins should be able to hide the admin perspective for a developer (non priv user), but disallow customization by the developer
5. As part of the customizing nav items, admin/users should be able to create parent folders in addition to add/remove pages

Why is it important?

Use cases:

1. <case>

Acceptance criteria:

1. <criteria>

Dependencies (External/Internal):

Design Artifacts:

Exploration:

Note: