Explainers · Explainer
What Are WordPress User Roles? A Plain Explanation

Short answer
A WordPress user role is a named set of permissions that controls what one user can do on your site. WordPress ships with six roles: Super Admin on multisite, Administrator, Editor, Author, Contributor, and Subscriber. Each role is a bundle of capabilities, which are single permissions such as publish_posts or install_plugins, so give each person the lowest role that still lets them do their job.
Key takeaways
- WordPress ships with six roles: Super Admin on multisite, Administrator, Editor, Author, Contributor, and Subscriber.
- A capability is one single permission, while a role is a named bundle of capabilities given to a user.
- The Subscriber role holds only the read capability, while the Super Admin role holds every capability.
- Editors can publish and manage any post but cannot install plugins or change site settings.
- Give each person the lowest role that still lets them do their job, and review the user list every few months.
What are WordPress user roles?
A WordPress user role is a named set of permissions that controls what one user can and cannot do on your site.
WordPress gives the site owner a way to control what each user can do by assigning them a role. WordPress.org states that WordPress uses roles so the site owner can control tasks such as writing posts, creating pages, moderating comments, managing plugins, and managing other users (checked November 2026).
WordPress ships with six set roles: Super Admin, Administrator, Editor, Author, Contributor, and Subscriber. WordPress.org lists all six, and notes that each role is allowed to perform a set of tasks called capabilities (checked November 2026).
Every user on your site has exactly one role on a single site. That role decides which menus they see in the dashboard and which buttons work for them, so a subscriber sees far less than an administrator.
What is the difference between a role and a capability?
A capability is one single permission, while a role is a named bundle of capabilities given to a user.
Examples of capabilities include publish_posts, moderate_comments, and edit_users. WordPress.org names these three as examples of the many capabilities WordPress defines (checked November 2026).
Think of a role as a job title and capabilities as the tasks that come with it. The Author role is a bundle that includes read, edit_posts, publish_posts, and upload_files, while the Subscriber role holds just the read capability.
WordPress.org states that the Subscriber role has just the read capability, and that the Super Admin role allows a user to perform all possible capabilities (checked November 2026).
A guide on how to add custom user roles in WordPress shows the full method for building a role when none of the six defaults fits the job.
What can an Administrator do?
An Administrator has access to all the admin features within a single site, including plugins, themes, users, and settings.
WordPress.org defines the Administrator as somebody who has access to all the administration features within a single site (checked November 2026).
An administrator can install and delete plugins and themes, add and remove users, change every setting, and run core updates. Learn WordPress states that the administrator can publish, edit, and delete posts and pages, edit code, and manage media, plugins, themes, other accounts, and settings (checked November 2026).
On a single site install, administrators hold extra powers that editors do not. WordPress.org lists update_core, install_plugins, install_themes, delete_plugins, edit_users, create_users, and unfiltered_html among the capabilities only single-site administrators hold (checked November 2026).
WordPress creates an Administrator account when you install it. WordPress.org states that upon installing WordPress, an Administrator account is automatically created (checked November 2026).
What can an Editor do?
An Editor can publish and manage posts, including the posts of other users, but cannot install plugins or change site settings.
WordPress.org defines the Editor as somebody who can publish and manage posts including the posts of other users (checked November 2026).
Editors can create, edit, publish, and delete posts and pages written by anyone on the site. Learn WordPress states that editors can also manage media and comments, and that they cannot install themes or plugins or approve any updates (checked November 2026).
Editors can manage categories and tags, which keeps the site structure tidy without giving them access to settings. WordPress.org lists manage_categories, manage_links, and moderate_comments among the capabilities shared by administrators and editors (checked November 2026).
Editors also hold edit_others_posts, edit_others_pages, publish_pages, and delete_pages. That set is what lets an editor review a contributor draft, fix it, and publish it under the site name.
What can an Author do?
An Author can publish and manage their own posts, and upload media, but cannot touch the posts of other users.
WordPress.org defines the Author as somebody who can publish and manage their own posts (checked November 2026).
Authors can write, edit, publish, and delete their own posts, and they can upload files to the media library. Learn WordPress states that authors can upload media and create, edit, publish, and delete their own posts, and that they have no admin rights (checked November 2026).
The capability list backs this up. WordPress.org shows that authors hold publish_posts, edit_posts, delete_posts, edit_published_posts, and upload_files, but not edit_others_posts or moderate_comments (checked November 2026).
The Author role fits a regular writer who publishes on their own. Give a new writer the Author role only after you trust them to publish without a review step.
What can a Contributor and a Subscriber do?
A Contributor can write and manage their own posts but cannot publish them, while a Subscriber can only manage their own profile.
WordPress.org defines the Contributor as somebody who can write and manage their own posts but cannot publish them, and the Subscriber as somebody who can only manage their profile (checked November 2026).
Contributors submit drafts for review, and an editor or administrator publishes them. Learn WordPress states that a contributor cannot upload media files, and that their content will be reviewed before publishing (checked November 2026).
Subscribers hold only the read capability, which lets them log in, read posts, and change their own profile. WordPress.org states that the Subscriber role has just the read capability (checked November 2026).
| Role | Can publish own posts | Can edit other posts | Can upload media | Can install plugins |
|---|---|---|---|---|
| Administrator | Yes | Yes | Yes | Yes |
| Editor | Yes | Yes | Yes | No |
| Author | Yes | No | Yes | No |
| Contributor | No | No | No | No |
| Subscriber | No | No | No | No |
What is the Super Admin role on multisite?
The Super Admin role exists only on a WordPress multisite network, and it controls the whole network of sites.
WordPress.org defines the Super Admin as somebody with access to the site network admin features and all other features (checked November 2026).
Super Admins hold every capability, including network-only ones such as create_sites, delete_sites, manage_network, manage_network_plugins, and manage_network_themes. WordPress.org lists 10 network-only capabilities that are only available to Super Admins (checked November 2026).
On a single site install there is no Super Admin, because there is no network to manage. WordPress.org states that in a single site install, administrators are in effect Super Admins, and only they hold the extra admin capabilities (checked November 2026).
How do you change a user role?
Open Users in the dashboard, edit the user, pick a new role from the drop-down, and save the profile.
To add a new user, open Users and click Add New, then fill in a username and a valid email address and pick a role before you save. Learn WordPress states that WordPress sends the new user a welcome email with their login details, including a generated password (checked November 2026).
To change an existing user, open Users, click Edit under the name, open the Role drop-down, and pick a different role. Learn WordPress states that you can select Edit, open the role drop-down, and select a different role or no role for the site at all (checked November 2026).
You can change several users at once with the checkboxes to the left of each name. Learn WordPress states that you can use the checkboxes to change the role of multiple users at the same time (checked November 2026).
Set the default role for new sign-ups under Settings, then General. WordPress.org states that the default role for new users can be set in Administration Screens, then Settings, then General (checked November 2026).
You can also manage users from the terminal. Developer.WordPress.org describes wp user as the command that manages users, along with their roles, capabilities, and meta (checked November 2026).
If you manage users from the terminal, run WP-CLI as the site user, not as root. The WordPress hosting handbook warns that running as root can leave files owned by root that the web server cannot write to later (checked November 2026).
A guide on how to set up a staging site for WordPress gives you a safe copy of the site where you can try role changes before you make them live.
How do you pick the right role for each person?
Give each person the lowest role that still lets them do their job, and raise it only when the work proves they need more.
Start with the job, not the person. A guest writer needs Contributor, a regular writer needs Author, a content lead needs Editor, and only the site owner or a trusted developer needs Administrator.
A client who only reviews content should get Editor, not Administrator. Editors can publish and manage every post, but they cannot install plugins or change settings, so a mistaken click cannot break the site.
A shop or membership site may need subscribers for its customers. Subscribers can log in and manage their profile, and nothing else, which keeps the customer area simple and safe.
Review the user list every few months. Old staff, past guest writers, and test accounts often keep roles they no longer need, and each one is a login that could be misused.
A guide on how to run a WordPress security audit covers the user list as one of the checks, since unused admin accounts are a common weak point.
What myths about user roles should you ignore?
The most common myth is that roles form a strict ladder, so a higher role always includes every power of the roles below it.
WordPress.org states that one role should not be seen as senior to another, and that roles define the user responsibilities within the site instead (checked November 2026).
A second myth is that an Editor can install plugins because they manage content. Editors cannot install themes or plugins, and they have no access to site settings, as the Learn WordPress lesson states (checked November 2026).
A third myth is that a Contributor can upload images with their draft. Contributors cannot upload media files, so an editor must add images to a contributor post or raise the writer to Author first (checked November 2026).
A fourth myth is that deleting a user always deletes their posts. When you delete a user, WordPress asks whether to delete all the content they created or reassign it to a different user, as the Learn WordPress lesson states (checked November 2026).
A fifth myth is that a custom role is hard to build. The roles documentation shows a short code sample that creates a Site Editor role with add_role(), and a second sample that adds a capability to the Editor role with add_cap() (checked November 2026).
How do you check what a role can do on your site?
Log in as a user with that role, open the dashboard, and confirm which menus appear and which actions work.
The fastest check is a test account for each role you use. Create one test Editor, one test Author, and one test Contributor, then log in as each and look at the dashboard menus they see.
Check the capability table in the roles documentation when a permission surprises you. WordPress.org publishes a full table that marks each capability as yes or no for Super Admin, Administrator, Editor, Author, Contributor, and Subscriber (checked November 2026).
If a user sees a 403 error where they should have access, the role may lack a capability the page needs. A guide on how to fix the 403 forbidden error covers the server and permission checks that go with a role check.
Site Editor access is a common surprise. WordPress.org states that edit_theme_options is the main capability WordPress checks when it decides whether a user can open the Site Editor (checked November 2026).
Frequently asked questions
Can two people share one role with different permissions?
No. Roles are a bundle of capabilities, so you cannot split one role between two people. Give each person the role that fits their job, or create a custom role with add_role() when none of the six defaults fits.
How do I change a user role in WordPress?
Open Users, click Edit under the name, open the Role drop-down, and pick a different role. You can also change several users at once with the checkboxes to the left of each name.
Is there a role above Administrator?
Yes, but only on a multisite network. The Super Admin role controls the whole network, including creating sites and managing network plugins and themes. On a single site install there is no Super Admin role.
Can a Contributor upload images with a draft post?
No. Contributors can write and edit their own posts but cannot publish them or upload media files. An editor or administrator must review the draft, add any images, and publish it.
Can I create a custom user role?
Yes, with code. The roles documentation shows add_role() for creating a new role and add_cap() for adding a single capability to an existing role. A role plugin can also do this from the dashboard.
Why does a user see a 403 error on a dashboard page?
The most likely cause is a missing capability, since each dashboard screen checks for one. Check the capability table in the roles documentation, confirm the user role, and check whether a plugin hides that menu with its own settings.
Sources
- Roles and Capabilities WordPress.org
- User management Learn WordPress
- WP-CLI Commands WordPress Developer Resources
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
Related guides
About the editors
Researched from the primary sources listed above and checked against our editorial rules before publishing.


