How to Change Administrator to Editor in WordPress

How to Change Administrator to Editor in WordPress: Complete 2026 Guide

To change an Administrator to Editor in WordPress, go to Users → All Users, find the Administrator account, click Edit, scroll to the Role dropdown, select Editor from the list, and click Update User.

 

 

This immediately downgrades their permissions from full site control to content management only, improving your site’s security posture.

Downgrading Administrator accounts is one of the most effective security hardening steps you can take. Many WordPress sites have far too many users with full administrative access, creating unnecessary risk. By changing Administrators to Editors, you limit their capabilities to content-related tasks while preventing potentially dangerous changes to plugins, themes, users, and site settings.

This 2026 guide shows you exactly how to change Administrator to Editor using multiple methods—dashboard, bulk actions, plugins, WP-CLI, and database—plus critical security considerations and best practices.

Last updated: September 2026

---

Why You Should Change Administrator to Editor

Having too many Administrator accounts is a leading cause of WordPress security breaches. Here’s why downgrading makes sense:

Reduce Attack Surface

Each Administrator account is a potential entry point for attackers. By limiting the number of full admins, you:

• Decrease phishing targets

• Minimize damage from compromised credentials

• Reduce risk of accidental site-breaking changes

Apply Least Privilege Principle

Users should have only the permissions they need. Most content creators don’t require:

• Plugin installation capabilities

• Theme editing access

• User management powers

• Site-wide settings control

An Editor role provides full content management without these risks.

Improve Accountability

When fewer people have Administrator access:

• Changes are easier to track

• Responsibility is clearer

• Audit trails are more meaningful

Protect Against Insider Threats

Former employees, disgruntled contractors, or compromised accounts with Administrator access can cause catastrophic damage. Downgrading to Editor limits this risk significantly.

Check this post: WordPress Role Security Checklist

---

Understanding the Difference: Administrator vs Editor

Before making the change, understand what capabilities are lost and retained.

Administrator Capabilities (Full Access)

• Install, activate, and delete plugins

• Install, activate, and delete themes

• Edit theme and plugin PHP files

• Manage all user accounts and roles

• Change site-wide settings (General, Reading, Permalinks, etc.)

• Access Tools (Import, Export, Site Health)

• Create, edit, delete any content (posts, pages, custom post types)

• Moderate all comments

• Manage categories and tags

Editor Capabilities (Content Only)

• Publish, edit, and delete any post or page (including others’)

• Manage categories and tags

• Moderate all comments

• Upload files to Media Library

• View site statistics (if plugin provides)

Cannot Do as Editor:

• Install or manage plugins

• Install or manage themes

• Edit theme or plugin code

• Create or manage user accounts

• Change site settings

• Access Tools menu

• Modify site structure or configuration

Key Takeaway: Editors have complete control over content but cannot modify site infrastructure, install extensions, or manage users.

See this post for more details: WordPress user roles explained

---

Before You Change: Critical Considerations

Downgrading an Administrator is permanent and affects their workflow. Consider these factors first:

Confirm They Don’t Need Admin Access

Ask:

• Do they install or update plugins?

• Do they manage theme settings or custom code?

• Do they need to create or manage user accounts?

• Are they responsible for site configuration or backups?

If yes to any, they may still need Administrator access—or you need to reassign those tasks.

Communicate the Change

Especially for team members or clients:

• Explain why the change is happening (security best practice)

• Clarify what they can still do (full content management)

• Provide a contact person for technical tasks (plugin installs, etc.)

Ensure Another Administrator Exists

Never downgrade the only Administrator on your site. You’ll lock yourself out of critical functions. Verify at least one trusted person retains full admin access.

Document the Change

Keep a record of:

• Who was downgraded

• When it happened

• Who approved it

• What their new responsibilities are

Test Their Workflow

After the change:

• Have them test their typical tasks

• Confirm they can still publish, edit, and manage content

• Address any legitimate needs for elevated access

---

Method 1: Change Administrator to Editor via Dashboard (Easiest) – 7 Steps

