WordPress User Roles Explained: Who Can Do What in 2026

Your best guest writer just agreed to contribute a monthly post, and the next email asks for a login. You open Users, click Add New, and the Role dropdown offers six words that all sound like job titles: Administrator, Editor, Author, Contributor, Subscriber. Choosing one feels like a personality test with security consequences.

It isn't. Each of those words is a bundle of permissions, and picking the wrong one either locks a writer out of their own job or hands a near-stranger the keys to your theme, plugins and settings. Work through the six roles, then the capabilities underneath them, then the handful of cases where the defaults fall short, and that dropdown stops being intimidating.

Table of Contents

The Six WordPress User Roles at a Glance

WordPress ships with six default roles, ordered from most powerful to least: Super Admin, Administrator, Editor, Author, Contributor and Subscriber. On a standard single-site install, the Administrator sits at the top of that list. Super Admin only appears on a multisite network, where it governs every site at once. The official WordPress roles and capabilities reference frames the whole system this way: a role is a named collection of capabilities, and a capability is one specific action, such as publishing a post, moderating a comment or editing a user.

Role Typical holder Publishes own posts Edits others' posts Changes site settings
Super Admin Network owner on multisite Yes Yes, across the network Yes, network-wide
Administrator Site owner or developer Yes Yes Yes
Editor Editorial lead Yes Yes No
Author Trusted independent writer Yes No No
Contributor Guest or new writer No, submits for review No No
Subscriber Reader or commenter No No No

Read the table from the top down and the shape becomes obvious. The higher the role, the wider its reach over both content and configuration. Editor and Author both publish, but only Editor reaches into work written by someone else. Editor and Administrator both handle content, but only Administrator touches settings, themes, plugins and user accounts.

That makes the six roles a ready-made pipeline for a small publication. Administrators configure the site, editors supervise the editorial system, authors publish their own material, contributors submit drafts for review, and subscribers follow updates without any editing access at all. Nobody has to invent a workflow, because the permission ladder already describes one.

Do this now: open the Users screen and compare each account's role with the table. Any account sitting above the work that person actually does is a risk you're carrying for no benefit.

One complication worth knowing early: plugins add their own roles on top of the six. If you sell anything, a Customer role and a Shop Manager role appear, and the WooCommerce customer role capabilities guide is a useful map of what each one can reach before you hand one out. The six defaults are a starting framework, not a fixed limit, and the rest of this guide shows how far you can bend them.

Roles Are Bundles of Capabilities

Think about an office lanyard. The printed side carries your name and job title, and everyone reads it to know what you do. The keys clipped to it are what open doors. WordPress works the same way: the role name is the printed side, and the capabilities are the keys.

WordPress checks keys, not names. The WordPress roles and capabilities documentation puts it plainly: authorization is capability-based rather than role-name-based, each of the six default roles receives a predefined capability set, and names such as publish_posts, moderate_comments and edit_users are the permissions core tests. Codes and plugins should ask current_user_can('capability_name') rather than comparing role strings, because a capability check keeps working when you later invent a custom role.

A leather backpack holding colorful cards representing knowledge, skills, behaviors, experience, and mindset in professional roles.

Here is the lookup that turns the lanyard metaphor into something usable. Find the task, read the capability, and see which default roles hold it.

Task Capability checked Default roles that hold it
Write and save drafts edit_posts Contributor, Author, Editor, Administrator
Publish a post publish_posts Author, Editor, Administrator
Edit other users' posts edit_others_posts Editor, Administrator
Moderate comments moderate_comments Editor, Administrator
Upload media upload_files Contributor, Author, Editor, Administrator
Manage user accounts edit_users Administrator
Install plugins install_plugins Administrator

The gaps in that table explain most permission confusion. A Contributor can draft all day but never holds publish_posts, so their work waits for someone else to press the button. On a single site only the Administrator holds edit_users and install_plugins, which is why an Editor can reorganize your entire homepage and still can't add a plugin.

Every role is just a list of these capability names. Once you can read the list, you can predict exactly what an account can do without logging in as that person. If you want the wider theory behind slicing permissions this finely, Vision's guide to role-based access control frames the same model well outside the WordPress context.

Matching Each Contributor to the Smallest Safe Role

The question isn't "which role is highest?" It's "which role is the smallest one that lets this person finish their work?" Match the person to the row, then move up only when the job demands it.

Contributor type Recommended role Why this role fits
Guest writer who submits drafts for review Contributor Writes and edits own drafts but cannot publish
Trusted freelance writer who publishes own articles Author Publishes own posts without touching others' work
Staff editor who approves all content Editor Edits and publishes any post and moderates comments
Site manager who installs plugins and manages accounts Administrator Controls settings, themes, plugins and users
Reader who wants to comment Subscriber Manages own profile only
Network owner on a multisite install Super Admin Manages the whole network
Comment moderator who never writes Custom role Holds moderate_comments only, no publishing rights

The ladder stops where it does for a structural reason. The WordPress security handbook on user roles and capabilities explains that on a single site the Administrator inherits the capabilities of Subscriber, Contributor, Author and Editor, so the roles form a descending permission structure rather than six unrelated account types. It also draws the line that matters most in practice: an Editor can manage other people's posts and pages but lacks manage_options, which blocks access to core site options. Editorial staff handle content and discussion without ever gaining authority over plugins, themes or accounts.

Run that against a real staffing pattern. Say a publication has one administrator, two editors and five freelance authors. The administrator sets up the theme and decides which plugins live on the site. The editors approve and schedule everything, keep categories tidy, and watch the comment queue, where comments are held for review before they appear. The authors write and publish their own articles and never see anyone else's draft. Nobody needs a capability outside their row, and nobody holds one.

