Status. Proposed design only. Nothing in this vault is DG client approval. No application, service or test has been executed; every scenario is Not executed. Fees and dates are open.
DG35 · Newsletter permission is separate and withdrawable
| Field | Value |
|---|---|
| Status | Not executed |
| Type | Manual DG service |
| Layer / kind | Manual · recipient rehearsal |
| Priority | — |
| Gates | S11 |
| Build step | Step-12-Manual-DG-Services-and-Scope-Guards |
| Decisions | Q23, Q14 |
Given
Guest, member, session attendee and optional public subscriber; one declines or later opts out.
When
Request newsletter-specific permission; prepare issue; apply opt-out before send and retry.
Then / oracle
Invite, attendance, membership and payment never silently subscribe. Send only to current approved recipients; no visible mailing list or private terms. Duplicate issue-recipient sends are prevented; reconcile ambiguous send before retry and recheck opt-out. Opt-out affects newsletter future use, not membership or necessary account controls. Any service-notice exception needs separate approved policy; no promotional correction bypass.
Evidence required
Recipient permission/suppression and final-check list; isolated examples, no real mail sent.
Decision dependency (verbatim)
Q23/Q14: audience, approved tool/contact basis and notices after opt-out; product subscription centre extra scope.
Source: TDD rev 1.3 (PDF); machine-readable in 10-Sources/tdd-bundle/. Back to Scenario-Index · Traceability-Matrix · integration dependencies in Dependency-and-Regression-Table.