The administrator list on a site that has been around a while collects ghosts: a contractor from two years ago, a plugin’s demo account, a login nobody can place. Every one of them is a full key to the site. This has the agent lay them all out with context so you can decide who keeps access, and it will not remove a single one until you say so.
Help me audit who has administrator access on this site, and don't change asingle account until I approve it.
First pass, read only: list every user with the administrator role and, foreach one, pull their details, when they registered, and how much content theyown. Hand me a table with a short note on which ones look stale or unfamiliar,the accounts nobody recognizes or that haven't done anything in ages.
I'll tell you what to do with each. For the ones I want to keep but downgrade,lower their role. For the ones I want gone, delete them and reassign whatevercontent they own to [me / a named editor]. Do the safe downgrades first, thenthe deletions, a few at a time, and pause before each deletion to confirm.
You can't delete me or the last administrator standing, so there's a floorunder this no matter what I ask. When you're finished, list every account youdowngraded or removed and where their content went.Why this is safe to run
The whole first pass is reads, so you get the full roster with context before anything happens to an account. Reading users, downgrading a role, and deleting a user are separate abilities with separate switches, so “don’t change anything” is enforced by the plugin, not just trusted: if you never enabled delete-user, the agent cannot remove an account even on request. The plugin refuses to delete the account the agent is acting as, or the last administrator, so you cannot lock yourself out. Downgrading a role is reversible and gets done first; deleting is permanent, so the flow reassigns each removed account’s content to a user you name and pauses for a yes before every deletion. Every step lands in the Activity Log.
Already connected? Skip the paste. Ask your agent for the “audit stale administrators” recipe and it runs the same read-first, approve-each flow across your own admin list.