Docs/SI services & Sigma

Provider approval and credential custody

Screens 4.2 and 4.10 — approve provider service profiles (environment, region, processing terms) and define credential custody and rotation.

PEEK Platform Administrator

/peek/customers/tenant-a/4-2

Live walkthrough · Provider approval and credential custody

Provider approval and credential custody — /peek/customers/tenant-a/4-10 — /peek/customers/tenant-a/4-10

PEEK approves which provider services and connection patterns an agency may use; the agency SI Admin performs the actual setup — including entering credentials — in the agency app. A consumer product brand alone is never sufficient; the allowed service environment, region and processing rights must be explicit.

No secrets in PEEK — There are no raw secret fields anywhere in PEEK. 4.10 sets custody requirements (custodian role, auth pattern, vault reference policy, rotation and revocation obligations); PEEK only sees lifecycle metadata. Requests to export or reveal a provider key are denied and logged. PEEK-managed custody needs an explicit bounded exception and named owner.

4.2 · Service & Connection Approval

Govern permitted provider services and connection patterns. Open it at /peek/customers/tenant-a/4-2 (any tenant ID you can access works in place of tenant-a). The primary action is Approve governance profile, which requires si_profile.publish.

How 4.2 works

1. Review provider/service environment, region, use case, processing terms and agency authority
2. Publish an allowed setup profile

Screen 4.2 contract

Fields shown: Provider, service environment, region, processing terms, agency approval
Primary action: Approve governance profile
Required capability: si_profile.publish
Validation: Consumer product brand alone is insufficient; allowed service environment and processing rights must be explicit.
Successful outcome: Agency SI Admin can configure only the approved profile in the agency app.
Screen states: Loading; empty; ready; restricted; stale; error; review pending
Audit event: admin.screen.4.2.action (acceptance test AT-UI-4.2)
Requirements: R02, R06, R11, R28, SYS02, SYS04, SYS06, SYS10, SYS11, SYS20, SYS23, UI-4.2

Boundary — Actual credentials and provider connection setup belong in the agency app.

Rejected even if the browser allows it — Attempt credential entry or live provider setup from the PEEK governance screen; it must be unavailable.

4.10 · SI Credential Governance & Ownership

Define custody and lifecycle requirements for provider credentials. Open it at /peek/customers/tenant-a/4-10 (any tenant ID you can access works in place of tenant-a). The primary action is Publish credential governance, which requires credential_policy.publish.

How 4.10 works

1. Define permitted credential custody, workload identity, vault metadata, rotation and revocation obligations

Screen 4.10 contract

Fields shown: Custodian role, auth pattern, vault reference policy, rotation status
Primary action: Publish credential governance
Required capability: credential_policy.publish
Validation: No raw secret fields or shared human credentials. PEEK-managed custody needs an explicit bounded exception and named owner.
Successful outcome: Agency setup receives custody requirements; PEEK sees only lifecycle metadata.
Screen states: Loading; empty; ready; restricted; stale; error; review pending
Audit event: admin.screen.4.10.action (acceptance test AT-UI-4.10)
Requirements: R02, R06, R11, R14, R28, SYS02, SYS04, SYS06, SYS10, SYS11, SYS20, SYS23, UI-4.10

Boundary — Secret values are entered only through the agency's authorized setup flow and never shown here.

Rejected even if the browser allows it — Request export or reveal of a provider key through this screen or its API; deny and log the attempt safely.

Related guides

Permitted uses, persona access and evidence

Screens 4.3, 4.4 and 4.9 — recommend SI by persona, constrain processing by data class and purpose, and trace use cases to agency approval evidence.

Connection governance and connector catalog

Screens 6.1 and 6.2 — review allowed source profiles per tenant and publish approved connector types and conditions.