When a person no longer needs WordPress access, remove or restrict the account while preserving content that belongs to the website. Review the deletion confirmation carefully because deleting a user and deleting their content are different decisions.
IN THIS ARTICLE
01 Review ownership and dependencies
Identify the account's posts, pages, uploaded media and any plugin-specific records. Choose a suitable existing user to receive content attribution where needed. Back up the site before removing an account with substantial or business-critical data.
Check external integrations, application passwords and scheduled processes tied to the account. Removing normal login access may interrupt an integration, while a third-party service can retain separate credentials that need revocation.
02 Remove the account deliberately
- Sign in through a separate authorised administrator account.
- Open Users > All Users and confirm the exact user being removed.
- Use Delete where appropriate and read the content-handling choices.
- Choose to attribute retained content to the intended user rather than deleting it, when that matches the plan.
- Confirm only after reviewing the account and destination attribution.
Confirm the expected result
Open representative posts and pages, check author labels and confirm media remains available. Test any business workflow previously maintained by the departing user. Review the user list to ensure the account is no longer able to access the site as intended.
On Multisite, removing a user from one site is different from deleting the network user. Network-wide deletion can affect several sites, so the Super Admin must review the broader consequences.
What if I am unsure which content belongs to the user?
If you do not yet know which plugin records depend on the user, first restrict access through a suitable reviewed method and complete the inventory. Do not delete the account simply to change the public author name; a display-name or author-assignment edit may be the correct task.
If content was deleted accidentally, stop further changes and plan recovery from the narrowest suitable source. A full database restore can overwrite newer orders and edits. Provide the user ID, deletion time and affected content when requesting help, without sharing the former user's password.