Skip to content

CAP-PFM-OPS-016Explain application availability to a customer administrator

Markdown

CAP-PFM-OPS-016

Explain application availability to a customer administrator

Markdown
  • DocumentDraft
  • Product intentConfirmed
  • ImplementationObserved

KindCapabilityProduct areaPlatformModuleOperational RecordsRevision1

Read atservices-platform ad3f6a65react-console baf6dae3

The Formal Contract

The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.

Outcomes
The customer can understand workspace application standing.Internal reasons and staff attribution remain within the staff view.
Surfaces
consoleapi
Preconditions
The administrator holds application-read authority for the workspace.
Postconditions
Customer application inspection leaves licensing and operational records unchanged.
Constraints
The workspace route serves the customer read while licensing owns its resolution and response mapping.
Intent sources
services-platform:docs/proposals/application-access-and-entitlements.md#6.4 Console integration (item 6, the tenant Applications page; accepted 2026-10-15)

Controls

21 controls apply, from the corpus control catalogue.

TC-AVL-001 TC-AZ-001 TC-AZ-002 TC-AZ-003 TC-AZ-004 TC-DAT-001 TC-DAT-003 TC-LOG-004 TC-LOG-005 TC-MON-001 TC-PI-001 TC-PI-005 TC-PRV-001 TC-PRV-002 TC-TEN-001 TC-TEN-002 TC-TEN-003 TC-TEN-004 TC-VEN-001 TC-VEN-002 TC-VEN-003

Permissions

KeyChecked atScope
platform.tenant-applications.readapitenant

Business Rules

6 rules, 3 to be proved before approval. A rule's product intent is derived from its origin: 6 confirmed by a product decision, the rest inheriting this capability's confirmed.

IdRuleKindEnforced atProvenance
01must prove
Confirmed
Application-read authority exposes the workspace’s application names, licence and grace dates, operational states and availability.
permissionapitest
services-platform:modules/licensing/tests/e2e/licensing.e2e.spec.js#answers each application with its key, name, licence state and dates, operation state and availability
02must prove
Confirmed
Customer application responses omit override decisions, personal attribution and commercial source details, simplify withholds to not licensed and hide suspension explanations.
policyapitest
services-platform:modules/licensing/tests/e2e/licensing.e2e.spec.js#says a withheld application is simply not licensed, never that Rhythm withheld it
03must prove
Confirmed
Another customer’s application read returns not found, while a caller missing application-read authority is refused.
permissionapitest
services-platform:modules/licensing/tests/e2e/licensing.e2e.spec.js#answers 404, not 403, to an administrator of another customer holding the same key
04
Confirmed
The application read remains available for a disabled workspace so its administrator can inspect its standing.
policyapidocumented
05
Confirmed
Configuration starts with Applications, presenting the available applications, understandable unavailability explanations and links to applicable settings.
policyconsoletest
react-console:e2e/mock/application-access.mock.spec.ts#the Applications page says which applications there are and why one cannot be used
06
Confirmed
Customer and staff application pages use shared readable state terminology.
policyconsoletest
react-console:e2e/dev/hq-licensing.dev.spec.ts#the tenant's own administrator reads Configuration › Applications with the same words

Scenarios

IdGivenWhenThenProvenance
01An application has an effective withhold carrying an internal explanation.The customer administrator reads Applications.The application is shown as not licensed without exposing the internal decision or author.inferred
services-platform:modules/licensing/tests/e2e/licensing.e2e.spec.js#says a withheld application is simply not licensed, never that Rhythm withheld it

The Markdown files under specs/ in rhythmsoftware/rhythm-v2-docs are the canonical source of truth. This reader is a generated, read-only projection of them.