Docs/Data & connections

Connector changes and connection oversight

Screens 6.7 and 6.8 — review custom API requests and connector revisions; monitor health and contain affected capabilities.

PEEK Technical Reviewer · PEEK Incident Operator

/peek/customers/tenant-a/6-7

Live walkthrough · Connector changes and connection oversight

Connector changes and connection oversight — /peek/customers/tenant-a/6-8 — /peek/customers/tenant-a/6-8

New endpoints, scopes or secondary uses need both technical review and agency authorization; a connector update that adds an operation beyond its approved contract is blocked until reviewed and adopted. In oversight (6.8), suspending a connector stops new affected calls only — accepted evidence follows record and retention policy and unrelated manual work and other sources continue.

6.7 · Exception & Connector Change Review

Review custom API requests and connector revisions. Open it at /peek/customers/tenant-a/6-7 (any tenant ID you can access works in place of tenant-a). The primary action is Approve bounded connector change, which requires connector_change.review.

How 6.7 works

1. Review custom API request or connector revision with old/new operations, terms and dependency impacts

Screen 6.7 contract

Fields shown: Requested operations, endpoint review, rights, risk, dependencies
Primary action: Approve bounded connector change
Required capability: connector_change.review
Validation: New endpoint, scope or secondary use requires corresponding technical and agency authority; review cannot waive fixed prohibitions.
Successful outcome: Publish a bounded catalog version; agency explicitly adopts/configures it before use.
Screen states: Loading; empty; ready; restricted; stale; error; review pending
Audit event: admin.screen.6.7.action (acceptance test AT-UI-6.7)
Requirements: R02, R06, R11, R12, R13, R24, R28, SYS02, SYS04, SYS06, SYS10, SYS11, SYS20, SYS23, UI-6.7

Boundary — New endpoints require technical review and agency authorization before use.

Rejected even if the browser allows it — Connector update adds an operation beyond the approved contract; block it until reviewed and adopted.

6.8 · Connection Oversight & Intervention

Review sanitized connection health and containment. Open it at /peek/customers/tenant-a/6-8 (any tenant ID you can access works in place of tenant-a). The primary action is Suspend affected capability, which requires connection.restrict.

How 6.8 works

1. Review sanitized health, stale status and dependent jobs
2. Apply scoped containment with authority

Screen 6.8 contract

Fields shown: Health, failure class, incident, dependency impact, suspension
Primary action: Suspend affected capability
Required capability: connection.restrict
Validation: Source interruption affects only dependent work; no credential or record contents in incident metadata.
Successful outcome: New affected calls stop; accepted evidence follows current record/retention policy and unrelated manual work continues.
Screen states: Loading; empty; ready; restricted; stale; error; review pending
Audit event: admin.screen.6.8.action (acceptance test AT-UI-6.8)
Requirements: R02, R06, R11, R26, R28, SYS02, SYS04, SYS06, SYS10, SYS11, SYS20, SYS23, UI-6.8

Boundary — Show dependency impact with sanitized metadata. Source interruption does not erase accepted packages or stop unrelated manual work.

Rejected even if the browser allows it — Suspend one connector; verify that unrelated tenant sources and Core records remain governed and available.

Related guides

Connection methods and technical boundaries

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

Incidents, containment and recovery

Screens 8.5 and 8.6 — apply preauthorized containment immediately, then restore service only after current authority and technical checks.