Black FridayCyber Monday 2026
14Days
15Hrs
34Mins
44Secs
Flat20% OFF

Our biggest sale of the year20% off the first payment on all maintenance plans. Code BF2026

Grab the deal
WordPress

WordPress User Roles and Permissions: Give Each Person Least Access

Too many administrators is a common security risk. Learn what each WordPress role can do, how to audit your users and how to give each person the least access.

wpallsolution Updated 5 min read

WordPress user roles decide what each person can do on your site: write a post, publish it, upload files, install plugins or change settings. Many sites collect extra administrator accounts over the years, from former developers, agencies and staff, and every one is a door into your site. The idea of least access is simple: give each person the lowest role that lets them do their job. This guide explains the built-in roles and shows how to audit your users in an afternoon.

Quick answer

Open Users, All Users and check every account. Keep Administrator for the one or two people who really manage the site. Use Editor for people who manage and publish others’ content, Author for people who publish their own posts, Contributor for writers whose work needs review, and Subscriber for accounts that only need a profile. Remove accounts you do not recognise or no longer need, and protect the remaining administrator accounts with strong, unique passwords and two-factor sign-in.

How this guide was prepared: it is research-based. We used the WordPress documentation on roles and capabilities listed under Sources, checked on October 23, 2026. We did not review your site. Plugins such as WooCommerce add their own roles, so check what your site uses.

What the built-in roles can do

  • Administrator: full control of a single site, including themes, plugins, users and settings. (On a multisite network there is also a Super Admin above this.)
  • Editor: can publish and manage posts, including other people’s.
  • Author: can publish and manage their own posts and upload files.
  • Contributor: can write and edit their own posts but cannot publish them.
  • Subscriber: can only manage their own profile.

Each role is a bundle of smaller permissions called capabilities. WooCommerce, membership and forum plugins add roles such as Customer or Shop manager, so the list on your site may be longer.

The decision tree: does everyone have the right role?

Flowchart for auditing WordPress user roles: five questions about unknown users, administrators, publishing rights, former contractors and admin security
Five questions find over-powered accounts.
  1. Do you know every user account? If not, list and clean them (Step 1).
  2. Do more than a few people have Administrator? Lower their role (Step 2).
  3. Do writers need to publish without review? Choose Contributor or Author (Step 3).
  4. Does anyone from an agency or freelancer still have access? Remove or limit it (Step 4).
  5. Do admin accounts use strong passwords and 2FA? Secure them (Step 5).

5 steps to apply least access

Step 1: List every user

Go to Users, All Users and filter by role. Note who each account belongs to and whether they still need it. If your host gives you command-line access, WP-CLI can print the list: wp user list --fields=ID,user_login,user_email,roles. Look for accounts you do not recognise, since unknown administrators are a warning sign; see our PHP2Shell article for what attackers do after a break-in.

Step 2: Reduce the number of administrators

Ask whether each administrator truly needs to install plugins, change themes or manage users. If not, change the role by editing the user and choosing a new one in the Role field. Keep a note of who you demoted in case something stops working for them. Take a backup first if you are unsure; see backup and restore testing.

Step 3: Match roles to the work

Match the role to the task. A freelance writer who sends drafts for review fits Contributor. A staff blogger who publishes their own posts fits Author. A content manager who edits everyone’s posts fits Editor. A shop assistant who only manages orders may need a WooCommerce role rather than Administrator.

Step 4: Remove old and shared access

Delete accounts for people who have left. When you delete a user, WordPress asks what to do with their content, so reassign it instead of deleting it. For agencies and developers, create a named account for each person instead of sharing one login, and remove it when the job ends. Avoid sharing the same password across several people.

Step 5: Protect the accounts that remain

Use long, unique passwords from a password manager, add two-factor sign-in for administrators and editors, and limit login attempts. See WordPress login security for options such as 2FA and passkeys. Keep your own email address current so password reset links reach you.

Version and hosting differences

  • On multisite, Super Admin controls the network and site administrators have less power.
  • Plugins can add roles or change capabilities, so check the Role list on your site.
  • Some hosts add their own access layer for staff; review those accounts too.

How to verify the result

  • Each person has the lowest role that still lets them work.
  • Only a small, known set of people are administrators.
  • Old accounts are gone and their content is reassigned.
  • Administrators use 2FA and unique passwords.

Common mistakes

  • Making everyone an administrator to avoid permission problems.
  • Sharing one login between several people.
  • Deleting a user and losing their posts.
  • Leaving a former agency account active.

Frequently asked questions

What is the difference between Editor and Author?

An Editor can manage and publish other people’s posts. An Author can publish and manage only their own.

Can a Contributor publish a post?

No. A Contributor can write and edit their own posts, but an Editor or Administrator has to publish them.

How many administrators should a site have?

As few as possible. For many small business sites, one or two trusted people is enough.

Can I create a custom role?

Yes, with a role management plugin or code. Test carefully, because a wrong capability can lock people out or give too much access.

Related guide: “Sorry, You Are Not Allowed to Access This Page” in WordPress: Causes and Fixes

What to do next

Run the user audit today. If you want a second pair of eyes, our WordPress maintenance packages include regular checks, and our emergency fix service helps if you suspect a break-in. We cannot promise your site will never be attacked.

Sources and official documentation

Keep reading

More guides

Need a hand with this?

Tell us what is happening. We reply with honest next steps.

Talk to us