How to set up a CMS editorial approval workflow
PraismaHub team · November 19 2026 · 4 min read
A CMS approval workflow helps a team answer one question at a glance. Who needs to act before this article can go live? Use the same handoffs for every article so editors spend their time on the content.
Give each step one clear owner
Draft: The writer adds the article, excerpt, source links and any open questions.
In review: The editor checks accuracy, clarity and usefulness for the intended reader.
Approved: The approver signs off on the article and confirms the publishing window.
Published: The publisher verifies the public URL, links and mobile layout.
Apply the workflow in PraismaHub
Open the relevant collection in the CMS builder and enable Supports Workflow. Start with the default steps. The entry sidebar shows which transitions a person can make based on the current step and their permissions. The feature is available on Grow, Scale and Enterprise. Set up roles so the people writing, approving and publishing can each do their part.
Check the page the reader will actually see
Before publishing a blog post, check the slug, excerpt, metadata, links and cover treatment in the page template. If a cover is still in production, preview how the template handles an empty image. After publishing, open the public page and confirm it appears in the intended listing.
Pilot the workflow on one article. Add a step only when it has a clear owner and a distinct purpose, such as fact-checking a release announcement before an editor approves the copy.
Example: review an announcement with three people
A writer drafts a release announcement about an external form feature. The editor checks that the article explains who can use it and what a successful submission looks like. A product owner verifies the interface labels and any limitations. The publisher then reviews the public preview, checks the documentation link and confirms the scheduled time. If the product name changes after sign-off, the publisher sends the affected copy back to the person who approved it.
On a smaller team, one person may wear two of those hats. Name the role at each step anyway. For instance, a founder can write and approve a short update, then ask a teammate to verify the public link. Knowing who does the final check matters most when the usual publisher is away.
Give reviewers a complete handoff
Intent: One sentence explaining the reader’s question and what the article should help them do.
Evidence: Links to the relevant docs, a test result, or an example the reviewer can reproduce.
Fields: A working title, slug, excerpt, body, author and search metadata.
Open items: Clearly mark what still needs a decision, including a pending screenshot or a release date.
Deadline: State when review is needed and who can approve in the primary reviewer’s absence.
Configure and test permissions with a sample article
Choose a collection that supports workflows and start with one representative draft. Ask a writer, reviewer and publisher to open it using their normal roles. Check which transitions each person can see and whether they can complete the step assigned to them. Use a draft intended for the test so no real announcement goes out while you are checking permissions.
If someone cannot advance the entry, check their role permissions and the current workflow step. For teams that use a custom step, decide who owns it and what must be true for an article to pass. A fact-check step makes sense when someone can verify claims that a general editor cannot.
Handle revisions and the scheduled queue
Agree on which changes reopen review. If a launch date, price or product promise changes, send the revised text to the appropriate approver. When a future post needs to move, update the publishing plan and check that the entry still has the intended status and date. The publisher should also know where to verify that the page became public.
Review the process after a few posts
Track the most common reason articles come back to draft. If documentation links are usually missing, add them to the writer’s handoff. If an approval sits in the queue when someone is out, assign a backup. Keep the workflow light enough for routine publishing and clear enough that a teammate can step in without asking where the article is or who owns the next move.
Once the pilot is working, write the handoff checklist beside the team’s editorial calendar. Review it whenever a new article type introduces a different risk, such as announcing a change before the feature is available.
See the PraismaHub workflow and approvals guide for the product setup.
