Connection methods and technical boundaries
Screen 6.3 — allowlist endpoints, methods, authentication patterns and network rules.
PEEK Platform Administrator
/peek/customers/tenant-a/6-3Method policy constrains transport, authentication and network reach. The runtime enforces the reviewed method and destination boundary independent of any UI control. Core file intake is a separate validated path.
6.3 · Connection Methods & Technical Boundaries
Constrain transport, authentication and network reach. Open it at /peek/customers/tenant-a/6-3 (any tenant ID you can access works in place of tenant-a). The primary action is Publish method policy, which requires connection_method.publish.
How 6.3 works
1. Allowlist source endpoints, methods, authentication patterns and network constraints
Screen 6.3 contract
- Fields shown
- API methods, approved endpoints, auth types, network rules
- Primary action
- Publish method policy
- Required capability
connection_method.publish- Validation
- Reject direct customer DB connections, arbitrary URL forwarding and unreviewed redirect destinations. Core file intake is a separate validated path.
- Successful outcome
- Runtime enforces the reviewed method and destination boundary independent of UI controls.
- Screen states
- Loading; empty; ready; restricted; stale; error; review pending
- Audit event
admin.screen.6.3.action(acceptance testAT-UI-6.3)- Requirements
- R02, R06, R11, R12, R28, R39, SYS02, SYS04, SYS06, SYS10, SYS11, SYS20, SYS23, UI-6.3
Related guides
Connection governance and connector catalog
Screens 6.1 and 6.2 — review allowed source profiles per tenant and publish approved connector types and conditions.
Connector changes and connection oversight
Screens 6.7 and 6.8 — review custom API requests and connector revisions; monitor health and contain affected capabilities.