Documentation
Workflows and Approvals
Define governed review paths for enrichment, QA, translation, and publication.
Best for: Catalog operations, QA leads, and compliance teamsLast updated: 2026-03-21
Guide overview
Approvals work best when they reflect real ownership boundaries. Build workflows around business risk, publication readiness, and the fastest safe handoff between teams.
Use simple status models with clear exit criteria for each approval stage.
Separate enrichment review from compliance review when different teams own those decisions.
Trigger publication only from approved states so channel errors do not bypass governance.
Track rejection reasons to reduce repeated catalog cleanup work.
Related docs and next steps
Need implementation support?
Use the docs as your rollout blueprint, then connect them to pricing, tools, and solution pages when you need a deeper implementation plan.