Skip to main content
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

JobDashboard areaUse it for
Monitor runtime behaviorOverview, EventsConfirm traffic is protected and investigate decisions.
Configure enforcementPolicies, Tool exposureTune request blocking and request-time tool filtering.
Manage credentialsAPI KeysCreate runtime keys and attach policies.
Administer the orgSettingsManage teammates, roles, and invites.

​
First Integration Workflow

After wiring a provider wrapper:
  1. Create or choose a policy in Policies.
  2. Create an API key and attach that policy in API Keys.
  3. Put the key in your app as AVERTA_API_KEY.
  4. Run one guarded provider call.
  5. Open 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

Events

Filter and investigate runtime decisions across checkpoints, providers, and API keys.

Policies

Create reusable policies and manage live request enforcement controls.

Tool exposure

Configure request-time tool filtering and review discovered tools.

API Keys

Create runtime credentials and attach policies to them.

Settings

Manage teammates, invites, and organization-level administration.