This is the standard method for downgrading one user at a time.

Step 1: Log Into WordPress Dashboard

Visit yoursite.com/wp-admin and log in with an Administrator account that will remain as Administrator.

Important: Do not downgrade your own account using this method—you won’t be able to reverse it easily.

Step 2: Navigate to Users → All Users

In the left sidebar:

1. Hover over Users.

2. Click All Users.

Step 3: Find the Administrator to Downgrade

Scroll through the user list or use the search box to locate the Administrator account you want to change.

Step 4: Click Edit

Hover over the username and click the Edit link that appears below it.

Step 5: Scroll to the Role Section

On the user profile page, scroll down until you find the Role dropdown menu.

Step 6: Select Editor

Click the dropdown and choose Editor from the list.

Available options:

• Administrator (current)

• Editor (select this)

• Author

• Contributor

• Subscriber

Step 7: Click Update User

Scroll to the bottom of the page and click the Update User button.

A confirmation message appears: “User updated.”

The user is now an Editor with content-only permissions.

---

Method 2: Change Multiple Administrators to Editors (Bulk Action) – Steps

For sites with many overprivileged users, WordPress allows bulk role changes.

Step 1: Go to Users → All Users

Navigate to the Users list in your dashboard.

Step 2: Filter by Administrator Role

At the top of the user table:

1. Click Administrator link (shows count, e.g., “Administrator (5)”)

2. This filters the list to show only Administrators

Step 3: Select Administrators to Downgrade

Check the boxes next to the usernames you want to change.

Pro tip: Leave your own account and at least one other trusted Administrator unchecked.

Step 4: Choose Bulk Action

At the top of the user table:

1. Find the Bulk Actions dropdown.

2. Select Change role to…

3. Choose Editor from the submenu.

Step 5: Click Change

Click the Change button next to the dropdown.

All selected Administrators are now Editors.

Warning: This change is immediate and affects all selected users simultaneously. Ensure they’ve been notified beforehand.

---

Method 3: Change Administrator to Editor with a Plugin

Plugins like User Role Editor, Members, or Capability Manager Enhanced provide advanced role management with additional controls.

Example: Using User Role Editor

1. Install and activate the User Role Editor plugin.

2. Go to Users → User Role Editor in your dashboard.

3. Select the Administrator you want to downgrade from the user dropdown.

4. Uncheck the “Administrator” role.

5. Check the “Editor” role.

6. Click Update to save changes.

Example: Using Members Plugin

1. Install and activate the Members plugin.

2. Go to Members → Members in your dashboard.

3. Find the user and click Edit.

4. Change their role from Administrator to Editor.

5. Click Update User.

Benefits of Using Plugins

• View detailed capability lists before changing

• Create custom intermediate roles (e.g., “Senior Editor” with select admin capabilities)

• Audit role changes with activity logs

• Revert changes more easily if needed

Post to check: custom WordPress roles and capabilities

---

Method 4: Change Administrator to Editor via WP-CLI (Advanced)

For developers or agencies managing multiple sites, WP-CLI allows fast, scriptable role changes without loading the dashboard.

Prerequisites

• SSH access to your server

• WP-CLI installed on your host

Command to Change Role

Replace:

• johndoe with the Administrator’s username

• editor with the target role (in this case)

Examples

Using User ID:

Change Multiple Administrators:

(This changes the first 3 Administrators to Editors—adjust head -n 3 as needed)

Verify the Change

List users to confirm:

The downgraded users now show editor instead of administrator.

---

Method 5: Change Administrator to Editor via phpMyAdmin (Database Method) – 6 Steps

For advanced users who need to change roles directly in the database (e.g., when locked out of wp-admin or after a security incident).

Warning

This method is risky—incorrect database edits can break your site. Always back up first.

Step 1: Access phpMyAdmin

Log into cPanel → Databases → phpMyAdmin. Select your WordPress database.

Step 2: Find the User ID

Open the wp_users table and locate the Administrator. Note their ID (e.g., 42).

Step 3: Open wp_usermeta Table

