Manage WordPress users on every site without logging into any of them
List, search, create, edit, re-role and delete WordPress users on any connected site from one screen. Add a contractor to fourteen sites in one operation, and remove them from all of them just as quickly.
Available now in early access. Included on every plan.
Multiply the routine
A new developer joins and needs an account on every client site. A contractor finishes and their administrator account stays behind on eleven of them. A client asks you to downgrade an ex-employee from editor to subscriber. None of this is difficult. All of it is repetitive, and repetitive work across thirty sites is where accounts get missed.
The accounts that get missed are the ones that matter. An orphaned administrator on a site nobody checks is a standing invitation, and it will not show up in any vulnerability feed because it is not a vulnerability. It is just a user nobody removed.
What goes wrong without this
- Departed staff keeping administrator accounts on client sites
- One shared login passed around because per-person accounts are too much effort
- Role changes applied to some sites and forgotten on others
- Nobody able to answer which sites a given person can reach
- Users deleted without deciding what happens to their posts
Live user administration through the connector
Every action runs against the site itself over the signed connector channel. Nothing here works from a cached copy that might be hours out of date.
Read from the site, not a cache
Listing, searching, filtering by role and paging all run against the site’s real user table at that moment. What you see is what WordPress currently holds.
Roles come from that site
Available roles are read from the site itself, so custom roles added by a plugin or theme appear alongside the standard ones. You cannot assign a role that does not exist there.
Deletion asks the right question first
WordPress makes you decide what happens to content owned by a user you remove. Reassignment candidates are fetched from the site so you pick a real destination account rather than losing posts.
Every change is recorded
Creates, edits, role changes and deletions are written to the activity log with the person who did it, the site, and the result WordPress returned.
What you can do
All of it from the website detail view, or across many sites at once from one screen.
Full user administration
List with search, filter by role, sort and page through users on any connected site. Open one to view or edit its profile fields, password and role.
Add one user to many sites
Pick an account, pick the sites, and set the role it should get. The operation runs site by site and reports the result for each one rather than as a single pass or fail.
Remove across the portfolio
The same in reverse. Offboard someone from every site they can reach in one action instead of working down a list and hoping you got them all.
Find who is where
See the accounts that exist across multiple sites, so you can answer which sites a person can reach without opening each one.
Credentials handled properly
A generated password is delivered by email rather than shown in the interface or pasted into chat, and it is stored encrypted with an expiry rather than kept indefinitely.
Operations you can resume
If a site was unreachable mid-run, the operation records that and retries only the sites that failed. An interrupted rollout is finished, not restarted.
What this does not do
This manages WordPress users through WordPress’ own user APIs. It does not invent a parallel permission system, and it does not change what a WordPress role can do. If a plugin has given the editor role an unusual capability on one site, that is still true after a change made here.
It is also not the same thing as WPCentrify team access. Team roles govern who can use WPCentrify. These are the WordPress accounts on the sites themselves. Keeping the two separate is deliberate: someone can be allowed to manage users on a client site without being allowed to disconnect it.
Worth knowing
- Role assignment is at role level, not individual capability level
- A site has to be connected and reachable for changes to apply
- Deleting a user is a WordPress deletion and cannot be undone from here
- Team access to WPCentrify is a separate permission system
- Bulk operations report per site, so a partial run is visible rather than silent
Related
Questions about WordPress user management
No. The connector authenticates with a scoped key unique to each site and signs every instruction. There is no standing WPCentrify administrator account on a site, and deactivating the connector ends platform access immediately.
You choose. WordPress requires a decision about content owned by a deleted account, so the candidates for reassignment are read from the site and offered before the deletion runs. You can reassign to another user rather than losing the content.
Yes. Roles are read from each site rather than assumed, so a custom role created by WooCommerce, a membership plugin or your own code appears in the list for that site and can be assigned like any other.
Yes, for that operation. One generated password is used across the sites in the run and emailed to the person once, which is what makes the account usable without twelve separate emails. It is stored encrypted with an expiry rather than kept indefinitely.
That site is marked failed with the reason, and the rest of the run continues. You can retry the operation later and only the sites that did not complete are attempted again.
Stop opening thirty wp-admins to change one role
Full WordPress user administration across every connected site, with bulk rollout, proper credential handling and a record of every change.
Free during early access. No credit card required.