Customer is requesting the ability to define multiple dashboard "personas" in IDP, where the landing page layout, widgets, and data sources rendered are determined by the user's role or group assignment. Today, the IDP homepage/dashboard is a single shared layout for all users; the customer wants different developer populations to land on different, purpose-built views.

Customer Use Case

The customer has distinct developer groups with different tooling footprints and access needs. They want admin-defined dashboard templates assigned per persona, for example:

Dev Persona A: Lands on a dashboard showing Jira widgets, Datadog plugin cards, and other integrated tooling panels

Dev Persona B: Lands on a stripped-down dashboard showing only Jira — no other plugin cards or data sources visible

The intent is both UX (reduce noise, show developers only what's relevant to their workflow) and governance (avoid exposing widgets/data sources a given team doesn't use or shouldn't see).

Requested Capability

Admin-defined dashboard layouts/templates (widget selection, arrangement, data sources per layout)

Assignment of layouts to users via role, user group, or RBAC mapping

Users automatically land on their persona's dashboard at login — no manual configuration by the end user

(Nice to have) Per-persona theming/branding and the ability for users to make limited personal customizations on top of the assigned base layout

Current Behavior / Gap

No mechanism today to vary the IDP homepage layout or visible widgets by role/group. All users see the same landing page regardless of team or tooling footprint.

Business Impact

The customer views this as important for driving adoption across heterogeneous dev teams — a one-size-fits-all homepage surfaces irrelevant tooling for many developers and dilutes the portal's value as a daily landing page. Persona-scoped dashboards would also align with their internal governance model for tool visibility.

Ask for PM

Is persona/role-based dashboard layout on the roadmap? If so, rough timeline; if not, can this be evaluated for the homepage customization workstream?