Status. Proposed design only. Nothing in this vault is GGA client approval. The GGA client documents are supplied drafts: see GGA-Source-Digest. No application, service or test has been executed; every scenario is Not executed. Delivery fees and dates are open.

Q08 · DG metadata and support-content access

Field	Value
Status	Pending GGA decision (recorded in 1.3 as “Pending DG decision”)
1.3 to GGA disposition	Reframed
Responsible role to confirm (recommendation)	GGA privacy/product owner
Needed before	Before T27–T28, live data
Named owner	[ ]
Due date	[ ]
GGA approver / decision date / chosen rule	[ ]

What the GGA documents say

Operations see review queues and restricted workflows with a recorded reason for sensitive overrides and exports; the technical administrator has no routine browsing and exceptional access is logged; finance sees billing data only; no restricted data in analytics, logs, indexes, exports or social previews (pp. 3, 17).

Source class: client-supplied design proposal or proposed default unless stated; GGA acceptance is not recorded. See GGA-Requirement-Register.

Rule or question as proposed in 1.3 (kept as history)

Candidate: opaque record/event IDs, approved event/state labels and timestamps only; no bodies, terms, reasons or contacts. Company/participant IDs need approval. Any support access needs scope, authoriser, duration and audit policy.

Still open

The exact metadata allowlist, who authorises exceptional support access, its duration and audit, and whether operations may read pitch contents.

Scenarios that depend on this decision (1.3 IDs, unchanged)

T03, T10, T12, T17, T19, T27, T28, T34, T36, DG02, DG07, DG22, DG24, DG28. Their dispositions are set in work package R4.

Related

GL04-staged. Index: Decision-Index.

A suggested default is a recommendation, not an approval. Record any actual decision with: ID · chosen rule · amendment to architecture and acceptance · GGA approver · decision date · affected test IDs · implementation owner.