Click on the wp_usermeta table (adjust prefix if needed).

Step 4: Find Capability Row

Look for the row where:

• user_id matches the user’s ID (e.g., 42)

• meta_key is wp_capabilities

Step 5: Edit wp_capabilities

Click Edit on the wp_capabilities row. Replace the meta_value with:

For Editor:

Click Go to save.

Step 6: Edit wp_user_level

Find the row where:

• user_id matches the user’s ID

• meta_key is wp_user_level

Click Edit and change meta_value to:

For Editor:

Click Go to save.

The user is now an Editor in the database.

---

Special Case: WooCommerce Shop Managers

If you run a WooCommerce store, you may have Shop Managers with Administrator-like access to e-commerce functions.

Shop Manager vs Editor

Shop Manager Capabilities:

• Manage orders, products, coupons, customers

• View WooCommerce reports

• Edit content (similar to Editor)

• Cannot install plugins or change site settings

Consideration: If the user primarily manages the store, keep them as Shop Manager rather than downgrading to Editor. This preserves their WooCommerce access.

When to Downgrade Shop Managers

If they no longer need store access:

• Change to Editor (content only)

• Or Subscriber (minimal access)

---

Security Benefits of Changing Administrator to Editor

1. Prevents Plugin Vulnerabilities

Editors cannot install plugins, eliminating risk from:

• Nulled or pirated plugins

• Malicious code in free plugins

• Outdated plugins with known exploits

2. Blocks Theme Exploits

Editors cannot install or edit themes, preventing:

• Backdoor code in theme files

• Vulnerable theme frameworks

• Unauthorized theme modifications

3. Stops User Proliferation

Editors cannot create new Administrator accounts, preventing:

• Privilege escalation attacks

• Unauthorized backdoor accounts

• Accidental overpermissioning

4. Protects Site Configuration

Editors cannot change critical settings:

• Permalinks (SEO impact)

• Reading settings (site visibility)

• General settings (site URL, email)

• Privacy and compliance settings

5. Reduces Phishing Impact

If an Editor’s credentials are compromised:

• Attackers can only modify content

• Cannot install malware via plugins

• Cannot create backdoor accounts

• Cannot change site configuration

See Post: WordPress access denied

---

Common Mistakes to Avoid

Downgrading the Only Administrator

This locks you out of critical functions. Always ensure at least 2–3 trusted Administrators remain.

Not Communicating the Change

Team members may feel demoted or confused. Explain the security rationale clearly.

Downgrading Without Testing

Verify they can still perform their job functions. Some workflows may require limited admin access.

Ignoring Plugin-Specific Roles

Some plugins (membership, LMS, e-commerce) add custom capabilities. Review these before downgrading.

Forgetting to Update Documentation

Keep your user access records current. Outdated documentation creates confusion during audits or incidents.

Reverting Without Reason

If they request Administrator access again, evaluate carefully. Don’t revert just to avoid inconvenience.

---

Troubleshooting: Issues After Changing to Editor

User Cannot Publish Posts

Cause: Role change didn’t save correctly, or plugin conflict.

Fix: Re-edit the user profile and confirm Editor role is selected. Clear cache if needed.

User Loses Access to Custom Post Types

Cause: Some custom post types require specific capabilities beyond Editor defaults.

Fix: Use a plugin like User Role Editor to grant specific capabilities (e.g., edit_products for WooCommerce).

User Reports Missing Menu Items

Cause: Editors don’t see Plugins, Themes, Users, Tools, or Settings menus—this is normal.

Fix: Explain that these are Administrator-only areas. Provide a contact for technical requests.

Cannot Reverse the Change

Cause: You downgraded your own account or the only Administrator.

Fix: Use WP-CLI or phpMyAdmin to restore Administrator access (see Method 4 or 5 above).

User Cannot Upload Files

Cause: Rare permission issue or plugin conflict.

Fix: Verify the Editor role includes upload_files capability. Use User Role Editor to add it if missing.

---

When NOT to Change Administrator to Editor

They Manage Plugins or Themes

If they’re responsible for:

