---
id: JNY-PFM-LLM-004
title: An administrator investigates an allowance warning
feature: FEAT-PFM-LLM-06
product_area: platform
module: llm
revision: 1
status: draft
product_intent: proposed
implementation_evidence: partially-observed
supersedes: []
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
actor: ACT-PFM-007
goal: 'Review remaining AI capacity, reset timing, feature availability and usage after receiving a warning.'
capabilities:
  - CAP-PFM-LLM-008
  - CAP-PFM-LLM-017
screens:
  - '/console/{tenantId}/queries'
steps:
  - 'n': 1
    surface: e-mail
    action: Read the allowance warning email.
    capability: CAP-PFM-LLM-008
    expected: 'The notice supplies usage, allowance, remaining credits and reset timing.'
    provenance: test
    source: >-
      services-platform:modules/llm/tests/e2e/allowance-warning.e2e.spec.js#writes the 80 % notice with what
      was used and what remains, in the words of the console
  - 'n': 2
    surface: getLlmUsageSummary
    action: Request the organization’s usage summary.
    capability: CAP-PFM-LLM-017
    expected: 'The service returns credit figures, status, history and usage by feature.'
    provenance: test
    source: >-
      services-platform:modules/llm/tests/e2e/llm-adjustments-and-organization.e2e.spec.js#answers the summary
      to the organization’s administrator
  - 'n': 3
    surface: listLlmUsageFeatures
    action: Request the feature availability list.
    capability: CAP-PFM-LLM-017
    expected: The result describes each feature and any restriction.
    provenance: test
    source: >-
      services-platform:modules/llm/tests/e2e/llm-adjustments-and-organization.e2e.spec.js#answers the
      features, available while the organization has credits
  - 'n': 4
    surface: '/console/{tenantId}/queries'
    action: Run the request-usage report by person.
    capability: CAP-PFM-LLM-017
    expected: The report contains organization-owned request figures without captured content.
    provenance: documented
    source: 'services-platform:docs/llm.md#Reporting'
alternates:
  - from_step: 3
    condition: Rhythm has disabled an AI feature.
    path: Its availability entry explains the restriction.
    outcome: The administrator knows that waiting for reset will not remove that restriction.
    provenance: test
    source: >-
      services-platform:modules/llm/tests/e2e/llm-adjustments-and-organization.e2e.spec.js#restricts the
      feature with the sentence when the organization turns it off
failures:
  - from_step: 2
    condition: Look for the planned AI Usage dashboard.
    path: The customer dashboard and navigation entry are absent.
    outcome: The summary is available through the service rather than that console page.
    provenance: documented
    source: >-
      services-platform:docs/milestones/PLAT-M3-ai-usage-organization-page.md#State found on 2026-10-19
      (re-inspected)
rules_in_play:
  - BR-CAP-PFM-LLM-008-04
  - BR-CAP-PFM-LLM-017-01
  - BR-CAP-PFM-LLM-017-02
  - BR-CAP-PFM-LLM-017-03
  - BR-CAP-PFM-LLM-017-04
  - BR-CAP-PFM-LLM-017-08
assertions:
  - id: AS-JNY-PFM-LLM-004-01
    statement: 'The summary omits money, provider, model, extra-capacity and limit fields.'
    provenance: test
    source: >-
      services-platform:modules/llm/tests/e2e/llm-adjustments-and-organization.e2e.spec.js#carries no key
      naming money, a provider, a model, an override or a limit on the summary
  - id: AS-JNY-PFM-LLM-004-02
    statement: A disabled feature is described as restricted with its explanation.
    provenance: test
    source: >-
      services-platform:modules/llm/tests/e2e/llm-adjustments-and-organization.e2e.spec.js#restricts the
      feature with the sentence when the organization turns it off
e2e_policy: optional
e2e_reason: >-
  The summary and availability services have automated evidence. The planned customer dashboard needs browser
  coverage when it is implemented.
evidence:
  - >-
    services-platform at ad3f6a6582843008ed0f5a17b131878d15829af1:
    docs/milestones/PLAT-M3-ai-usage-organization-page.md; docs/proposals/llm-observability/11-decisions.md
    (D-2, D-7); docs/llm.md (What an organization sees, Reporting);
    modules/llm/tests/e2e/llm-adjustments-and-organization.e2e.spec.js, allowance-warning.e2e.spec.js.
  - >-
    react-console at baf6dae382d6f41dce976c7f848667ccc37e076f: components/console/nav-config.ts (Dashboards
    planned); app/(console)/console/[tenantId]/queries/page.tsx.
proved_by: []
---

# An administrator investigates an allowance warning

## Story

An administrator receives a warning and wants to understand the organization’s AI usage. The journey combines notices, customer-facing usage information and request reporting. The services supply part of that experience, but the planned dashboard is absent. Its placement has a recorded decision; the complete journey remains proposed.