---
id: SCR-PFM-LLM-008
title: Organization AI Usage dashboard (planned)
route: '/console/{tenantId} Tools > Dashboards > AI Usage (planned; no route exists)'
surface: console
product_area: platform
module: llm
revision: 1
status: draft
design_intent: proposed
origin: >-
  D-2 (Andrew, 2026-10-18): a read-only page at Tools, Dashboards, AI Usage
  (services-platform:docs/proposals/llm-observability/11-decisions.md#Decision record); its milestone PLAT-M3
  is proposed.
implementation_evidence: not-implemented
inference: []
source_sha:
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
purpose: 'Provide the planned customer view of credits, reset dates, feature availability and request-history access.'
supports:
  - JNY-PFM-LLM-004
  - CAP-PFM-LLM-017
  - CAP-PFM-LLM-018
permission: platform.llm-usage.read (the organization administrator's key)
entry_from:
  - The existing navigation entry or its recorded planned placement.
  - The recorded allowance-notice entry.
exits_to:
  - The scoped query or directory and its history.
displays:
  - field: 'Proposed credit position, local reset and explanatory wording'
    source: getLlmUsageSummary
  - field: Proposed recent-period and feature usage history
    source: getLlmUsageSummary
  - field: 'Proposed feature labels, availability and restriction reasons'
    source: listLlmUsageFeatures
actions:
  - label: Open request history
    operation_id: 'none: opens the organization''s AI requests dataset in the query layer'
    permission: platform.llm-usage.read
    confirm: false
states:
  - planned loading state
  - planned read-error state
  - planned capacity warning and limited states
  - planned AI-disabled explanation
  - planned read-only presentation
validation:
  - BR-CAP-PFM-LLM-017-01
  - BR-CAP-PFM-LLM-017-03
  - BR-CAP-PFM-LLM-017-09
  - BR-CAP-PFM-LLM-018-06
patterns:
  - 'Standard layout dashboard page under Tools, Dashboards'
  - 'Credits and percentages only; no money, provider, model, grant or limit detail'
  - A v0 design is required because the screen does not exist yet
evidence:
  - >-
    services-platform at ad3f6a6: docs/milestones/PLAT-M3-ai-usage-organization-page.md;
    modules/llm/aws/api/llm-usage.routes.ts (getLlmUsageSummary, listLlmUsageFeatures);
    services/usage/organization-usage.ts, usage-sentences.ts.
  - 'react-console at baf6dae: components/console/nav-config.ts (Dashboards planned); no page exists.'
controls: [TC-AVL-001, TC-AVL-004, TC-AVL-005, TC-AZ-001, TC-AZ-002, TC-AZ-003, TC-AZ-004, TC-CRY-001, TC-CRY-002, TC-CRY-003, TC-CRY-004, TC-DAT-001, TC-DAT-002, TC-DAT-003, TC-IAM-001, TC-IAM-002, TC-IAM-004, TC-IAM-005, TC-LOG-001, TC-LOG-002, TC-LOG-003, TC-LOG-004, TC-LOG-005, TC-MON-001, TC-PI-001, TC-PI-002, TC-PI-003, TC-PI-004, TC-PI-005, TC-PRV-001, TC-PRV-002, TC-TEN-001, TC-TEN-002, TC-TEN-003, TC-VEN-001, TC-VEN-002, TC-VEN-003]
---

# Organization AI Usage dashboard (planned)

## What the Screen Is For

The recorded placement is a customer dashboard under Tools and Dashboards. Its service reads exist, but no console page or component implements this screen.

## What It Shows and Lets People Do

The proposed page presents credits used and remaining, percentage, status, local reset, recent periods and feature availability. It should link to scoped request reporting and withhold prices, provider details, grant records and internal limits. These requirements remain prospective.

## States and Errors

Loading, read failure, warning, limited and AI-disabled presentation must be designed. The backend feature list currently ignores active exemptions, so it can contradict actual admission. Screen preparation must resolve that discrepancy.

## Patterns It Must Respect

Use the recorded dashboard placement and customer-facing units. A new implementation preview is required for this absent screen; observed component patterns cannot yet be claimed.