If freelancers, guest writers or an agency touch your WordPress site, the role you give each person decides what they can publish, edit or break. This guide is for small business owners and bloggers who manage their own site. It explains what the default roles can and cannot do, how to choose the smallest role that lets someone do their job, how to add, change and remove users, and where application passwords fit in. It is based on the official WordPress.org documentation.
Contents
What a role is
WordPress documentation describes a role as a set of tasks a user is allowed to perform. Each task is called a capability, such as publishing posts or moderating comments. Every role comes with a default set of capabilities. The documentation also says roles are not a ranking: they define a user’s responsibilities on the site.
The default role for new users is set under Settings → General. The same documentation notes that an Administrator account is created automatically when WordPress is installed.
The default roles, in plain English
- Subscriber: can only manage their own profile. Their only default capability is “read”.
- Contributor: can write and manage their own posts but cannot publish them.
- Author: can publish and manage their own posts.
- Editor: can publish and manage posts, including the posts of other users.
- Administrator: has access to all the administration features within a single site.
- Super Admin: exists on multisite networks and has access to network administration features and all other features.
Role comparison table
This table summarises selected capabilities from the official capability-versus-role table. It is a simplified view of a long list, so check the source for anything not shown.
Enjoying this? Get our best tips by email
Practical SEO, link building and content strategies, straight to your inbox.
| Capability | Subscriber | Contributor | Author | Editor | Administrator |
|---|---|---|---|---|---|
| Write and delete own unpublished posts | No | Yes | Yes | Yes | Yes |
| Upload files | No | No | Yes | Yes | Yes |
| Publish own posts | No | No | Yes | Yes | Yes |
| Edit and delete others’ posts | No | No | No | Yes | Yes |
| Edit and publish pages | No | No | No | Yes | Yes |
| Moderate comments | No | No | No | Yes | Yes |
| Change theme options, manage settings, import and export | No | No | No | No | Yes |
| List, promote and remove users | No | No | No | No | Yes |
| Install plugins and themes, edit users, update core | No | No | No | No | Yes (single site only) |
A Contributor has no upload capability by default, so a guest writer at that level cannot add images to their own drafts.
Single site versus multisite
On a single-site install, the documentation says Administrators are in effect Super Admins, and only they have capabilities such as installing plugins and themes, updating core, and editing or deleting users. On multisite, those abilities belong to the Super Admin, and an Administrator’s powers are limited to one site. The Super Admin also holds network-only capabilities such as creating sites and managing network plugins, themes and users.
How to pick the least-privileged role
The idea is simple: give each person the lowest role that still lets them finish their work. The role definitions above translate into a practical starting point.
- Guest writer who submits drafts for review: Contributor. They can draft but not publish, so you stay in control of what goes live.
- Regular freelance writer you trust to publish and who needs to upload images: Author. They can publish their own posts and upload files, but cannot edit anyone else’s content.
- Managing editor or proofreader who must change other people’s posts and pages: Editor. They can also moderate comments and manage categories.
- Members or customers with a login: Subscriber, which carries only the read capability.
- Agency or developer changing themes, plugins or settings: This work needs Administrator on a single-site install. Because that role also covers user management and updates, give it for the length of the job and review it afterwards.
Common mistakes
- Making everyone an Administrator for convenience. The role includes capabilities to install plugins, edit users and update core on a single site.
- Leaving the default role for new users too high. Check it under Settings → General.
- Sharing one login between several people, which makes it hard to tell who did what or to remove one person cleanly.
If you publish under contributors’ names, see our post on honest bylines and author pages so the author shown matches the person who wrote the piece.
How to add a user
- In the dashboard, go to Users → Add New.
- Enter a username and an email address. Both are required, and the email address must be unique for each user.
- Set a password. The screen shows a strength indicator, and the documentation suggests mixing upper and lower case letters, numbers and symbols.
- Tick the option to send the password to the new user by email if you want WordPress to deliver it.
- Choose the Role from the drop-down. If you leave it alone, it uses the New User Default Role from Settings → General.
- Click Add New User. If you do not click this button, the user is not added.
These labels follow the official documentation, so the wording on your WordPress version may differ slightly.
How to change or remove a role
Go to Users → All Users. The table lists each username, name, email address, role and number of posts. Use the links above the table to filter by role, or the search box to find someone by username, name, email or website.
- Tick the checkbox beside one or more users.
- Use the “Change role to” drop-down and pick the new role.
- Click Change. A “Changed roles.” message confirms the update.
To edit one person in detail, click their username to open the Edit User screen. To take someone’s access away completely, delete the user, as described next.
What happens to content when you delete a user
You can delete a user from the row link on All Users or as a bulk action. You cannot delete the account you are logged in with. WordPress then shows a Delete Users screen asking what should be done with posts and links owned by that user. There are two choices:
- Delete all posts and links: removes the user and everything attributed to them.
- Attribute all posts and links to: keeps the content and reassigns it to another user you choose from a drop-down.
For a freelancer whose published work should stay on the site, attribute it to an existing account such as an editor or the site owner before you confirm. Choosing the first option on a prolific writer removes their posts. Take a backup first; our guide to automatic off-site WordPress backups covers the options. The documentation does not describe a way to undo this choice, so treat it as permanent.
Where application passwords fit in
Some tools need to reach your site without a person logging in. WordPress core handles this with application passwords, introduced in WordPress 5.6. The details below come from the WordPress core team’s integration guide, a developer-facing post on make.wordpress.org.
- Each application password is 24 characters of letters and numbers, and is meant for programmatic access only. It cannot be used to log in through the normal login page.
- Users create, view and revoke their own on the Edit User screen. Anyone who has permission to edit a given user can also manage that user’s passwords.
- By default they are available to all users on sites served over HTTPS. Developers can restrict or disable them with filters.
- The guide describes limiting (“scoping”) what a single password can access as something expected in future versions, so treat each password as carrying the access of the account that created it.
The practical lesson follows from that last point. An application password is only as safe as the role of the account behind it. If a publishing tool only needs to create drafts, connect it to a dedicated Contributor account rather than your Administrator login, and name each password after the tool so you know what to revoke when you stop using it.
Review Users → All Users whenever a contract ends, starting with Administrators. If open registration is on, our guide to preventing user-generated spam on WordPress is a useful companion.
Key takeaways
- Contributors draft but cannot publish or upload files; Authors publish their own work; Editors manage everyone’s posts; Administrators control the whole site.
- Choose the lowest role that allows the work, and review roles when projects end.
- Use Users → All Users to change roles in bulk, and decide whether to delete or reassign content before deleting anyone.
- Treat an application password as carrying the access of the account that created it, and tie each tool to an account with a limited role.
FAQ
Can a Contributor publish a post?
No. The documentation describes a Contributor as someone who can write and manage their own posts but cannot publish them.
What is the difference between an Author and an Editor?
An Author can publish and manage only their own posts. An Editor can publish and manage posts including those of other users, and can also moderate comments and manage pages and categories.
Does my site have a Super Admin?
Only if it is a multisite network. On a single-site install, the documentation says Administrators are in effect Super Admins.
Can an application password log someone into the dashboard?
No. According to the core team’s guide, application passwords cannot be used to log in through the standard login page. They are for programmatic access such as the REST API.
