What exactly gets rebranded in the WordPress admin

This is a reference list of every place the Manage GPL connector appears in a client's WordPress admin, whether whitelabel controls it, and what they'll see with/without whitelabel.

Plugins list (wp-admin/plugins.php)

Controlled:

• Plugin name column — configurable via whitelabel Plugin name field.
• Plugin description column — configurable via whitelabel Description.
• "Author" link below the plugin — configurable via Author + Author URI.
• Row visibility — Hide from Plugins list removes the row entirely (the plugin stays active; the client just can't see it).

Not controlled:

• The plugin file path (managegpl-connect/managegpl-connect.php). Visible in "View details" and in the "Edit file" screen. Hidden if plugin-editing is disabled (it usually is on managed hosts).

Admin bar (top of every admin page)

The connector doesn't add an admin bar item. Nothing to rebrand.

Plugin's own settings screen

Currently, the connector exposes a minimal settings screen under the Plugins list's "Settings" link (just for pairing status and manual disconnect). This screen uses the whitelabel Plugin name in its title.

Update-related notifications

When the connector runs a plugin update, the WordPress core fires "Plugin updated" notices. These:

• Appear on the Updates screen as an ephemeral success/failure notice.
• Are rendered by WordPress core, not by the connector.
• Say generic things like "Plugin updated successfully." They don't mention Manage GPL or your rebrand.

Emails from WordPress

WordPress's core sends "Your site has been updated to WordPress X" and "Auto-update complete" emails to the site admin. These:

• Don't reference the connector.
• Can be suppressed via standard WordPress filters (auto_plugin_theme_update_email) from a must-use plugin if you want to reroute them to yourself.

Emails from premium plugin vendors

When the connector updates a premium plugin, some vendors send renewal-notice or release-note emails from their own servers to the site's admin email. These aren't part of WordPress or the connector — they come directly from the vendor. The only way to stop them is to point the site's admin email to an address you control (e.g., [email protected]).

Things we can't hide without risk

• The plugin file on the server (renaming it would break the upgrader).
• A determined client running SHOW PROCESSLIST or SELECT * FROM wp_options can see the connector's options. Whitelabel isn't encryption.

If hiding-from-technical-clients is critical, consider a white-glove managed service rather than a resold WordPress admin.