Manage User Roles and Capabilities in WordPress

WordPress's five roles rarely fit a real team. Create custom roles, edit capabilities with plain-English labels, and undo any change from a snapshot.

WordPress gives you exactly five roles, each with a fixed set of powers—and real sites almost never fit neatly into five boxes. The moment you need a “Support Agent” who can edit pages but not publish, or an intern who writes drafts but can’t delete anyone else’s work, or a shop manager who touches products but not plugins, the defaults run out. The usual fix is fiddly functions.php code you have to remember to remove afterward. There’s a safer, visual way—and it can undo its own mistakes.

The essentials

  • WordPress has five fixed roles (six on multisite, with Super Admin) and no admin way to edit their capabilities or add new ones.
  • The module lets you create, clone, rename and delete roles, and edit capabilities—core ones with a human-readable label, grouped by area.
  • Per-user overrides: grant a single extra capability to one user without inventing a new role.
  • Automatic snapshots: it saves the previous role setup before each change (the last ten, roles only), so you can restore it—plus a one-click reset to defaults that removes every role not in WordPress core, WooCommerce’s included.
  • Safe by default: editing the Administrator role is locked, only administrators (manage_options) can change roles, and network-only capabilities stay locked on multisite—no privilege escalation.

Why aren’t the default roles enough?

Out of the box, WordPress won’t let you modify an existing role’s capabilities, create a new role from the admin, grant a capability to one user, or export your configuration. The only native path is PHP in functions.php—and because role changes are written to the database once, you then have to remember to remove that code, or it keeps re-applying. It’s the kind of task that’s easy to get subtly wrong and awkward to reverse.

A proper role editor turns all of that into a visual, reversible interface. Before you start bending them, here are the five roles WordPress gives you and where each one stops:

Core roleWhat it can do (per WordPress)Don’t hand it to
AdministratorFull control—content, plugins, users, settingsAnyone who only needs to manage content
EditorManage all content, including others’ posts and pagesA writer who should only touch their own work
AuthorPublish and manage their own postsSomeone who shouldn’t publish without review
ContributorWrite posts, but not publish themAnyone who needs to publish directly
SubscriberManage their own profile onlyAnyone who needs to create content

How do you edit roles and capabilities?

Open the User Role Editor module and every role appears with its capabilities as plain-English checkboxes, grouped by area. From there you add, clone, rename or delete roles, toggle any capability, grant extra capabilities to a single user, and import or export the whole setup as JSON. An automatic snapshot lets you undo a bad change.

Activate the User Role Editor module in Blaminhor Essentials.

Illustration: a ring of users—one at the top with wings, a golden shield and keys, two below with check-marked shields—and three padlocks, two of them open. Different users, different keys. In the module itself, capabilities are grouped and labelled in plain English—so you’re toggling “Edit others’ posts,” not decoding edit_others_posts.

Create, clone and rename roles

Click Add Role, name it, and pick capabilities from scratch—or clone an existing role as a starting point. Clone the smallest role that fits and add powers, rather than cloning Editor and removing some: Editor carries “Edit others’ posts” and “Post unfiltered HTML”, which are easy to forget to untick. You can also rename roles and delete ones you no longer need.

Edit capabilities with real labels

Core capabilities are listed with a human-readable label and grouped by area, not just raw slugs like edit_others_posts; plugin capabilities (WooCommerce’s, say) can be added under Custom Capabilities first, and then appear by their slug. Check or uncheck to shape a role: add WooCommerce product capabilities to your Editor once they’re registered there, or stop Authors from deleting their own posts. What each toggle does is legible at a glance.

Override capabilities per user

Sometimes one person needs one extra permission their role doesn’t include. Instead of creating a whole role for a single user, grant individual extra capabilities to that user, on top of their role (and take those extras away later). You can also assign multiple roles to a user right on the native WordPress profile screen when that fits better than a bespoke role.

Restrict content to certain roles

