Console

The BroomVA Console at broomva.tech/console is the administration dashboard for managing your organizations, monitoring usage, and configuring platform services. It is available on the Pro tier and above.

Overview

The console provides a centralized view of your organization's activity:

• Usage dashboard -- real-time credit consumption, model usage breakdown, and projected burn rate
• Member management -- invite and manage team members with role-based access
• API keys -- create and rotate API keys for programmatic access
• Billing -- view invoices, update payment methods, and manage your subscription

Navigation

The console uses a sidebar navigation pattern (shadcn sidebar-07) separate from the chat interface. The sidebar sections are:

Usage analytics

The usage dashboard shows credit consumption across multiple dimensions:

• By model -- which models are consuming the most credits, with cost-per-request averages
• By member -- per-user consumption within the organization
• By time -- daily, weekly, and monthly consumption trends with interactive charts
• Projected runway -- based on current burn rate, how many days until credits are exhausted

Usage data is computed from the @broomva/billing package's aggregation engine. Every API call records a UsageEventRecord with:

interface UsageEventRecord {
  id: string;
  organizationId: string | null;
  userId: string;
  type: string;              // e.g., "chat", "api", "agent"
  resource: string | null;   // e.g., model ID
  inputTokens: number | null;
  outputTokens: number | null;
  costCents: number;
  chatId: string | null;
  createdAt: Date;
}

These events are aggregated into UsageSummary objects with per-type and per-resource breakdowns. The dashboard queries these aggregations to render charts and tables.

Revenue metrics (Enterprise)

Enterprise organizations have access to revenue analytics powered by the RevenueMetrics interface:

• MRR -- Monthly Recurring Revenue in cents
• ARR -- Annualized Recurring Revenue
• ARPU -- Average Revenue Per User
• Churn rate -- as a decimal (e.g., 0.05 = 5%)
• Net new MRR -- expansion minus contraction for the period

Member roles

Organizations support a 4-tier role-based access control system. The hierarchy is: owner > admin > member > viewer. Higher roles inherit all permissions of lower roles.

The RBAC system is implemented in the @broomva/conformance package. Every API endpoint that requires authorization calls verifyRbac() with the user's ID, organization ID, and the minimum required role. If the user's actual role is at least as high as the required role in the hierarchy, the check passes.

Invitations are sent by email. When the invited user signs up or signs in, they are automatically added to the organization with the assigned role.

API keys

API keys provide programmatic access to the platform API without requiring a user session. Each key:

• Is scoped to a single organization
• Has a configurable expiration date (or no expiration)
• Can be revoked at any time from the console
• Shows its last-used timestamp for auditing
• Is recorded in the audit log when created or revoked

API keys use the same authentication format as user tokens -- include them as a Bearer token in the Authorization header. The key encodes the organization ID so the API can resolve the correct billing and permission context.

Audit log

The console maintains a chronological audit log of all administrative actions. Each entry records:

Audit logs are queryable by actor, action, resource, and date range. Admins and owners can export logs as CSV or JSONL for compliance purposes.

Settings

Organization settings include:

• Profile -- name, slug, description, and avatar
• Default model -- the model used when no specific model is requested
• Memory scope -- whether organization-level memories are shared across members or kept per-user
• Webhook URLs -- endpoints for event notifications (usage alerts, member changes)
• MCP servers -- organization-wide MCP tool connections