feat(campaigns): add portable campaign transfers
Module Package Release / publish-packages (push) Successful in 12s
Module Package Release / publish-packages (push) Successful in 12s
This commit is contained in:
@@ -73,6 +73,18 @@ has a remaining occurrence, including while it is paused; once the schedule
|
||||
finishes, already accepted Mail commands retain their own encrypted payload and
|
||||
evidence under Mail policy.
|
||||
|
||||
Campaign versions can also be exported as versioned portable JSON packages and
|
||||
imported as independently owned drafts. The privacy-safe export default is
|
||||
metadata plus template/configuration. Recipients, attachment rules, aggregate
|
||||
review state, and recipient-level delivery history are separate scopes with
|
||||
their existing fine-grained permissions. Packages include source provenance,
|
||||
scope/item/redaction manifests, and a SHA-256 integrity digest. They never
|
||||
contain attachment bytes, transport secrets, credential references,
|
||||
password-field values, local storage locators, shares, or ownership grants.
|
||||
Import previews schema and checksum compatibility plus every created/skipped
|
||||
domain. It clears deployment-bound Mail references and never replays locks,
|
||||
approvals, review decisions, jobs, attempts, or sent state.
|
||||
|
||||
Public campaign, version, job, and report responses expose business data and
|
||||
delivery evidence, but never process-local paths, storage-backend keys, or
|
||||
worker claim tokens. Operational troubleshooting uses the dedicated job
|
||||
|
||||
Reference in New Issue
Block a user