Skip to content

CAP-PFM-INT-002Explore the integrations available to a workspace

Markdown

CAP-PFM-INT-002

Explore the integrations available to a workspace

Markdown
  • DocumentDraft
  • Product intentProposed
  • ImplementationObserved

KindCapabilityProduct areaPlatformModuleIntegration access, customer extensions and shared workflow configurationRevision1

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 workspace finds precisely the integrations offered to it.Provider details explain supported jobs, requested access and available releases.
Surfaces
consoleapi
Intent sources
services-platform:docs/milestones/INTG-M1-find-install-connect.md#D3services-platform:docs/milestones/INTG-M1-find-install-connect.md#D4services-platform:docs/milestones/INTG-M1-find-install-connect.plan.md#INTG-M1-S01services-platform:docs/milestones/INTG-M1-find-install-connect.plan.md#INTG-M1-S02services-platform:docs/milestones/INTG-M1-find-install-connect.plan.md#A1

Controls

31 controls apply, from the corpus control catalogue.

TC-AVL-001 TC-AVL-005 TC-AZ-001 TC-AZ-002 TC-AZ-003 TC-AZ-004 TC-AZ-005 TC-CRY-001 TC-CRY-002 TC-CRY-003 TC-CRY-004 TC-DAT-001 TC-DAT-002 TC-DAT-003 TC-IAM-003 TC-LOG-001 TC-LOG-004 TC-LOG-005 TC-MON-001 TC-PI-001 TC-PI-005 TC-SEC-001 TC-SEC-002 TC-SEC-003 TC-SEC-004 TC-TEN-001 TC-TEN-002 TC-TEN-003 TC-VEN-001 TC-VEN-002 TC-VEN-003

Permissions

KeyChecked atScope
platform.integrations.readapitenant
platform.integrations.readconsoletenant

Business Rules

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

IdRuleKindEnforced atProvenance
01must prove
Proposed
The workspace catalogue includes active integrations with a published current release only where public availability, a restricted grant or Rhythm staff access permits them.
policyservicetest
02must prove
Proposed
An integration hidden from the workspace is absent from its catalogue and returns not found at its direct address.
policyapi, servicetest
03must prove
Proposed
Provider detail presents the current release, capability contracts and feature meanings, requested access, and published or deprecated releases with their notes.
policyapi, consoletest
services-platform:modules/integrations/tests/integration/services/catalog/catalog.integration.spec.js#answers the contracts the version implements, with their schemas and feature meanings
04
Proposed
Catalogue results support category and current-capability filters and paginate in integration-key order.
policyapi, servicetest
05must prove
Proposed
An availability reduction hides the catalogue offer while preserving reads of the workspace’s existing installation and connections.
policyservicetest
services-platform:modules/integrations/tests/integration/services/installations/narrowed-availability.integration.spec.js#stays readable to the tenant that holds it: the installation, the connection and their lists answer, and the catalog entry stays hidden
06must prove
Proposed
Integration readers can inspect Library records without secrets or change controls; callers without integration rights see access denied and are refused by protected routes.
permissionapi, consoletest
react-console:lib/integrations/access.test.ts#shows a reader every screen, with no change control and no secret
07
Proposed
The Library is reached through Configuration, earlier integration addresses resolve to it, and unknown Library addresses show the console’s not-found page.
policyconsoletest

Scenarios

IdGivenWhenThenProvenance
01The test integration is the only publicly published offer.The administrator searches for Dummy in the catalogue.A single offer opens to the provider’s capabilities and requested access.test
02An integration is offered only to a different customer.The administrator opens its direct address.The catalogue detail returns not found.test

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.