A single estate-wide dashboard is useful for leadership, but day to day each team wants to see only what they own. This guide explains how to shape Vibgrate Cloud into team-focused dashboards.
Overview
Team dashboards are built from the same pushed scans as everything else in Vibgrate Cloud. The difference is grouping: when repositories are named and mapped consistently, the dashboard can present each team the repositories and applications it is responsible for, with their DriftScores and trends.
Prerequisites
- Repositories pushing to a shared Vibgrate Cloud workspace.
- Consistent repository names (see Connect a Repository to Vibgrate Cloud).
Step-by-step
Ensure every team's repositories push under stable, recognizable names so they can be grouped:
vg scan --push --repository-name org/payments-api
Group related repos into applications so a team's view reflects the products it owns; see Map Repositories to Applications. With naming and grouping in place, each team gets a coherent slice of the dashboard at dash.vibgrate.com.
Keeping team views trustworthy
A team dashboard is only useful if it is current and complete. Automate pushes so coverage does not depend on individuals; see Push from CI Pipelines and Schedule Recurring Drift Reporting.
Access and visibility
Who can see and act on a team dashboard depends on workspace access and roles; see Access and Roles Overview.
Related
Set Up a Portfolio View and View Drift Trends on the Dashboard.