PKPEEK Docs
Docs/Data & connections

Connection governance and connector catalog

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

PEEK Platform Administrator · PEEK Support Operator

/peek/customers/tenant-a/6-1
Live walkthrough · Connection governance and connector catalog
/peek/customers/tenant-a/6-1
/peek/customers/tenant-a/6-2

The PEEK center governs connection rules; it never connects agency data. 6.1 shows allowed source profiles, the agency’s configuration status and operation eligibility. 6.2 releases connector catalog entries (catalog type connector) after reviewing the source interface, license and use rights, supported operations and permitted methods.

Heads up — Connection health never implies record access: a healthy source plus a missing user record grant still denies the user’s query. G2x stays conditional until interface availability and integration rights are verified; an unverified subscription is never permission for automated export or SI processing.

6.1 · Connection Governance Overview

Review allowed source capability and agency setup status. Open it at /peek/customers/tenant-a/6-1 (any tenant ID you can access works in place of tenant-a). The primary action is Open source governance, which requires connection_governance.read.

How 6.1 works

  1. 1. Show allowed source profiles, agency configuration status and operation eligibility

Screen 6.1 contract

Fields shown
Connector policy, method, permitted operations, dependencies
Primary action
Open source governance
Required capability
connection_governance.read
Validation
Connection health cannot imply source-record access or processing rights. No real setup is offered here.
Successful outcome
Open governance details or synthetic agency setup guidance with current safe status.
Screen states
Loading; empty; ready; restricted; stale; error; review pending
Audit event
admin.screen.6.1.action (acceptance test AT-UI-6.1)
Requirements
R02, R06, R11, R28, SYS02, SYS04, SYS06, SYS10, SYS11, SYS20, SYS23, UI-6.1
Boundary — This center governs connection rules rather than connecting agency data.
Rejected even if the browser allows it — Healthy source connection plus missing user record grant must still deny the user's query.

6.2 · Approved Connector Catalog

Publish permitted connector types and conditions. Open it at /peek/customers/tenant-a/6-2 (any tenant ID you can access works in place of tenant-a). The primary action is Release connector capability, which requires connector_catalog.publish.

How 6.2 works

  1. 1. Review source interface, license/use rights, supported operations and permitted methods

  2. 2. Release a catalog entry

Screen 6.2 contract

Fields shown
Source, interface verification, rights, operations, status
Primary action
Release connector capability
Required capability
connector_catalog.publish
Validation
G2x remains conditional until interface and rights evidence is recorded. Each operation has a defined schema and purpose.
Successful outcome
Agency can select only catalog entries eligible for its purchased and authorized scope.
Screen states
Loading; empty; ready; restricted; stale; error; review pending
Audit event
admin.screen.6.2.action (acceptance test AT-UI-6.2)
Requirements
R02, R06, R11, R12, R13, R26, R28, R41, SYS02, SYS04, SYS06, SYS10, SYS11, SYS20, SYS23, UI-6.2
Boundary — G2x remains conditional until interface availability and integration rights are verified.
Rejected even if the browser allows it — Mark an unverified subscription as permission for automated export or SI processing; reject publication.

Related guides

Connection methods and technical boundaries

Screen 6.3 — allowlist endpoints, methods, authentication patterns and network rules.

Data access and permitted use

Screen 6.4 — separate source access from secondary uses: export, SI processing, actions and onward handoff.

Delegated connection administration and setup preview

Screens 6.5 and 6.6 — define what agency connection admins can do, and preview the setup guidance agencies will see.