[Feature] Add lists, segments, consent, suppression, and communication preferences #9

Open
opened 2026-07-13 00:53:46 +02:00 by zemion · 1 comment
Owner

Goal

Support reusable recipient governance beyond raw contacts.

Scope

  • static lists and dynamic segments
  • communication preferences
  • consent and legal-basis metadata
  • suppression/do-not-contact lists
  • consent-filtered recipient-source views

Acceptance Criteria

  • Recipient-source responses can include governance/provenance fields.
  • Campaigns can distinguish usable, suppressed, and policy-blocked contacts.
  • The first implementation can be local-only; sync integration can follow later.

See govoplan-addresses/docs/ADDRESS_MODULE_ARCHITECTURE.md and govoplan-addresses/docs/IMPLEMENTATION_PLAN.md.

## Goal Support reusable recipient governance beyond raw contacts. ## Scope - static lists and dynamic segments - communication preferences - consent and legal-basis metadata - suppression/do-not-contact lists - consent-filtered recipient-source views ## Acceptance Criteria - Recipient-source responses can include governance/provenance fields. - Campaigns can distinguish usable, suppressed, and policy-blocked contacts. - The first implementation can be local-only; sync integration can follow later. See `govoplan-addresses/docs/ADDRESS_MODULE_ARCHITECTURE.md` and `govoplan-addresses/docs/IMPLEMENTATION_PLAN.md`.
zemion added the
area/governance
type
feature
module/addresses
status
ready
priority
p2
labels 2026-07-13 00:53:46 +02:00
Author
Owner

Codex State: progress

Summary

  • Implemented classical address-list backend support in govoplan-addresses: address-list tables, API/service layer, permissions, manifest ownership, tests, and addresses.recipient_source exposure using addresses:address_list:<id> source IDs.
  • Documented the boundary: address lists remain address-domain groupings; operational mixed Verteiler/distribution lists move to govoplan-dist-lists.
  • Created focused govoplan-dist-lists issues for DTO/contract, local implementation, and UI/provider integrations.

Remaining In Addresses

  • Address-list management UI and campaign picker polish.
  • Dynamic address-domain segments.
  • Consent, suppression, communication preferences, and privacy policy behavior.
## Codex State: progress ### Summary - Implemented classical address-list backend support in `govoplan-addresses`: address-list tables, API/service layer, permissions, manifest ownership, tests, and `addresses.recipient_source` exposure using `addresses:address_list:<id>` source IDs. - Documented the boundary: address lists remain address-domain groupings; operational mixed `Verteiler`/distribution lists move to `govoplan-dist-lists`. - Created focused `govoplan-dist-lists` issues for DTO/contract, local implementation, and UI/provider integrations. ### Remaining In Addresses - Address-list management UI and campaign picker polish. - Dynamic address-domain segments. - Consent, suppression, communication preferences, and privacy policy behavior.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: add-ideas/govoplan-addresses#9
No description provided.