Manage GPL

← Whitelabel & branding

Whitelabel & branding

Override whitelabel per site

For specific clients who need their own branding, override the global whitelabel profile on a per-site basis without affecting your other sites.

Updated

The global whitelabel profile covers the common case: one agency, one brand, all clients see the same plugin name. If you have a client that needs their own brand name (they're reselling your service, they want to present the whole thing as "their" tool, etc.), you can override the profile for just that site.

How precedence works

  • If a site has a per-site whitelabel profile, that applies on the site.
  • Otherwise, the global profile (if set) applies.
  • If neither is set, the default Manage GPL branding applies.

Set a per-site override

  1. Open the site's detail page.
  2. Click the Whitelabel tab.
  3. You'll see a note showing what the site is currently inheriting (from the global profile, if any).
  4. Fill in the per-site fields with the client-specific branding.
  5. Click Save.

The connector on that site receives the updated branding and reflects it on the next wp-admin page load. The global profile is untouched and still applies to all your other sites.

Revert a per-site override

On the site's Whitelabel tab, click Delete site profile. The site falls back to the global profile (or Manage GPL default, if no global exists).

If the rebrand doesn't appear on the site

Manage GPL pushes whitelabel changes immediately, but the push can fail if the site is temporarily unreachable. The global Settings → Whitelabel page lists every site that's received a push and surfaces a Retry button next to any row whose last push failed. The connector also self-heals every 6 hours: it polls Manage GPL for its current whitelabel profile and syncs if it doesn't match, so even without a manual retry it'll catch up eventually.

Real example

Agency "Acme Web Co." has a global whitelabel:

  • Plugin name: "Acme Site Manager"
  • Author: "Acme Web Co."

One of their clients, "Bright Studio", resells websites to their own end customers under their brand. Acme sets a per-site override on Bright Studio's sites:

  • Plugin name: "Bright Studio Care"
  • Author: "Bright Studio"

Now Bright Studio's end customers see the plugin as Bright Studio's, while Acme's other clients still see Acme's brand.

Is something wrong with this article?

Tell us so we can fix it — outdated info, broken steps, wrong numbers, anything.

Report an issue

Article: Override whitelabel per site

Still stuck?

If this article didn't solve it, open a ticket and we'll help.

Open a support ticket