---
title: "WordPress User Roles: Who Should Get What Access"
url: https://hostmy.blog/wordpress-user-roles/
date: 2026-10-28
modified: 2026-10-28
lang: en
author: "Aditya Sharma"
description: "The six default WordPress roles, what each can do, who on a blog should get which one, and how to audit the accounts you already have."
categories:
  - "WordPress"
image: https://hostmy.blog/wp-content/uploads/2026/10/hmb-card-2620-1024x538.jpg
word_count: 1374
---

# WordPress User Roles: Who Should Get What Access

WordPress user roles decide who can do what on your site, and most blogs give out more access than anyone needs. A freelance writer with an Administrator account can install plugins, change settings and delete other people's work, usually without meaning to and sometimes without noticing.

This post sets out what each default role can do, who should get which one, and how to review the accounts you already have. It is based on WordPress's own documentation of roles and capabilities, and it is written for blog and small business owners with a few people who touch the site.

## The six default roles

WordPress describes its roles in its [documentation of roles and capabilities](https://wordpress.org/documentation/article/roles-and-capabilities/). A role is a set of tasks a user is allowed to perform. The documentation summarises the defaults in one line each.

| Role | What WordPress says it can do | Give it to |
| ---- | ----------------------------- | ---------- |
| Super Admin | Access to the network administration features of a multisite network, plus every other feature | Whoever runs a multisite network, and nobody on a single site |
| Administrator | Access to all the administration features within a single site | The site owner, and a developer for the shortest time needed |
| Editor | Can publish and manage posts, including the posts of other users | The person who runs the editorial calendar |
| Author | Can publish and manage their own posts | A trusted regular writer |
| Contributor | Can write and manage their own posts but cannot publish them | A guest writer or a new hire |
| Subscriber | Can only manage their own profile | A reader with an account, such as a member or commenter |

The default role for new users is a setting. The documentation says it is found under Settings, General, and it is worth checking that it is not set to anything above Subscriber.

## Why the difference matters

The gap between Contributor and Author is the one that changes how a blog works. A Contributor can write but cannot publish, so everything they produce passes through an editor. An Author can publish their own posts straight to the site. For guest writers, that review step is a protection for your readers and for your search rankings.

The gap between Editor and Administrator is the one that protects the site. An Editor works on content, including other people's. An Administrator can change anything on the site, including plugins, themes and users. Almost nobody who writes needs that. When someone does need it, such as a developer fixing a problem, it should be for a defined job and then removed.

## Least privilege in plain words

The rule behind all of this is least privilege: give each person the lowest role that lets them do their job. It limits what a mistake can break, and it limits what a stolen password can do. A writer whose password leaks costs you a draft. An Administrator whose password leaks costs you the site.

The same reasoning applies to anything that logs in on your behalf. Tools and automations that connect to WordPress act as a user, with that user's role. Connecting one to an Administrator account gives it the keys to everything. Where the tool only needs to create drafts, a lower role is the better choice.

## Who should get what, on a typical blog

| Person | Role | Notes |
| ------ | ---- | ----- |
| You, the owner | Administrator | Use a separate, lower account for everyday writing |
| A freelance writer | Contributor | Their work is reviewed before it goes live |
| A regular staff writer you trust | Author | Can publish their own posts |
| Your editor | Editor | Manages posts without touching the site's settings |
| A developer, for a fix | Administrator, temporarily | Remove or downgrade the account when the job is done |
| A reader or member | Subscriber | Has no editing access |

The note on the first row is worth acting on. Day-to-day writing does not need the highest role, so an owner who writes from an Editor or Author account is safer than one who writes from an Administrator account. Keep the Administrator login for the work that needs it.

## Audit the accounts you already have

Most sites have accumulated accounts: a developer from three years ago, a writer who left, a test user. They are the quiet risk, because nobody is watching them. If you have command-line access, this lists every Administrator on the site.

`wp user list --role=administrator --fields=ID,user_login,user_email,user_registered`

You can also see them in the Users screen in the dashboard. For each one, ask whether the person still works with you, whether they still need that role, and whether the email address is one you recognise. Remove or downgrade anything that fails. Repeat the check for Editors, who can change content across the whole site.

## Habits that go with roles

Roles are only part of account safety. Each person should have their own login, so that you can tell who did what and remove one without disturbing the others. Passwords should be unique and long, and two-factor sign-in is worth turning on for anyone above Contributor. [WordPress security without a security plugin that fights your host](/wordpress-security/) sets out the wider approach, and [what breaks on a WordPress site when nobody is watching](/what-breaks-when-nobody-is-watching/) explains why forgotten accounts matter.

When someone leaves, deal with their account the same day. Transfer their posts to another user before deleting the account, or the posts can be removed with it. Backups matter here too, as in [the WordPress backup that did not restore](/wordpress-backup/), because a wrongly deleted account is easier to recover from when a restore has been tested.

## When the default roles are not enough

Some sites need something in between, such as an editor who can manage the media library but not publish. Custom roles and plugins that adjust capabilities exist for this. Use them carefully, because every extra permission is something that can be misused, and a plugin that edits roles is one more thing to keep updated. A good test is whether the same result can be had with a default role. If it can, use the default.

## A worked example: a food blog with a small team

Take a recipe blog with an owner, two freelance recipe writers, a part-time assistant editor and a photographer. Here is how the roles could be assigned, and why.

| Person | Role | Reason |
| ------ | ---- | ------ |
| The owner | Administrator for settings, Editor for daily work | Keeps the highest role for the jobs that need it |
| Two freelance recipe writers | Contributor | Their recipes are checked before they go live |
| The assistant editor | Editor | Can review and publish other people's posts, without access to plugins or settings |
| The photographer | No account | Sends images through a shared folder, and an editor uploads them |

The photographer row is the one people do not think of. Not everyone who contributes to a blog needs a login. Where a person's only job is to hand over files, a shared folder is safer than an account, and it leaves one fewer password to look after.

If one of the freelancers becomes a regular, promote them to Author, and note the date. If one stops working with you, deal with the account that day, and move their posts to another user first so they are not removed with it.

## What to do when you inherit a site

A site you have taken over, from a previous developer, a former employee or an agency, is the most likely place for old accounts. WordPress does not record last logins by default, so you cannot tell from the Users screen who is active. Start with the list, and ask the questions.

`1. List every Administrator and Editor.
2. Ask who each person is, and whether they still work with you.
3. Check each email address is one you recognise and can reach.
4. Downgrade or remove accounts that fail those questions.
5. Change the password on every account you keep.`

An activity log plugin helps if you want to see who has done what in future, but it is optional, and the list above costs nothing. Do it once when you take over, and again every few months.

## Where Host My Blog fits

Checking accounts and roles is part of what we look at when we take on a blog. It is one of the small things that is easy to skip until it matters, as in [what we check before taking on a client blog](/what-we-check-before-taking-a-client-blog/). If you would rather have someone review the accounts regularly and tell you what changed, [our care for bloggers](/for-bloggers/) is built for that.

If you listed every account on your site tonight, could you say why each one has the role it has?