Skip to main content

Dashboard user guide

Task-oriented navigation, filters, freshness, and safe actions in the CodeGraph dashboard. See the examples and checks before applying it.

User Guides

The dashboard turns project, portfolio, security, release, and governance signals into task-oriented workspaces. Use it to locate a problem and its evidence; use the owning CLI, API, or governed workflow for deeper remediation.

Sign in and choose scope

Open /dashboard/login. Every other route is inside the frontend ProtectedRoute and requires an authenticated session. Authentication alone does not grant a project or administrative action: the API still enforces the current user, project, group, and operation scope. A hidden or disabled action does not grant another user permission to run it.

After sign-in, start at /dashboard. Apply the project, group, organization, team, environment, criticality, language, domain, service type, risk, and period filters that are relevant to the decision. Save a view when the same filtered scope will be compared or exported again.

Current workspaces

Current workspaces
Route Use it for
/dashboard Portfolio overview and filtered health.
/dashboard/red-zone Prioritized risks and drill-down.
/dashboard/repositories Registered repositories and synchronization.
/dashboard/compare Cross-project comparison.
/dashboard/projects Project catalog.
/dashboard/projects/:name One project: audit, compliance, release, delivery, SCA, trends, memory, sessions, and documentation tabs.
/dashboard/compliance Compliance evidence and gaps.
/dashboard/cross-repo Cross-repository analysis.
/dashboard/gitverse GitVerse integration status and actions.
/dashboard/sca Dependency inventory and vulnerability posture.
/dashboard/snapshots Immutable history, manual snapshots, comparison, and export.
/dashboard/notifications Subscriptions, delivery status, and notification catalog.
/dashboard/ai-finops AI usage, cost, and efficiency evidence.
/dashboard/security Security context and saved security views.
/dashboard/digital-employees Digital employee state and governed work.
/dashboard/release-control Release-control status and evidence.
/dashboard/onboarding-research Governed onboarding research.
/dashboard/accounts User and service-account administration.
/dashboard/service-accounts Compatibility redirect to /dashboard/accounts?mode=service.

Read freshness before the value

Dashboard cards expose evidence currency independently from whether data is present:

  • current — evidence is at least as new as its basis;
  • stale — the basis is newer or not coherent with the surface;
  • missing — required surface evidence is absent;
  • updating — a refresh job is queued or running;
  • failed — the latest refresh failed;
  • unknown — the available timestamps or basis do not establish currency.

The response also separates backend mode, synchronization status, data presence, and action availability. If refresh_required is true, use the displayed recommended action only when refresh_supported is true. An old value remaining visible during updating is an intermediate display; use the value after the update completes.

Complete common tasks

Find why a project is risky

  1. Open /dashboard/red-zone and keep the active filters visible.
  2. Open the project at /dashboard/projects/:name.
  3. Compare the health breakdown with compliance, release, SCA, and evidence freshness.
  4. Follow the evidence reference to its owning workflow; do not close a finding from the summary card alone.

Compare a stable period

  1. Save the exact filtered portfolio view.
  2. Open /dashboard/compare for projects or /dashboard/snapshots for immutable before/after evidence.
  3. Use the same saved view, baseline period, and comparison period in an export.
  4. Record the evidence revision with the result.

Configure notifications

  1. Open /dashboard/notifications.
  2. Choose a supported scope: portfolio, project, or saved view.
  3. Select events, severity, channel, and delivery mode.
  4. Confirm a live delivery event. A test send proves only the test path.

Sources of truth

  • frontend/src/App.tsx — current route map.
  • frontend/src/components/auth/ProtectedRoute.tsx — authentication boundary.
  • src/api/services/dashboard/surface_state/surface_freshness.py — freshness states and action metadata.
  • src/api/routers/dashboard_core/ and src/api/routers/dashboard_domains/ — API scope and actions.

For score interpretation, use Dashboard score methodology. Operators should use Dashboard operations.

Report a documentation issue