web
You’re offline. This is a read only version of the page.
close
  • Enable Native Content Approval Workflow in Dynamics 365 Commerce CMS

    Organizations using Microsoft Dynamics 365 Commerce Content Management System (CMS) require a structured and controlled content publishing process to ensure governance, compliance, and quality assurance.

    Currently, the CMS does not provide a built-in approval workflow. Content created or modified by one user can be published without a mandatory review or approval step, forcing organizations to manage approvals outside the system. This creates operational inefficiencies, increases the risk of errors, and weakens governance controls.

    We propose introducing a native approval workflow capability within D365 Commerce CMS with the following features:

    • Multi-step approval workflows (e.g., Creator → Reviewer → Publisher)
    • Ability to assign roles (e.g., Content Creator, Reviewer, Approver)
    • Mandatory approval gating before content can be published
    • Workflow status tracking (Draft, In Review, Approved, Rejected)
    • Audit trail and version history for compliance and traceability
    • Optional notifications/alerts for pending approvals
    • Configurable workflows to support different business needs

    Example Use Case

    • User A creates or updates content (Draft)
    • User B reviews and approves/rejects (In Review)
    • Only approved content can be published to the live site

    Business Impact

    • Improves content governance and compliance
    • Reduces dependency on manual/off-system processes
    • Minimizes risk of incorrect or unapproved content going live
    • Aligns CMS capabilities with enterprise content management standards

    This enhancement would significantly strengthen the CMS capabilities within Dynamics 365 Commerce and better support organizations operating in regulated or large-scale environments.


    Right Now:

    Capability Evolution (Landmarks)

    1. Current State – Role-Based Access

    • Users are assigned roles (e.g., content author, editor)
    • No enforced approval step before publishing
    • Publishing control depends on user permissions only