Decide campaign sub-object resource access explanation scope #50

Open
opened 2026-07-11 00:30:09 +02:00 by zemion · 0 comments
Owner

Decision needed

The platform resource-access explanation endpoint can now explain a campaign resource itself. We still need to decide which campaign sub-objects should become first-class explainable resources.

Candidate resource types:

  • campaign versions
  • recipient rows and recipient data entries
  • attachment rules and managed attachment bindings
  • send/review jobs and delivery outcomes
  • audit log entries and reports
  • template/data sections inside a campaign workspace

Acceptance criteria

  • Decide the initial supported campaign sub-object resource types.
  • Define stable resource identifiers for each accepted type.
  • Define which provenance sources can grant or constrain access for each type.
  • Document unsupported sub-objects explicitly so the current campaign-level explanation remains clear.

Context

This follows the resource-access explanation rollout for Files and Campaign. The initial implementation intentionally covers the campaign ownership/sharing object first and leaves finer-grained campaign objects behind this decision.

## Decision needed The platform resource-access explanation endpoint can now explain a `campaign` resource itself. We still need to decide which campaign sub-objects should become first-class explainable resources. Candidate resource types: - campaign versions - recipient rows and recipient data entries - attachment rules and managed attachment bindings - send/review jobs and delivery outcomes - audit log entries and reports - template/data sections inside a campaign workspace ## Acceptance criteria - Decide the initial supported campaign sub-object resource types. - Define stable resource identifiers for each accepted type. - Define which provenance sources can grant or constrain access for each type. - Document unsupported sub-objects explicitly so the current `campaign`-level explanation remains clear. ## Context This follows the resource-access explanation rollout for Files and Campaign. The initial implementation intentionally covers the campaign ownership/sharing object first and leaves finer-grained campaign objects behind this decision.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: add-ideas/govoplan-campaign#50
No description provided.