• Plugin installation and updates

• Theme customization

• Site performance optimization

Keep them as Administrator or create a custom role with specific capabilities.

They Handle User Management

If they need to:

• Create or manage user accounts

• Onboard new team members

• Handle access requests

They require Administrator or a custom role with edit_users capability.

They Configure Site Settings

If they manage:

• SEO settings (Yoast, RankMath)

• Caching and performance plugins

• Backup and security configurations

These often require Administrator access.

They’re the Site Owner

Site owners should retain Administrator access for full control, even if they delegate daily tasks.

Alternative: Create a custom “Site Owner” role with all capabilities except user management, if desired.

---

Best Practices for Managing Administrator Access

Limit to 2–3 People Maximum

Ideal Administrator count:

• Site owner

• Lead developer or technical manager

• Optional: Trusted agency or maintenance provider

More than 3 significantly increases risk.

Use Editors for Content Teams

Content creators, writers, and marketers typically need Editor access, not Administrator.

Create Custom Roles for Specific Needs

For users who need more than Editor but less than Administrator:

• Use User Role Editor or Members plugin

• Grant only necessary capabilities

• Document the custom role’s purpose

Review Administrator Access Quarterly

Schedule quarterly audits to:

• Verify all Administrators still need access

• Downgrade former team members

• Remove unused or suspicious accounts

Internal-link proposal: Link “WordPress Role Security Checklist” to your role-audit guide on wprole.com.

Enable Two-Factor Authentication (2FA)

For remaining Administrators:

• Require 2FA using Wordfence, WP 2FA, or host tools

• This adds critical protection even if passwords are compromised

Document Access Decisions

Keep records of:

• Who has Administrator access

• Why they need it

• When it was granted

• When it should be reviewed

---

How to Verify the Role Change Was Successful

Check the Users List

Go to Users → All Users and confirm:

• The user’s role column now shows “Editor”

• They no longer appear when filtering by “Administrator”

Test Their Access

Ask the user to:

• Try accessing Plugins menu (should be hidden)

• Try accessing Themes menu (should be hidden)

• Try accessing Users menu (should be hidden)

• Try publishing a post (should work)

Review Activity Logs

If you use activity logging plugins:

• Check for any role-related errors

• Verify the change is recorded in audit logs

Confirm Capabilities

Use a plugin like User Role Editor to view their exact capabilities and confirm Administrator privileges are removed.

---

Frequently Asked Questions

Can I change my own Administrator account to Editor?

Technically yes, but it’s not recommended. If you’re the only Administrator, you’ll lock yourself out. If you must, ensure another Administrator exists first, or use WP-CLI to reverse it.

Will changing Administrator to Editor delete their content?

No. Their posts, pages, and media remain intact. Only their permissions change, not their existing content.

Can I change an Editor back to Administrator?

Yes. Follow the same steps in reverse: Users → All Users → Edit → Select Administrator → Update User.

What happens if I change the only Administrator to Editor?

WordPress typically prevents this via the dashboard, but if done via WP-CLI or database, you’ll lose access to Administrator functions. Use WP-CLI or phpMyAdmin to restore access.

Does changing to Editor affect WooCommerce access?

Yes. Editors cannot manage WooCommerce settings, orders, or products. Use the Shop Manager role for e-commerce staff instead.

Can Editors install plugins if I give them permission?

No. The Editor role does not include install_plugins capability. You’d need to create a custom role with that specific capability using User Role Editor.

How do I change multiple Administrators to Editors at once?

Use the Bulk Actions method: filter by Administrator role, select users, choose “Change role to… → Editor,” and click Change.

Will the user be notified when I change their role?

No. WordPress doesn’t send automatic notifications for role changes. Inform them manually to avoid confusion.

Can I schedule automatic role downgrades?

Not natively. Use a plugin like User Role Editor with automation features, or create a custom script with WP-CLI.

What’s the difference between Editor and Author?

Editors can edit and delete anyone’s posts; Authors can only manage their own. Editors are better for content managers; Authors for individual writers.

---