← All guides

White-label 7 min read

White-label a Jetonomy community for your clients

A step-by-step guide for agencies and resellers: brand the community and its emails from the free Appearance and Email settings, then use Pro White Label to rename Jetonomy in the admin your client's team works in.

The Jetonomy admin dashboard rebranded with a custom logo and menu label for a client

If you build communities for clients, borrowed branding is a problem. A client pays you to deliver their community, then finds a Jetonomy menu in their admin sidebar, a Jetonomy name on their Plugins page, and plugin-default emails landing in their members’ inboxes. That undercuts the work. The same problem hits SaaS products embedding community features under their own name.

The rebrand splits cleanly across two places, and knowing the split saves time. The member-facing branding (the logo, the accent colour, custom CSS, and the emails) lives in the free plugin’s settings, so it works on any Jetonomy site. Pro White Label handles what is left: it renames Jetonomy in the admin menu, the menu icon, the Plugins page and the admin footer. This guide walks both halves as an agency would run them, then shows how to script the result across client sites.

What a client will and will not see rebranded

Be clear with the client about the edges before you promise anything. The front-end templates do not print a “Powered by” line, so there is nothing to remove there. The logo setting feeds the mobile app and notification emails, but the web header does not draw it, so a client who expects their logo at the top of every community page needs a theme-level change instead.

Pro White Label is also limited to the admin side. It changes the menu label, the menu icon, the plugin name and the footer text that your client’s team sees in wp-admin. It does not touch what members see on the public pages. That is the right split for most agency work, because members were never looking at the admin anyway.

If you want the words themselves to match the client’s world, the free plugin lets you rename the built-in terms. Under Settings, then General, the Terminology fields rename Space, Topic, Reply, Member and Category, so a course business can say Cohort and Question while a software vendor says Channel and Thread.

Brand the community from Settings, Appearance

The Appearance tab under Jetonomy, then Settings, is where the community picks up the client’s identity. Everything here is in the free plugin.

Set the logo. There is one Logo setting. Paste the client’s logo URL, ideally a transparent PNG or an SVG at 512 pixels or more on its longest side. The mobile app shows it on its login and header screens, and it is the brand mark Jetonomy uses wherever one is needed. Leave it empty and the Community Title shows as text instead.

Set the accent colour. The Accent field in the Color Palette card recolours buttons, links, active states, and notification emails in one place. Fonts and colours follow the active theme by default, so leave the accent alone if the theme already carries the client’s palette, or set it when the theme gives Jetonomy nothing to inherit.

Add custom CSS. The Custom CSS field injects your rules into the community frontend. It is added after Jetonomy’s own stylesheet, so you can override spacing, colours, and details without editing or forking the client’s theme. That keeps the handover clean and survives theme updates.

Brand the emails from Settings, Email

Notification emails are the branding leak clients notice last and members notice first. Under Settings, then Email, set three things:

  • From Name. It defaults to the site name; change it to the client’s brand.
  • Email Logo. A separate logo for the top of notification emails. The field recommends about 200 by 40 pixels, PNG or SVG. Leave it empty to show the site name as text.
  • Footer Text. Replace the default footer line with the client’s own wording.

Combined with the accent colour, every notification a member receives looks like it came from the client, not from a plugin they have never heard of.

Rename Jetonomy in the admin with Pro White Label

The client’s team works in wp-admin every day, and that is where the plugin name still shows. Pro White Label fixes it. In the client’s WordPress admin, go to Jetonomy, then Extensions, find White Label, and click Enable. A Branding tab appears under Jetonomy, then Settings, with four fields:

  • Brand Name. Replaces “Jetonomy” in the admin menu, on the Plugins page, and in the admin footer. It defaults to the site name if left empty.
  • Admin Menu Label. Overrides the Brand Name for the sidebar menu item only, for example Community, Forum, or the client’s product name.
  • Admin Icon. Any Dashicons class, such as dashicons-groups, or leave it blank for the default icon.
  • Admin Footer Text. The line shown in the admin footer on Jetonomy screens.

White Label needs the client’s site to run both the free plugin and Pro.

