Multiple approvers for all marketing assets

Status: Idea Submitted

We require the implementation of a structured, multi-stage approval workflow within the system to govern the publication of all marketing assets (e.g., blogs, marketing emails, social media posts, case studies).

Functional Requirements

  1. Asset Creation Trigger

    • Upon creation of any draft marketing asset, the system should automatically initiate an approval workflow.
    • Applicable asset types include: blog posts, email campaigns, social media content, and case studies.
  2. Sequential Approval Logic

    • The workflow must enforce a two-tier, sequential approval process:
      • Stage 1 (Manager A Approval)
        • Manager A is automatically notified when a draft is ready for review.
        • Manager A must review the asset and provide an explicit approval action (e.g., checkbox, status change, or digital sign-off).
        • The workflow cannot proceed until Manager A approval is completed.
      • Stage 2 (Manager B Approval)
        • Upon completion of Stage 1, Manager B is notified.
        • Manager B performs a final review and provides a second explicit approval.
        • This acts as the final gate before publication.
  3. Approval Controls & Status Tracking

    • Each approval step must be auditable with:
      • Timestamp
      • Approver identity
      • Approval status (Approved / Rejected / Requires Revision)
    • The asset should maintain a status lifecycle (e.g., Draft → Pending Approval A → Pending Approval B → Approved → Published).
  4. Publishing Constraint

    • The system must enforce a hard dependency such that assets cannot be published or distributed until both approvals are complete. (Note: Admins should have the ability to skip an approval if needed)
    • Any rejection at any stage should revert the asset to draft or revision-required status.
  5. Notifications & Alerts

    • Automated notifications should be triggered at each stage:
      • Draft ready → Notify Manager A
      • Approval A completed → Notify Manager B
      • Final approval completed → Notify content owner / trigger publishing workflow
  6. Extensibility Consideration

    • The workflow should be configurable to support:
      • Additional approval levels (if needed in the future)
      • Role-based assignment (instead of hardcoding specific individuals)