How to Admin a WordPress Multisite Network

admin

5 hours ago

WordPress multisite administration guide showing Network Admin sites users themes plugins updates and backups

Administering WordPress multisite is mostly about governance. The buttons are easy. The hard part is deciding who can create sites, which plugins are allowed, which themes are safe, how backups work, and how one broken subsite will be handled without dragging the whole network into panic.

WordPress Network Admin is visible to super admins after a network is created. From there you manage the network dashboard, sites, users, themes, plugins, settings, and updates.

Super admin rules

Give super admin access only to people who understand the whole network risk.
Use individual accounts, not shared admin logins.
Require strong passwords and two-factor authentication where your security stack supports it.
Review super admins after staff changes, client offboarding, or agency changes.

Sites screen

Use Network Admin > Sites to add sites, edit site settings, assign users, enable themes for a specific site, archive inactive sites, and delete only after a backup and retention decision.

Name sites clearly so support staff know what belongs to whom.
Keep a simple owner/contact field in your internal documentation.
Document mapped domains, SSL source, DNS provider, and cache rules for each public site.
Archive instead of deleting when there is any legal, billing, school-year, or client-history reason to keep the site.

Users

Users can exist on the network and be assigned to individual sites. That is powerful and also easy to misunderstand. A user who can edit one subsite does not automatically need access to every subsite.

Use the lowest practical role for each site.
Remove users from subsites they no longer manage.
Review agency, contractor, and old employee access regularly.
Be careful with shared customers who have accounts on more than one subsite.

Themes and plugins

Network-enabled does not mean harmless. A plugin network-activated everywhere can break every site at once. A theme enabled network-wide may still need site-level testing.

Network activate only plugins that truly belong everywhere.
Enable optional plugins site by site when possible.
Keep builders, ecommerce plugins, LMS plugins, membership plugins, and security plugins on a staged update schedule.
Document which themes are allowed and why.

Updates and Upgrade Network

After updating WordPress core on multisite, use Network Admin > Updates > Upgrade Network. WordPress documents that this process applies network database changes across sites after a core update.

Back up the whole network.
Test updates on a network staging copy.
Update plugins and themes in batches.
Update WordPress core.
Run Upgrade Network.
Spot-check the main site plus representative subsites.

Backups and restores

Multisite backup and restore planning matters more than it does on a single site because one database and one codebase can serve many public experiences. Know whether your backup tool can restore the full network, one subsite, files only, database only, or a staging copy.

Monthly admin checklist

Review super admins, new users, inactive users, and public sites.
Check plugin/theme update status and vulnerability notices.
Verify backups and at least one restore path.
Review storage, inodes, uploads, and large media folders.
Check domain mapping, SSL expiration, DNS, sitemap health, and cache rules.
Archive or remove unused test sites after the retention decision is documented.