PublishPress Capabilities

PublishPress Capabilities extends role editing into a broader permission and interface-control system for WordPress teams.

Quick take

PublishPress Capabilities fits editorial, WooCommerce and multisite teams that want role editing plus admin, editor, media and frontend feature restrictions. It is particularly relevant when the project needs both capability changes and control over what editors see in the dashboard, editor, media library, profile or navigation menus.

Role and capability model

PublishPress Capabilities can create or copy roles, edit native capabilities, control WooCommerce permissions, restrict admin and editor features, manage taxonomy capabilities, and synchronize changes across multisite networks.

PublishPress Capabilities should be configured from a written permission map, not by clicking capabilities until a screen appears. PublishPress Capabilities projects should map role capabilities together with editor features, admin menus, media permissions and WooCommerce access because those layers can be changed independently.

Important capabilities

• create and copy roles
• edit WordPress capabilities
• automatic permission backups
• admin menu restrictions
• block and classic editor feature restrictions
• WooCommerce permissions
• media library permissions
• multisite synchronization

Automatic permission backups provide a useful safety layer for teams that make frequent role changes. The plugin also goes beyond capability checkboxes by hiding or limiting interface elements according to role.

Pricing and licensing

A free edition is available on WordPress.org. PublishPress currently lists its Business bundle at $129 per year for one site and includes Capabilities Pro among the suite plugins.

PublishPress Capabilities cost matters less than the operational risk of a poorly documented role model. PublishPress Capabilities free is sufficient for many role changes, while Pro becomes more relevant when interface restrictions, advanced admin controls and commercial support are part of the operating model.

Safe implementation

Use the backup history before and after major permission changes, and test restricted editor or admin features with actual role accounts because hiding a menu item is different from removing the underlying capability.

When testing PublishPress Capabilities, keep a separate administrator account untouched and verify the edited role in a private browser session. PublishPress Capabilities testing should use its automatic permission backups and a separate test account so both the underlying capability and the visible admin interface can be checked independently.

Where it fits

PublishPress Capabilities fits newsrooms, agencies, WooCommerce stores and multisite networks where permissions and the visible admin experience need to be managed together.

PublishPress Capabilities is easier to maintain when role names describe organizational responsibility rather than individual people. PublishPress Capabilities works best with role names tied to ongoing responsibilities, because admin and editor feature rules are easier to maintain when the same role survives personnel changes.

Trade-offs

The broader PublishPress model may be excessive for a small site with two simple roles. Highly granular access to individual posts or terms may also require PublishPress Permissions rather than Capabilities alone.

PublishPress Capabilities already controls several admin and editor surfaces, so adding separate menu-hiding plugins can create duplicate rules that are difficult to troubleshoot. For PublishPress Capabilities, decide whether another plugin truly needs to modify the same admin menu, editor feature, media, or WooCommerce permission before layering additional controls.

Migration and rollback

Export or record current role definitions, then compare permissions for editor screens, WooCommerce objects, media and custom post types after moving from another role editor.

PublishPress Capabilities migrations should be verified against custom post types and plugin-defined capabilities because those permissions may not exist on a clean WordPress install. Keep PublishPress permission backups and a before-change role record until editors, shop managers, authors and administrators have passed their normal workflows.

PluginSuggest verdict

PublishPress Capabilities is a strong alternative when role editing must extend into admin-interface and publishing-workflow control.

Interface restriction versus authorization

PublishPress Capabilities can hide editor features and admin menu items, but an interface restriction should not be confused with the capability that authorizes an action. Test both layers. A hidden menu can simplify a dashboard without being the security boundary, while a removed capability can block the action even if another plugin exposes a link to it.

WooCommerce sites should test products, orders, coupons and product taxonomies separately because commerce permissions often extend beyond the standard post capabilities familiar to editorial teams.

Backup review cadence

Automatic permission backups are most useful when teams know when to review them. Keep a short change note for major role edits and verify that the backup timestamp matches the change. On sites with several administrators, this creates a practical audit trail and makes it easier to identify whether a new publishing problem came from a capability change or an unrelated plugin update.

Free versus Pro permission controls

PublishPress Capabilities Free covers core role and capability editing, while Pro adds deeper restrictions around the WordPress admin, navigation menus, media library access, WooCommerce permissions, editor features, admin notices, and blocking specific admin pages by URL. The practical difference is that Free is mainly a role editor, while Pro can also simplify or lock down the admin experience for client and staff roles.

Permission backups are useful before a large role cleanup because they give you a known-good reference if a plugin update or manual edit removes required capabilities. On WooCommerce and publishing sites, test custom roles against real workflows rather than only checking whether a menu is visible: creating orders, uploading media, editing taxonomies, publishing content, and accessing reports may depend on separate capabilities.

Current licensing and migration checks

PublishPress currently bundles Capabilities Pro into its paid plugin plans: Business is 9 per year for one site, Agency is 9 for five sites, and Unlimited is 9. Before migrating from another role editor, export or document the current roles and capabilities, then compare admin-menu restrictions separately because those controls are often stored in plugin-specific settings rather than native WordPress role data.

PublishPress Capabilities FAQs