> ## Documentation Index
> Fetch the complete documentation index at: https://docs.averta.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Dashboard overview

> Use the Averta dashboard to monitor decisions, tune policies, manage keys, and administer your organization.

The dashboard is Averta's control plane. Your application still sends runtime traffic through the SDK wrappers or the raw decision API; the dashboard is where you inspect that traffic and configure enforcement.

## Main Jobs

| Job                      | Dashboard area          | Use it for                                              |
| ------------------------ | ----------------------- | ------------------------------------------------------- |
| Monitor runtime behavior | Overview, Events        | Confirm traffic is protected and investigate decisions. |
| Configure enforcement    | Policies, Tool exposure | Tune request blocking and request-time tool filtering.  |
| Manage credentials       | API Keys                | Create runtime keys and attach policies.                |
| Administer the org       | Settings                | Manage teammates, roles, and invites.                   |

## First Integration Workflow

After wiring a provider wrapper:

1. Create or choose a policy in [Policies](/dashboard/policies).
2. Create an API key and attach that policy in [API Keys](/dashboard/api-keys).
3. Put the key in your app as `AVERTA_API_KEY`.
4. Run one guarded provider call.
5. Open [Events](/dashboard/events) and confirm you see a request event.
6. Add `requestContext` in code if the event is hard to correlate.

If you cannot find an event, do not start tuning policy yet. First prove the integration is sending runtime decisions.

## Daily Operating Loop

For most teams, the dashboard loop is simple:

1. Watch recent decisions in Overview.
2. Investigate blocks, tool restrictions, and unexpected allows in Events.
3. Tune request thresholds or tool exposure rules in Policies.
4. Confirm the right policy is attached to the right key.
5. Rotate or delete stale keys when integrations change.

## Page Map

<CardGroup cols={2}>
  <Card title="Events" icon="activity" href="/dashboard/events">
    Filter and investigate runtime decisions across checkpoints, providers, and API keys.
  </Card>

  <Card title="Policies" icon="shield-check" href="/dashboard/policies">
    Create reusable policies and manage live request enforcement controls.
  </Card>

  <Card title="Tool exposure" icon="toolbox" href="/dashboard/tool-exposure-policy">
    Configure request-time tool filtering and review discovered tools.
  </Card>

  <Card title="API Keys" icon="key" href="/dashboard/api-keys">
    Create runtime credentials and attach policies to them.
  </Card>

  <Card title="Settings" icon="gear" href="/dashboard/settings">
    Manage teammates, invites, and organization-level administration.
  </Card>
</CardGroup>