Automate it across client sites over REST

If you run more than one client community, you will not want to click through the Branding tab by hand every time. White Label exposes its settings over the REST API under the jetonomy/v1 namespace: a GET on /settings/white-label reads the current configuration and a PATCH saves it. Both routes require the manage_options capability, so only an administrator can read or change them. That lets an agency script the admin rename as part of a provisioning step and keep every site consistent without repeating the manual work. The logo, accent, CSS and email fields are ordinary Jetonomy settings, so apply those alongside it in the same provisioning run.

Fit the theme, not just the settings

Most of the visual work comes from the theme rather than from Jetonomy. The community adopts the active theme’s brand colour and fonts by default, which is why the accent field is optional on a well-built client theme. If the theme is one of ours, such as BuddyX Pro or Reign, the community picks up the same colour system with nothing to configure.

When a client needs layout changes beyond CSS, copy a template into a jetonomy folder inside the theme and edit the copy. Template overrides survive plugin updates, and they keep the customisation in the client’s theme repository where their developer expects to find it.

Right-to-left languages are supported, so an Arabic or Hebrew community does not need a separate build. Check your custom CSS in both directions if the client serves both.

Keep custom CSS small

Treat the Custom CSS field as a place for a handful of overrides, not a second stylesheet. Long blocks are hard to hand over and easy to break when the plugin changes its markup. If you find yourself writing hundreds of lines, move the work into the theme and use the field only for community-specific touches.

Extend the brand to a mobile app

The rebrand does not have to stop at the browser. On Pro, the Jetonomy mobile app can ship white-labelled too, carrying the client’s own name, icon, and colours rather than Jetonomy’s. So the identity you set for the web community can extend to a native app the client publishes under their own name. For agencies, that turns a web community deliverable into a fuller branded product without building an app from scratch.

A handover checklist you can reuse

Run the same sequence on every client site and the work stays predictable. Here is the order we would use.

  1. Install the free plugin and Pro, then enter the client’s licence key on the Settings licence tab.
  2. Create the spaces and categories the client asked for, and rename the built-in terms to their vocabulary.
  3. Open Settings, then Appearance, and set the logo, accent colour and any custom CSS.
  4. Open Settings, then Email, and set the From Name, Email Logo and Footer Text. Send yourself a test notification.
  5. Enable White Label under Jetonomy, then Extensions, and fill in the four Branding fields.
  6. Log in as an ordinary member on a phone-sized screen and read the community as a stranger would.

Keep a short note of the values you used. When the client asks for a change in six months, you will not have to hunt through tabs to find out what was set.

Licences, renewals and what happens if the client stops paying

White Label is a Pro extension, and one Pro licence covers every extension. The plans differ only by how many sites they cover, so an agency running many client communities should look at the plan that covers unlimited sites rather than buying one licence per project. The pricing page lists the current plans.

Decide up front who holds the licence, you or the client. If the client holds it and lets it lapse, Pro extensions switch off thirty days later. White Label is one of them, so the admin would show the Jetonomy name again. Nothing public breaks, because the logo, accent, CSS and email branding live in the free plugin, and the community and all of its data keep working.

For agencies the cleaner arrangement is usually to hold the licence yourself and fold the cost into a maintenance retainer. Then the rename never lapses because someone forgot to renew a card.

What your client will ask about their data

Clients rarely ask about branding first. They ask who owns the members and what happens if they leave you. The honest answer is simple. The community lives in custom tables in the client’s own WordPress database, and the members are ordinary WordPress users with one login. There is no hosted account that you or we control.

Personal data requests use the standard WordPress tools. Jetonomy registers its profile, posts and replies with the core export and erase screens, and members can delete their own account. Hand the client those instructions rather than inventing a process.

One warning belongs in the handover notes. Deleting the plugin from the Plugins screen removes its tables, so a client who clears out plugins to tidy up would lose the community. Deactivating is safe, and a database backup before any plugin housekeeping is the real protection.

Where the rest of the family fits

