Skip to main content

Dashboard user guide

Find project risks in the CodeGraph dashboard, check evidence freshness, and compare history. Learn the navigation and limits of available actions.

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 on your CodeGraph deployment. You need an issued account and access to that deployment’s API. After sign-in, select a project or group you can access. The API checks the user’s permissions for the selected scope and operation. Account administration requires the admin role.

After sign-in, open /dashboard. Search narrows the project list by name, organization, team and other attributes. Select a period; the default is the live state. The toolbar’s advanced filters select language and risk level. Open the reference panel to access organization, team, environment, criticality, domain and service-type filters.

A saved view stores the panel filters, baseline period, projects selected for comparison and default export format. The search field narrows the current project list. To reuse a specific set of projects, select them in the list before saving.

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/projects/sections/:documentFile Legacy redirect to the documentation tab of the codegraph project. It removes .md and the _ru or _en suffix from the document name; invalid names redirect to the project catalog.
/dashboard/compliance Compliance evidence and gaps.
/dashboard/cross-repo Cross-repository analysis.
/dashboard/gitverse GitVerse integration status and actions, when enabled in the frontend bundle.
/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, when enabled in the frontend bundle.
/dashboard/onboarding-research Governed onboarding research.
/dashboard/accounts User and service-account administration; requires the admin role.
/dashboard/service-accounts Compatibility redirect to /dashboard/accounts?mode=service; requires the admin role.

GitVerse and release control are disabled by default in the frontend bundle. A disabled route redirects to the portfolio overview. To use these workspaces, an operator enables the routes and configures the corresponding API integrations.

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 and action_availability is available. 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. Open the linked evidence, verify the cause of the risk and implement the correction in the owning workflow. Save the verification result with the finding.

Save a working view

  1. On /dashboard, set the filters and select the projects in the list.
  2. Open the screen’s reference panel to reveal the Saved Views section.
  3. Enter a name that identifies the scope, such as “Prod Platform / 90d”. Choose a default export format: JSON or Markdown.
  4. Select “Save current view”. Wait for the confirmation and the new entry in the list.
  5. Select “Open” on the saved view. Check the restored filters, period and selected projects before comparing or exporting.

Compare a stable period

  1. To compare projects, select 2–10 projects in the portfolio and open /dashboard/compare.
  2. To compare history, choose a period instead of the live state. Open the reference panel and find the portfolio history section. Select a baseline period: 30, 90 or 180 days, or one year. Save a view with these settings.
  3. For immutable before/after results, open /dashboard/snapshots. Follow the snapshot guide to select snapshots and inspect their analysis basis.
  4. Open the “…” menu at the top of the portfolio and select “Export JSON” or “Export MD”. Use the same saved view and periods. Record the evidence revision with the result.

Configure notifications

  1. Open /dashboard/notifications and select the “Subscriptions” tab, then “Setup”.
  2. Choose a channel. “CodeGraph inbox” delivers events within the dashboard. For Telegram, Slack, email or webhook delivery, ask the operator to configure the channel and its recipient.
  3. Select the scope: portfolio, project or saved view. For a project scope, choose the project; for a saved-view scope, choose the saved view.
  4. Open “Events” from the “Subscriptions” tab menu. Select events by their title and description, such as “Risk level changed” or “Release gate failure”. Return to “Setup” and set the minimum severity and delivery mode: immediate or daily digest. Select “Create subscription” and check the new entry in the list.
  5. When a selected event occurs in the chosen scope, open “Inbox” and inspect its message and delivery status. Use “Delivery” to inspect pending deliveries and errors.

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

Report a documentation issue