Docs/Data & connections

Data access and permitted use

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

PEEK Platform Administrator

Live walkthrough · Data access and permitted use

Data access and permitted use — /peek/customers/tenant-a/6-4 — /peek/customers/tenant-a/6-4

The permitted-use profile defines record scopes and which secondary uses — export, SI processing, actions and onward handoff — are allowed, carrying source provenance and markings to every downstream use.

Note — Three things never grant record access on their own: a source connection, accepting a handoff package, and a persona assignment. Accepting a package that contains evidence the recipient cannot see is denied until authorized sharing exists.

6.4 · Data Access & Permitted Use

Separate source access from secondary use. Open it at /peek/customers/tenant-a/6-4 (any tenant ID you can access works in place of tenant-a). The primary action is Publish permitted-use profile, which requires data_use_policy.publish.

How 6.4 works

1. Define record scopes, export, SI processing and onward-handoff uses with source provenance and markings

Screen 6.4 contract

Fields shown: Data scope, export, SI processing, action permissions
Primary action: Publish permitted-use profile
Required capability: data_use_policy.publish
Validation: Source connection, package acceptance and persona assignment each leave record grants separate.
Successful outcome: All downstream uses receive explicit permitted-use constraints and current access evaluation.
Screen states: Loading; empty; ready; restricted; stale; error; review pending
Audit event: admin.screen.6.4.action (acceptance test AT-UI-6.4)
Requirements: R02, R06, R11, R23, R26, R28, R35, R39, R40, R42, SYS02, SYS04, SYS06, SYS10, SYS11, SYS20, SYS23, UI-6.4

Boundary — Apply provenance, markings, source-use rights and current record access to every handoff. Acceptance is not a new access grant.

Rejected even if the browser allows it — Accept a package containing recipient-inaccessible evidence; deny protected preview and acceptance until authorized sharing exists.

Related guides

Handoff and synchronization governance

Screen 3.11 — publish package submission, human acceptance, immutable accepted versions and changed-input review rules.

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.