To let WordPress contributors edit their own posts after approval without letting them publish changes, grant a controlled contributor role the edit_published_posts capability and leave publish_posts disabled. Editors or administrators must then review and publish each change. The capability alone does not enforce review of edits to already-published posts.
What contributors can do by default
WordPress describes a Contributor as someone who can write and manage their own posts but cannot publish them. The default role does not include edit_published_posts, the capability WordPress documents for editing a user’s published posts. See WordPress roles and capabilities.
That distinction matters after an editor approves and publishes a post: the contributor’s default permissions do not provide the same ability to revise it. Adding the published-post editing capability can enable that work while keeping publication authority with the editorial team.
Choose an implementation method
| Method | Setup and scope | Publishing and review | Compatibility and maintenance |
|---|---|---|---|
| Role-capability change in code | Requires someone comfortable managing WordPress roles and capabilities. Configure a controlled contributor-derived role and limit its permissions to contributors’ own posts. | Keep publish_posts absent. The capability change does not itself ensure every published-post edit is held for review. |
Verify the implementation against the current WordPress version and test after changes. The cited sources do not establish vendor support or a numeric compatibility measure. |
| WPCode snippet | A snippet-based route presented in the implementation guide; confirm its scope and configuration before use. | Leave publication rights disabled and check that contributors cannot publish changes. | Check current WordPress compatibility and terms; snippet maintenance and support depend on the current product and arrangement. |
| PublishPress permissions | A plugin-based route presented in the implementation guide. Choose a role or permission scope that restricts editing to the contributor’s own posts. | Keep publication rights with Editors or Administrators and verify the configured review workflow. | Check current WordPress compatibility, plugin settings, and terms; support depends on the current product and arrangement. |
The WordPress capability documentation establishes the native permissions model; the implementation guide discusses WPCode and PublishPress as alternatives. Neither cited source provides numeric performance or adoption figures, nor a verified current compatibility rating for these options. See the WPCode and PublishPress sites for current product details.
#1 Best Overall
Configure permissions without handing over publication
- Create or choose a controlled role. Use a contributor-derived role rather than broadening permissions for every account if only a specific contributor group needs to edit published work.
- Grant
edit_published_posts. This is the capability WordPress identifies for editing a user’s published posts. Confirm the role remains limited to the contributor’s own posts. - Do not grant
publish_posts. Keep that capability with Editors or Administrators when an editor must approve publication. - Set an editorial review process for published edits. Editing permission is not an approval gate. Require an editor to review changes and handle publication of the revised post.
- Test with a non-admin account. Confirm the contributor can edit their own published post, cannot edit another user’s post, and cannot publish. Then confirm an editor can review and publish the change.
WordPress checks permission for the specific post being updated; the developer reference illustrates this with current_user_can( 'edit_post', $post_id ). A capability change should therefore be tested against posts owned by different users, not just against the role settings screen. See the current_user_can() developer reference.
Use revisions to review or recover changes
Revisions let editors compare saved versions of a post and restore an earlier one if needed. Include revision review in the editorial process, and test that an editor can restore a previous version after a contributor has changed a published post. WordPress workflow discussions describe revisions as records of saved drafts or published updates and emphasize permissions across the editorial process: WordPress revisions documentation.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Verify the workflow before launch
- A contributor can edit their own already-published post.
- A contributor cannot edit another user’s post.
- A contributor cannot publish a post or a published-post change.
- An editor can review and publish the change.
- An editor can compare revisions and restore an earlier version.
Run these checks in a staging environment with representative contributor and editor accounts before applying the permissions to a live site.
Quick Recap
Best Value
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
