Docs/Data & connections

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.

PEEK Platform Administrator

/peek/customers/tenant-a/6-5

Live walkthrough · Delegated connection administration and setup preview

Delegated connection administration and setup preview — /peek/customers/tenant-a/6-6 — /peek/customers/tenant-a/6-6

Agency connection administrators manage live setup only within their assigned source and operation scope. Test, configure and rotate capabilities never confer user-role or SI administration, and connection tests return sanitized health metadata — never business records.

The setup guidance preview (6.6) shows allowed connectors, setup steps and policy explanation drawers with mock values. It has no secret entry, real connectivity test or arbitrary endpoint input, and dispatches no network request.

6.5 · Delegated Connection Administration

Define connection admin capabilities and limits. Open it at /peek/customers/tenant-a/6-5 (any tenant ID you can access works in place of tenant-a). The primary action is Publish delegation profile, which requires connection_delegation.publish.

How 6.5 works

1. Define agency connection-admin operations, scope, custodians and delegation ceilings

Screen 6.5 contract

Fields shown: Role, scope, supported actions, custodian, delegation ceiling
Primary action: Publish delegation profile
Required capability: connection_delegation.publish
Validation: Test, configure and rotate capabilities do not confer user-role or SI administration; test results are sanitized.
Successful outcome: Agency administrators manage live setup only within assigned source and operation scope.
Screen states: Loading; empty; ready; restricted; stale; error; review pending
Audit event: admin.screen.6.5.action (acceptance test AT-UI-6.5)
Requirements: R02, R05, R06, R11, R14, R28, R29, SYS02, SYS04, SYS06, SYS10, SYS11, SYS20, SYS23, UI-6.5

Boundary — Connection administration never permits user-role elevation or unrestricted data browsing.

Rejected even if the browser allows it — Source admin uses a connection test to retrieve protected business records; deny content and return safe health metadata.

6.6 · Customer Setup Guidance Preview

Preview the permitted setup options an agency will see. Open it at /peek/customers/tenant-a/6-6 (any tenant ID you can access works in place of tenant-a). The primary action is Preview setup guidance, which requires preview.use.

How 6.6 works

1. Preview allowed connector options, setup steps and policy explanation drawers using mock values

Screen 6.6 contract

Fields shown: Allowed connector, setup steps, explanation tags, required roles
Primary action: Preview setup guidance
Required capability: preview.use
Validation: No secret entry, real connectivity test or arbitrary endpoint input in the PEEK preview.
Successful outcome: Agency-facing guidance accurately explains which administrator can complete each live step.
Screen states: Loading; empty; ready; restricted; stale; error; review pending
Audit event: admin.screen.6.6.action (acceptance test AT-UI-6.6)
Requirements: R02, R06, R11, R18, R28, SYS02, SYS04, SYS06, SYS10, SYS11, SYS20, SYS23, SYS12, UI-6.6

Boundary — No credential entry, connection test or live source call from this preview.

Rejected even if the browser allows it — Try a production API call from preview; ensure no network request is dispatched.

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.

Synthetic previews

How the customer-facing previews in Groups 4, 6 and 7 work and what they can never do.