Three mistakes worth naming. Making every collaborator an Administrator because it avoids awkward conversations. Giving Editor access to a writer who only ever submits drafts. Leaving a departed contributor's account active because deleting it feels like paperwork. The first two over-grant, and the third leaves a working login attached to someone who no longer works with you.

Then there's the person the table can't hold: a moderator who reads and clears comments but never writes a post. No default role fits, because Editor drags in publishing and page editing along with comment rights. That's a custom role, and it's the subject of the next section.

How to Safely Give WordPress Access: User Roles & Permissions Explained
Watch this video on YouTube.
This video is hosted by YouTube (Google). Pressing play loads the video from YouTube, which may set cookies and share data with Google.

The contrarian point deserves saying out loud. The familiar hierarchy is a permission ladder, not a staffing chart. WordPress.com's guidance on inviting people recommends granting only the permissions essential to a person's work, and warns against reading the roles as fixed job titles. A role is a bundle, not proof of trust or seniority, and it should be reviewed whenever someone's responsibilities shift.

How to Build a Custom Role Safely

A default role is too broad when you find yourself promoting someone a level too high just to enable one feature. That's the signal to build a narrow role instead of over-granting a wide one.

A six-step infographic showing how to securely build and manage custom user roles within an organization.

  1. Write the task list first. List every action the person must perform, such as drafting posts, uploading images and clearing comments, and note the capability behind each one. You can't trim a permission bundle you haven't defined.
  2. Start from the closest default role. Contributor or Author usually works as a base, because each already carries the safe basics like reading and editing their own drafts. Building upward from a minimal base is safer than stripping an Administrator down and hoping you caught everything.
  3. Add what's missing and remove what's extra. Use add_cap() and remove_cap() on the role object, or reach for a role-management plugin if you'd rather work from checkboxes than code. Either route changes the same stored definition.
  4. Create the role and test it as that user. Assign it to a test account, log in as that person and walk the dashboard. The menus you see should match the task list you wrote in step one, no more and no less.
  5. Confirm your plugins check capabilities, not role names. Any code that compares role strings will ignore your new role entirely. Code that calls current_user_can('capability_name') keeps working, which is the whole reason to build this way.
  6. Record the purpose and set a review date. One line in your notes explaining why the role exists saves an hour of guessing in six months, and the role should be revisited whenever the person's responsibilities change.

A correct result looks unremarkable. The test account can do every task on the list, cannot do anything else, and gets a permission message when it tries. If the account can reach a screen you never listed, the bundle is still too wide.

Practical rule: if you're about to promote someone one level higher just to unlock a single screen, build a role instead. Over-granting is the more expensive shortcut.

Common Permission Questions Answered

Can a Contributor upload images? Yes. Contributors hold upload_files, so they can attach media to a draft. What they can't do is publish the post, so the piece still waits for review.

Can an Author edit a post after publishing it? Yes, but only their own. Authors can revise their published articles and cannot touch anyone else's work at any stage.

Can a Subscriber see unpublished drafts? No. Subscribers hold only the read capability, which gives them public content and their own profile.

Can an Editor install plugins or switch themes? No. Both actions require manage_options, and on a single site only Administrators hold it. If an Editor tells you the plugin screen is missing, nothing is broken.

Does changing someone's role delete their content? No. Posts stay attached to the account and remain on the site. Deleting an account is a separate action, and WordPress asks where that person's posts should go before it proceeds.

Can I grant one capability without changing the whole role? Yes, through a custom role or a plugin that adds that single capability. The rest of the bundle stays exactly as it was, which is often the cleanest fix for a one-off need.

Audit Your User Roles This Week

An audit is smaller than it sounds. Open the Users screen, read the role next to every account, and compare each one against what that person does. Use the capability table above as your reference and treat any mismatch as work to finish, not a note to keep.

Downgrade the obvious cases first. An Administrator who only publishes posts should be an Editor. An Editor who only writes their own articles should be an Author. Then check for accounts belonging to people who have left, and remember that demoting someone to Subscriber is reversible while deleting an account forces you to decide where their posts go.

Even a tiny site benefits. Read More Information is run by a single editor, and that setup still keeps a separate role for anyone who submits a draft, because one shared login erases the record of who wrote what. A guest writer stays a Contributor until their drafts prove reliable, then moves to Author.

Set a rhythm rather than relying on memory. Quarterly works for a small site, and any change in someone's responsibilities should trigger an immediate review. Keeping the rest of the site current matters too, and Baikou's guide to keeping your website up to date treats access review as part of routine maintenance rather than a one-off cleanup.

The test for every account: what is the smallest set of actions this person needs to do the job, and does their role grant anything beyond it?

Three decisions make the habit stick. Name one person who owns role decisions, so access doesn't get granted by whoever answers the email. Write down the default role for each contributor type your site uses. And apply the least-privilege test to every new account from today, before the dropdown becomes a reflex.

To change a role, open Users, select the account's checkbox, choose Change role to from the bulk actions dropdown and confirm. Then open the profile page and check the Role field matches, because a change you didn't verify is a change you don't know about.


Read More Info publishes how-to guides on WordPress themes, scheduled posts, blog layouts and site setup, and the role discipline in this guide is how the site itself runs: a single editor, no shared administrator logins, and the lowest permission level that still gets a post published. If you're setting up your first blog or cleaning up an old one, visit Read More Info and start with the guide that matches where your site is right now.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top