Black Friday: 50% off. Your first year on any annual plan, until 1 December. See the dealFirst year on annual plans, until 1 December
WPClientHub V2 is live. Fewer plugins on your client sites: caching, forms and image optimization now come built into WPClientHub One. See what’s newCaching, forms and images, built in. See what’s new
Sign in Start free

← Docs  /  Getting started

White-label WPClientHub One

Updated 2026-10-06

Your agency’s name, author, menu label and icon on the WPClientHub One plugin on every client site — and what can’t change. Agency and above.

Browse documentation

What it does

The WPClientHub One plugin is the one part of WPClientHub your clients can see: it sits in every site’s Plugins list and has a settings page in wp-admin. With the white-label plugin it shows there under your agency’s name — its name, description, author and link, its menu label and icon, and your support contact — on every connected site at once. You can also hide it from the Plugins list for everyone except one WordPress login you name.

It is part of Agency and Scale (the 14-day Agency trial includes it). Each site needs the WPClientHub One plugin 0.13.0 or newer; an older plugin is listed as Plugin too old and keeps showing the standard plugin until it is updated.

Set it up

  1. Go to Settings → White label and switch WPClientHub One plugin on.
  2. Fill in how it is listed: Plugin name (required), and optionally a description, an author (your agency name is used when empty) and the author’s website.
  3. Choose the admin menu entry: a label, and whether it sits under Settings or as its own menu item — with WordPress’s default icon, a Dashicon from the picker, or your own SVG.
  4. Decide who sees it: hide it from the Plugins list, hide its settings page from the menu, and replace “WPClientHub” in the plugin’s own text. Name the WordPress user (username or email) who should still see it — normally your agency’s own login on every site.
  5. Add a support link or email for your clients.
  6. Watch the live preview of the Plugins row and the admin menu — switch it between “Other administrators” and your named user — and press Save and send to sites.

Connected sites pick it up within a minute; one that is offline gets it on its next sync. The Sites list underneath shows each site’s state, and Send to all sites now sends it again.

What changes on a client site

  • Plugins → Installed Plugins: the plugin’s name, description, author and “Visit plugin site” link are yours, plus a Support link when you set one. Links never point at wpclienthub.com while the white label is on.
  • Dashboard → Updates and WordPress’s own update messages (“… updated successfully”, the automatic-update email) use your plugin name, and WordPress’s generic plugin icon instead of ours.
  • The admin menu: your label under Settings, or a top-level item with your icon. The page keeps its address (options-general.php?page=wpclienthub-connector) and its title is your plugin name.
  • The plugin’s own text — its notices, its settings page and the page shown when a one-click sign-in link has expired — uses your plugin name; with Replace “WPClientHub” on, every other mention says your agency name instead.
  • The plugin’s settings page shows your support contact (“Questions about this site? Contact Acme Digital”) and, when the plugin is hidden, says so plainly and how to show it again.

The plugin sends no emails of its own. The emails WordPress itself sends for a new account or a password reset never mentioned WPClientHub to begin with.

What can’t change, and why

  • The plugin’s folder, file and slug (wpclienthub-connector). WordPress and the update channel find the plugin by them; renaming them would break updates. They appear in the plugin’s file path, in WP-CLI and on WordPress’s Site Health → Info screen.
  • Its WordPress.org listing and readme. Sites that installed it from the directory see the directory’s own “View details” page, which describes WPClientHub. That page belongs to WordPress.org and stays honest about who makes the plugin.
  • The REST address /wp-json/wpclienthub/v1/… — briefly visible in the address bar during a one-click sign-in — and the wpch_ option names and the wpch-vault backup folder.
  • The hub address shown on the plugin’s settings page (for example app.wpclienthub.com). A site owner should always be able to see where their site is connected.
  • WP-CLI always shows the real plugin, so wp plugin list and wp plugin deactivate wpclienthub-connector keep working.
  • A site administrator’s final say — see The escape hatch.

Hiding the plugin

Hide it from the Plugins list removes the plugin’s row — and with it the Deactivate and Delete links — for every user except the WordPress user you name (matched by username or email, any case, on every site). The named user sees the row as usual, with a note that it is hidden from everyone else. If you name nobody, it is hidden from everyone.

Hide its settings page from the menu takes the entry out of the admin menu for everyone except the named user. The page still opens from its address, so a site owner can always disconnect the site.

