Require a Manager's Sign-Off Before Anything Reaches Your WordPress Site
Why publishing to an external CMS is gated at a higher role than editing a draft, and what that means for how you set up your team.
Editing a draft and putting it on your live, public website are not the same level of risk, and the content app's permission model treats them that way on purpose.
The two thresholds
Most actions in the content app — writing, editing, revising — only need write access. That's intentionally low friction: anyone contributing to a draft shouldn't need elevated permissions just to do their job.
Publishing to an external CMS is different. The route that sends an article to WordPress or a generic endpoint checks specifically for Manager role or above — Editor or Admin, in the app's terms. A contributor with plain write access can build a draft end to end, but the actual "send this to WordPress" action requires someone at that higher threshold to trigger it, or to have approved the connection settings being used.
Why the line is drawn here specifically
A draft with a mistake in it costs you a review cycle. A post that goes out with a mistake, a wrong claim, or something that shouldn't have gone public yet costs you a public correction — a different order of consequence entirely. Gating the specific action that crosses from "internal workspace" to "published on a site your customers see" is a narrower, more deliberate control than just requiring write access for everything, and it means whoever hits publish is someone with the standing to make that call.
Setting this up for your team
If you're structuring roles for a content team, the practical version of this is: writers and editors get write access and do the drafting, reviewing, and internal approval work. Whoever actually owns the relationship with your WordPress site — or is accountable for what goes out under your brand — should be a Manager or above. That person doesn't need to write every post; they need to be the one who can send it.
This pairs naturally with in-editor commenting for review (see the companion guide) — a draft can go through as many comment rounds as it needs at the write-access level, and the publish action stays a deliberate, single, accountable step at the end.