WordPress Login Redirect Loop: Fix Being Sent Back to wp-login
You type the right password and WordPress sends you back to the login page. The cause is usually cookies, address settings, caching…
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.
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.
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.
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.

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.
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.
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.
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.
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.
An Editor can manage and publish other people’s posts. An Author can publish and manage only their own.
No. A Contributor can write and edit their own posts, but an Editor or Administrator has to publish them.
As few as possible. For many small business sites, one or two trusted people is enough.
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
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.
You type the right password and WordPress sends you back to the login page. The cause is usually cookies, address settings, caching…
Old PHP stops getting fixes, but a rushed update can break plugins. Learn to check your version, test compatibility and switch PHP…
A staging site lets you test updates on a copy before customers see them. Learn how to create one, lock it down…
Black FridayCyber Monday sale
Before you go,
Our biggest discount of the year on the first payment of every maintenance plan.
BF2026 at checkout