Hiding is a convenience for a tidy client dashboard, not a lock: the plugin can still be deactivated with WP-CLI, and an administrator can reveal it at any time.

The escape hatch: WPCH_SHOW_CONNECTOR

An administrator of a site can always switch the white label off for that site by adding one line to wp-config.php:

define( 'WPCH_SHOW_CONNECTOR', true );

The plugin then shows under its real name, in its usual place, with its normal links, for everyone — and its settings page explains why. Nothing else changes: the site stays connected and keeps your settings, which come back when the line is removed. WPClientHub is told: the site shows as Shown under its real name in Settings → White label.

We built it this way on purpose. A plugin must never be impossible for the people who own a site to find or remove — that is both the WordPress.org plugin guidelines and plain honesty toward your clients.

Per-site status

StatusMeaning
AppliedThe site reported back the exact settings you saved.
PendingSent, or waiting for the site’s next sync.
Not appliedThe site could not be reached or refused it; the reason is shown, and it is tried again on the next sync.
Plugin too oldThe site runs a plugin older than 0.13.0. Update it from Updates → WPClientHub One.
Not connectedThe site is disconnected; it gets the settings when it is connected again.
Shown under its real nameAn administrator set WPCH_SHOW_CONNECTOR on that site.
Standard pluginThe white label is off (or your plan doesn’t include it), and the site shows the normal plugin.

“Applied” is never a guess: every sync carries a fingerprint of the settings the site is using, and WPClientHub compares it with yours. Sending the same settings again changes nothing on the site.

Menu icons

  • Dashicons: pick from the shield, gear, globe, wrench, lock, lifebuoy and a dozen more. The preview draws close approximations; wp-admin uses WordPress’s own icon font.
  • Your SVG: up to 20 KB. It is cleaned before it is stored and cleaned again on each site: only shapes, groups, gradients and clip paths survive, with their geometry and colours. Scripts, styles, event handlers, links, embedded images, external references and anything with a DOCTYPE are removed or refused, and you are told what was removed. The icon travels inside the signed settings; a site never loads anything from elsewhere to draw it.
  • WordPress recolours menu icons to match the admin colour scheme, so a single-colour icon works best.

Plans and downgrades

The white-label plugin is part of Agency and Scale, and of the Agency trial. On Free and Studio, Settings → White label shows what it does and an upgrade link.

If your plan drops below Agency — or the trial ends — every site goes back to the standard WPClientHub One straight away, or on its next sync if it was offline. Your settings are kept, shown as paused, and go back out to every site when you upgrade again.

Who can change it

RoleWhite label
Owner, AdminChange the settings, upload an icon, send to all sites
Tech, ViewerSee the settings and every site’s status

Every save is written to the Activity Log with who made it and the settings revision.

Limits & defaults

SettingDefault
PlansAgency, Scale (and the Agency trial)
Plugin versionWPClientHub One 0.13.0 or newer on the site
Plugin name / author / menu labelUp to 80 / 80 / 40 characters, plain text
DescriptionUp to 300 characters; when empty, “Connects this site to your agency for updates, backups, monitoring and support.”
SVG iconUp to 20 KB, sanitized twice
Applies toEvery site of the organization; per-site settings are not available
DeliveryWithin a minute of saving, else on the site’s next sync
Downgrading below AgencySites show the standard plugin; settings are kept

Troubleshooting

A site says “Plugin too old”
It runs a WPClientHub One plugin older than 0.13.0. Update it from Updates → WPClientHub One (or the site’s Plugins page); it picks up the white label on its next sync.
A site shows the plugin under its real name
An administrator of that site added WPCH_SHOW_CONNECTOR to wp-config.php. That is their call to make; the site stays connected and your settings come back if the line is removed.
My client can’t find the plugin to deactivate it
It is hidden from the Plugins list for everyone but your named user. They can add define( 'WPCH_SHOW_CONNECTOR', true ); to wp-config.php, or run wp plugin deactivate wpclienthub-connector, or you can switch hiding off in Settings → White label.
My SVG icon was refused
It is larger than 20 KB, declares a DOCTYPE, has no viewBox, or has nothing drawable left once scripts and external references are removed. Export a simple single-colour SVG and try again.
I switched the white label off but a site still shows it
That site was offline when you saved. It goes back to the standard plugin on its next sync; Send to all sites now tries straight away.