What WordPress Editors can’t do (that Admins can)

I thought it would be helpful to outline what WordPress Editors can’t do that admins can. I see a tendency among our clients to assign the highest user role possible when creating new user accounts to make sure a new staff member can do anything they’ll be needed to do.

In the case of WordPress the highest user role is “Admin” (or “Super Admin” on a Network site). Not only is it unnecessary to use the ‘admin’ role as the go-to user role, but it can put your website at risk. Even users with the best intentions, if not properly trained in WordPress, can make mistakes and cause problems for your website.

I strongly recommend assigning the highest level of Editor to any staff you add as users to your website. I explain a bit more about WordPress user roles in my article, 7 Tips for Setting WordPress User Roles

WordPress functions that Editors can NOT do (but Admin users can)

Network tasks (on a WordPress Multisite install):

  • configure the network,
  • add/remove network sites, users, plugins, themes and options.

Network sub-site or single site tasks:

  • Plugins: install, activate, update, edit, delete
  • Themes: install, switch between themes, delete, edit theme options, edit theme files
  • Users: List users, change user roles, create new users, edit users, delete users
  • Manage site options
  • Update core system
  • Edit the dashboard
  • Import/export posts, pages, etc.

I think you’ll agree with me that these tasks are best in the hands of those more experienced. User Roles within WordPress are fantastic tools when used properly. I encourage you to review the user roles on your WordPress site and reconsider the admin roles, especially.

Questions? We can help. Drop me a note using our contact form