Your brand, on every surface
You built the community. Your members recognize your name, not the name of the plugin running underneath it. White Label makes that reality complete by stripping Jetonomy branding from the three places it shows up: the frontend pages members browse, the admin sidebar your team works in, and the emails that land in members’ inboxes. Turn it on from the Extensions screen and a Branding tab appears under Settings, where all of it is controlled in one place.
On the frontend, you remove the Powered by Jetonomy footer and either replace the nav logo with your own or hide it entirely. A custom CSS field lets you apply brand colours and spacing on every community page, and because it loads after Jetonomy’s own stylesheet, your rules always win without touching a single theme file. That combination lets an agency or a SaaS make the public community read as a first-party product.
Rebrand the admin and the emails too
Branding that stops at the frontend still leaks. Members who get a notification see the plugin’s name in the email, and your team sees the plugin’s name in the sidebar. White Label covers both. In the admin, rename the top-level menu from Jetonomy to whatever fits, Community, Forum, or your product name, and set its icon to any Dashicons class. The new label follows through to the browser window title on every admin page, so even the tab reads as yours.
Email gets the same treatment. Set the from name that appears on transactional emails and digests, replace the default footer with your own text or HTML, and upload a logo shown at the top of every notification. A single accent color setting recolours the Pro-rebranded surfaces, email accents included, so your brand colour stays consistent from the community to the inbox.
Two logos, one accent, all under your control
A few settings are worth understanding because they carry the branding. The header logo is the image members actually see at the top of every page. The fallback logo is separate on purpose: it powers social share cards and stands in anywhere a logo is needed but no header logo is set. They are often different shapes, so both stay configured. The accent color gives you one global override, and the custom CSS field handles anything finer, always loading last so it wins.
All of it is reachable over the REST API through the white-label settings endpoints, which require admin capability to read or save. If you are upgrading, note that on Jetonomy 1.4.1 and newer every Branding setting applies on every render and send, the header logo, footer text, email accent, email logo, sidebar sign-in card, and admin footer included. Update both the free and Pro plugins together so all of your branding takes effect.