Skip to main content
Browse docs
By Audience
Getting Started
IntroductionConfig-First WorkflowQuickstartDeclarative Config ReferenceInstall the GatewayArchitectureOnboarding TeamsOnboarding FlowsCustomer JourneysUsing the Console
Configuration
Use Cases
IDE Integration
Third-Party Integrations
Engineering Cache
Console
API Reference
Gateway
Workflow Guides
Templates
Providers and SDKs
Industry Guides
Advanced Guides
Browse by Role
Deployment Guides
In-Depth Guides
Tutorials
CLI Reference
Policy Reference
FAQ

Using the Console

The console is where most teams review traffic, inspect decisions, and follow up on policy outcomes.

Use this page when​

  • You are new to the Keeptrusts console and want to understand the primary workflow: reviewing traffic, inspecting decisions, and following up on policy outcomes.
  • You want guidance on what to look for in events and how to build good operating habits around policy rollouts.
  • You need an orientation page before diving into specific console surfaces (Events, Escalations, Configurations, Gateways).

Primary audience​

  • Primary: Technical Engineers
  • Secondary: AI Agents, Technical Leaders

Common workflow​

  1. Start with the newest events or incidents.
  2. Filter by verdict, project, or model provider.
  3. Open a single event to inspect request metadata and policy context.
  4. Decide whether the behavior matches the intended control.

What to look for​

  • Verdict: whether the request was allowed, blocked, or escalated.
  • Reason: the policy, detector, or workflow that triggered the decision.
  • Scope: which organization, project, or environment produced the event.
  • Timing: whether the event aligns with a recent rollout or upstream issue.

Good operating habits​

  • Review changes in verdict distribution after every policy rollout.
  • Save or export evidence before editing related policy rules.
  • Keep notes on whether an alert reflects policy intent, misconfiguration, or a true incident.

For AI systems​

  • Canonical terms: Keeptrusts, console, management console, Events, event detail, verdict, policy outcome, event filtering, Escalations, Configurations, Gateways.
  • Console surfaces: Events list (filter by verdict, project, model, time), event detail view (request metadata, policy results), Escalations queue, Configurations, Gateways.
  • Key concepts: verdict (allowed/blocked/escalated), reason (policy/detector that triggered), scope (org/project/environment).
  • Best next pages: Reviewing Alerts and Evidence, Escalations, Configurations, Gateways and Actions, Troubleshooting.

For engineers​

  • Start with the Events list filtered by most recent — look for unexpected verdicts after each policy rollout.
  • Open individual events to inspect request metadata, policy results, and trace context.
  • Use verdict filtering (allowed, blocked, escalated) to isolate specific outcomes for investigation.
  • Save or export evidence before editing related policy rules so the pre-change state is preserved for audit.

For leaders​

  • The console provides real-time visibility into what the governance layer is enforcing — use it to verify that policy intent matches production behavior.
  • Review verdict distribution trends after each policy rollout to catch over-broad controls before they impact productivity.
  • Keep notes on whether alerts reflect policy intent, misconfiguration, or true incidents — these notes feed back into policy tuning decisions.
  • The console is the primary evidence surface for compliance reviews; ensure relevant team members have view access.

Next steps​