Operator Runbooks

Review usage, cost, and the audit log

Monitor AI spend against plans and read the platform audit trail.

These are the recurring oversight routines operators run from the Intelligence and Governance areas.

Review usage and cost

Open Command Center → Intelligence → Usage & cost (/admin/console/intelligence/usage).
Select the period (month) you want to review.
Scan the by-organization table: runs used vs. cap, tokens, estimated cost, and the cost-to-revenue ratio. Sort by cost or ratio to find outliers.
Check the near-cap watchlist for tenants approaching their run cap.

What to do with what you find:

  • A tenant near or at its cap that needs more headroom → change its plan via plans & lifecycle.
  • A high cost-to-revenue ratio → investigate the tenant's conversations under conversation oversight.

Read the audit log

Open Command Center → Governance → Audit log (/operator/audit).
Filter by action, organization, actor, or date range to narrow the trail.
Expand an entry's metadata to see action-specific detail (for example the reason on a support session).

The log captures support-session start/end, tenant tier changes, onboarding, and global-library deletions, with the acting operator recorded on every entry, including actions taken during a support session.

Pair this with the Knowledge Gaps radar: usage tells you what the platform costs, gaps tell you where the knowledge base is letting tenants down. Closing gaps in the Global Library improves answers for everyone.

On this page