Roles also decide who reads what. Every public post type gets a Content Restriction box in the editor: tick the roles allowed to see the post, and everyone else gets a log-in prompt in its place. The restriction covers the excerpt, RSS feeds and the REST API as well as the page itself, and the SEO module stops describing the post in its meta tags. For a single passage, the [be_restrict] shortcode does the same inside any content.

Import, export and reset

Save all your roles and their capabilities as a JSON file to move to another site, hand to a client, or keep as a backup before a big change. If you come from the standalone “User Role Editor” plugin, your roles show up as they are, and its custom capabilities and display preferences import in one click. And you can reset everything to WordPress defaults in one click when things get messy—say, after removing a plugin that left custom roles behind. Treat it as the nuclear option: it removes every role that isn’t one of the five core ones, including roles plugins still rely on, such as WooCommerce’s Customer and Shop Manager. The snapshot taken just before the reset lets you bring them back.

How do you create an “Intern” role that drafts but can’t publish?

Start from Contributor, not Editor. Contributor already holds exactly the right powers—edit own posts, delete own posts, read—and nothing else, whereas a cloned Editor keeps “Edit others’ posts” and “Post unfiltered HTML” until you remember to untick them. Clone Contributor, rename the clone, add “Upload files” if the intern needs images in their drafts, and assign it.

You run a site with three editors and one intern:

  1. Clone the Contributor role.
  2. Rename the clone “Intern.”
  3. Tick Upload files (upload_files) if the intern should add images to their drafts—Contributor can’t by default.
  4. Assign the intern to the new role.

The intern can write drafts and edit their own unpublished posts, but can’t publish or touch anyone else’s work—no code, no functions.php edits, and if you got a capability wrong, the snapshot has your back.

What does capability-level control change day to day?

WordPress’s five roles are a starting point, not a straitjacket. With capability-level control you give each person exactly the permissions their job needs—no more, no less—and the automatic snapshot means you can change your mind without fear of locking someone out. That combination is what makes granular permissions usable on a real team, not just possible.

If you’re shaping different experiences per role, it pairs well with the Classic Editor module’s per-role editor choice—decide not just what each role can do, but which editor they see. And when a snippet of your own code should run for administrators only, checking a capability rather than a role is the right test.

User Role Editor is one of the 26 modules in Blaminhor Essentials—free and open-source on WordPress.org.

Download Blaminhor Essentials

– blaminhor

FAQ

What are the default WordPress user roles?

WordPress ships with five on a single site: Administrator (full control), Editor (manage all content), Author (publish their own posts), Contributor (write but not publish) and Subscriber (profile only); multisite adds Super Admin above them. Each has a fixed set of capabilities, and core gives you no admin-interface way to change them or add new roles.

What's the difference between a role and a capability?

A capability is a single permission—publishing posts, say, or deleting other people's pages. A role is a named bundle of those capabilities, such as Editor or Author. You assign roles to users for convenience, but under the hood WordPress is really checking individual capabilities on every action a user tries to take.

Can I give one user an extra permission without changing their role?

Yes. The module supports per-user capability overrides: you grant extra capabilities to a single user on top of their role (and remove those extras later). It's the clean way to handle a one-off—no need to invent a whole new role for one person who needs one extra permission.

What happens to custom roles if I deactivate the plugin?

They stay. Roles are written to the WordPress database once, not held in memory, so custom roles and edited capabilities survive deactivating the plugin. That's handy, but worth knowing: to fully remove a custom role you delete it in the editor or reset to defaults, not just switch the plugin off.

What happens to existing users when I delete their role?

Reassign those users first. If you delete a role while users are still assigned to it, they're left without a valid role and lose the matching capabilities until you give them another. The safe order is always: move everyone to a replacement role, then delete the now-empty one.

What if I break my role configuration?

The User Role Editor takes an automatic snapshot before role changes (the last ten are kept) and lets you restore a previous configuration, so a bad edit is reversible. You can also reset everything to WordPress defaults in one click. As a safeguard, editing the Administrator role is disabled by default to prevent locking yourself out.

blaminhor Building what's missing.

Comments