> For the complete documentation index, see [llms.txt](https://docs.kyvvu.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kyvvu.com/platform/dashboard.md).

# Dashboard Guide

**What you'll learn:** How to navigate the Kyvvu dashboard, oversee agents, and manage policies.

***

## Overview

The Kyvvu dashboard is a web interface at [platform.kyvvu.com](https://platform.kyvvu.com) for overseeing agents, managing policies, triaging incidents, and generating reports.

## Navigation

The sidebar provides access to all sections:

| Section       | What it shows                                                                                               |
| ------------- | ----------------------------------------------------------------------------------------------------------- |
| **Dashboard** | Overview stats (agents, manifests, policies, incidents), recent incidents table, recent activity.           |
| **Agents**    | Agent list with risk, environment, last policy fetch. Expand for assigned manifests, resync, view policies. |
| **Manifests** | Connect GitHub repos, browse YAML manifest files, assign manifests to agents via checkbox modal.            |
| **Logs**      | Behavioral trace logs — searchable by agent, task ID, time range. Hash chain validation.                    |
| **Incidents** | Policy violations with severity, status, and agent details.                                                 |
| **Settings**  | Sub-tabs: API Keys, Platform Events, Reports, Organization, Members.                                        |

## Agent oversight

The **Agents** page lists all registered agents with:

* Agent key and ID
* Name and purpose
* Environment (development / staging / production)
* Risk classification (high / limited / minimal)
* Active/inactive status

Click an agent to see its details, associated policies, recent logs, and incidents.

## Policy management

Policies are created automatically when manifests are assigned to agents. To manage policies:

* **Manifests page**: Connect a repo, browse manifests, assign to agents
* **Agents page**: Expand an agent to see assigned manifests, view policies, update or remove assignments

## Log viewer

The **Logs** page displays the behavioral trace as a paginated list of tasks:

* The task list is loaded server-side (`GET /api/v1/logs/tasks`), one summary row per task with its agent, environment, step count, and status — 20 tasks per page. This scales to agents with hundreds of steps per task.
* Filter by agent or time range; the free-text task ID filter resolves a single task directly.
* Expand a task (or open its details) to lazy-load the full ordered sequence of steps — steps are fetched on demand, not up front.
* Each step shows its evaluation result (allow / warn / block) and the Behavior data.
* Hash chain validation: click "Validate" on a task to verify chain integrity.

## Authentication

Login at [platform.kyvvu.com](https://platform.kyvvu.com) with your email and password. JWT tokens expire after 24 hours.

***

## Next steps

* [Incident Management](/platform/incidents.md) — triage and resolve policy violations
* [Organizations & Access](/platform/organizations.md) — manage team members and permissions
* [Reports](/platform/reports.md) — generate compliance reports


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.kyvvu.com/platform/dashboard.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.