Who Changed It/Teams

Change management for a WordPress site with more than one admin.

Two developers, a marketing lead, an SEO contractor and the agency that built it: five administrator accounts and no record of who does what. Here is a working routine for shared sites, the parts WordPress can enforce, and the part that needs a log.

Why shared admin access goes wrong

Nobody plans to have seven administrators. Accounts accumulate because Administrator is the only role that reliably "just works", and because removing access feels ruder than granting it. The trouble is what the role includes. Every administrator can install code, create other administrators, change where password resets are sent, and edit theme files in the browser.

WordPress records almost none of that. Revisions name who saved a post. Nothing names who deactivated a plugin, changed a setting or promoted an account. So when the site breaks on a Friday, the investigation is a group chat.

Start with the parts WordPress can enforce

A change routine light enough to survive

Formal change control fails on small teams because it costs more than the changes do. Three habits cover most of the benefit:

  1. Say it before you do it. One line in the team channel: "updating WooCommerce on production at 14:00". It takes ten seconds and removes most surprises.
  2. Plugins, themes and settings on staging first when the site earns money.
  3. A weekly look at what actually changed, compared against what was announced. This is the step that needs a record.

The record: what changed, whether or not anyone announced it

Who Changed It writes down each administrative change as it happens, with the user, the IP address and the old and new values. For a shared site the useful part is what it does with them:

#2207 · 16:41 · seo-contractor · user_role_changed · m.lang: editor → administrator — dangerous

Contractors and freelancers

A log changes the contractor relationship in both directions. You can see what was done under the account you paid for, and the contractor can show that the thing that broke was not theirs. Tell them the log exists when you hand over the login. It is fairer, in the EU it is generally required, and people are more careful when they know changes are attributed.

At the end of the engagement, filter the log to their account, export it, and keep the file with the invoice. Then delete or downgrade the account. Removing a user does not remove their history; the rows stay under the username they were recorded with.

Who watches the watchers

On a shared site, some of the people in the log are the same people who could edit it. Three settings deal with that:

Changes to the plugin's own settings, purges and redactions are themselves logged and cannot be muted.

What a log does not fix

It will not stop a bad change, approve a good one, or undo anything. It cannot see edits made over SFTP or directly in the database. And it does not replace the conversation about who should have Administrator at all. It makes that conversation shorter, because you can look at what each account has actually done in the last ninety days.

Common questions

How do I see which admin changed something in WordPress?
WordPress only records this for content, through revisions. For plugins, themes, settings, users and roles you need an activity log installed before the change happens. Who Changed It records each of those with the user, the IP address and the old and new values.
How many administrators should a WordPress site have?
As few as the maintenance needs, and each one a named individual. Most content and SEO work can be done as Editor. Every administrator can install code and create further administrators, so each extra account is a larger risk than it looks.
How do I keep track of what a freelancer changed on my site?
Give the freelancer their own account, tell them activity is logged, and review the log filtered to that account. At the end of the work, export that history and remove or downgrade the account. The log entries remain after the user is deleted.
Can another administrator delete or edit the activity log?
They can try. Settings can be restricted to a single account so others cannot purge or mute, and purges are logged as dangerous events that cannot be muted. Rows removed directly from the database break the hash chain and are reported on the next verification.
Do I have to tell staff and contractors that their changes are logged?
In the EU, generally yes: transparency is part of processing their data lawfully, and some countries add employment-law requirements such as works-council consultation. Outside the EU it is still good practice. Telling people also tends to make them more careful.