### Problem to solve In an effort to extend the dashboard framework to accommodate other dashboard views within the larger navigation of GitLab, we need to decouple it from the Analyze navigation space. While it makes sense to have those connected for the larger customization plans (custom dashboards and data exploration), the framework is flexible enough to additionally support dashboard views outside this space and thus improve the consistency of said views throughout the GitLab UI. The first use case we are encountering where the team would like to use the framework to update their dashboard view is the Secure → Security dashboard. ### Proposed solution We should unblock any internal teams who would like to adopt the dashboard framework, but who also are not ready to move their dashboards into the consolidated, customizable dashboard space (Analytics dashboards). We should do this by decoupling the analytics dashboards UI from the Analytics dashboards navigation item and page. The final solution should allow internal teams to use the analytics dashboards UI under their own navigation space, with their own dashboards. All dashboards should still be retrievable through the dashboards GraphQL API in case we need/our customers need the full list. ### Goals 1. Develop a consistent interface pattern for dashboard implementations through the UI. - Separate the dashboards UI from the analytics space so it can be used in other product areas. - Ideally, this should be modular enough for teams to use parts of the dashboards UI if they're not ready for the full customization experience. - Update the analytics space as required to support the separation of the dashboards UI. - Resolve outstanding technical debt due to product shifts to improve developer experience and onboarding efficiency. - Ensure all dashboards remain accessible through GraphQL regardless of location. 2. Document the implementation pattern for other teams who wish to adopt the framework. - Establish guidelines for maintaining consistency while allowing for section-specific customizations. - Create a migration path for teams who might want to move their dashboards to the dashboards UI in the future.