Jetonomy is the discussion layer, and clients often want more around it. BuddyNext is the social layer from the same team, with profiles, an activity feed and groups. With both active, the forum adopts BuddyNext’s look and BuddyNext owns the page header and navigation, so there is nothing extra to brand. On a BuddyNext site, BuddyNext also owns messaging, so do not promise Jetonomy private messaging there. The BuddyNext partner page has the detail.

Learnomy is the course plugin. With Jetonomy Pro, a space can be gated by a Learnomy course or plan, and enrolling adds the member while expiry removes them. See the Learnomy partner page.

Other pieces from the same team run beside it on the same site, such as WP Career Board for jobs, Listora for directories and Eventonomy for events. They are separate plugins you install and update yourself, and we make no promise that they share branding settings with Jetonomy. The trade is plain: a hosted platform bundles everything into one bill, while here you host and maintain each piece.

When this is the wrong tool for a client

White-labelling is not a fit for every brief. If a client needs live chat, voice rooms or video, Jetonomy does not include them, and it has no built-in Discord or Slack bridge. If they need the plugin name removed from the front end, there is nothing to remove. If they need branding beyond the admin rename, the answer is theme work. Say this at the proposal stage and you avoid the awkward conversation after the build.

It also helps to agree who answers member questions after launch. A rebranded admin does not change the fact that someone has to read the moderation queue each week, so write that duty into the maintenance agreement and name the person responsible. Clients are happiest when the handover includes a short list of what to check and how often.

Hand it over

Done properly, white-labelling a Jetonomy community is a short, contained job: set the logo, accent and CSS under Appearance, brand the emails under Email, enable Pro White Label to rename the admin, and script it over REST if you run several sites. The client gets a community that reads as their own, in the admin their team uses and in every inbox. See exactly what each tier includes on the pricing page, read the White-label feature overview for the capability summary, and if a client needs branding that goes beyond these settings, custom development can take it further.

Watch it

How to Put Your Own Brand on the Admin in Jetonomy2:37Chapters and transcript

Browse the full video library →

Common questions

What does Pro White Label actually change?

It renames Jetonomy inside wp-admin. Pro White Label has four fields: a brand name, an admin menu label, an admin menu icon, and admin footer text. Together they replace Jetonomy in the admin sidebar, on the Plugins page, and in the admin footer. The client's logo, accent colour, custom CSS and email branding are free settings under Settings, Appearance and Settings, Email.

Can I set my client's brand colours without editing their theme?

Yes, two ways and neither touches a theme file. Set the accent colour under Settings, Appearance to recolour buttons, links, active states and notification emails in one place. For finer control use the custom CSS field on the same tab, which is added after Jetonomy's own stylesheet so your rules can override its defaults.

Where does the logo setting show up?

There is one Logo setting, under Settings, Appearance. The mobile app uses it on its login and header screens, and it is the brand mark Jetonomy reaches for wherever one is needed. Notification emails have their own Email Logo field under Settings, Email.

Can I ship the client a white-labelled mobile app too?

Yes, on Pro. The Jetonomy mobile app can carry the client's own name, icon, and colours rather than Jetonomy's, so the branding you set for the web community can extend to a native app the client publishes under their identity.

Does Pro White Label hide Jetonomy from members?

It does not need to. The public pages carry no Powered by line, and Pro White Label only changes the admin menu label, icon, plugin name and footer text. Member-facing branding comes from the free Appearance and Email settings plus your theme.

What happens to the branding if the client's Pro licence lapses?

Pro extensions switch off thirty days after the licence expires, so the admin rename stops and the Jetonomy name returns in wp-admin. The logo, accent colour, custom CSS and email branding are free settings and stay in place, and the community keeps working.

Build it on your own WordPress.

Jetonomy is free to start and self-hosted. Run the 5-minute wizard and put what you just read into practice.

What customers say on Trustpilot

WBCOM Designs is Amazing!

WBCOM Designs has constantly updated and supported their plugins and themes. Recently the new BuddyNext project is Amazing! - and the new line of addons like Mediaverse, Jetonomy, Mediashield, and Listora.. are likewise Amazing! - and very well built. Today their online Chat solved a download…

Edward S.US