A branded community lets you run BetaTesting on your own subdomain, with your logo, your colors, your landing page, and your own welcome message, so the people you recruit feel like they joined your program rather than a third-party platform.
This matters most when you are building and running your own panel. If you email your customers, post a sign-up link on your site, or invite an internal group of employees to test early builds, the first thing they see is your community landing page. A page carrying your logo and your wording gets far better sign-up rates than a generic one, and it keeps your program looking like yours all the way through the tests your participants take.
Typical uses include a customer beta program with a public sign-up page, a private employee dogfooding community, and a research panel you recruit into once and then invite to test after test.
Branding is a plan-specific feature, so it may not be enabled on your account. If you do not see Company Branding in the settings menu, or you open it and see a message that your company does not have this feature, contact your BetaTesting account manager.
What you can customize
There are two screens involved, and both sit in the same settings menu.
Company Branding holds your subdomain, your community landing page, your logos, your colors, and your terms and policies.
Tester Onboarding holds the welcome message that new members see the first time they join, along with the sign-up controls for your community.
To reach either one, click Settings in the top navigation, then pick Company Branding or Tester Onboarding from the menu on the left.
You need to be a full company admin with super admin rights to open these screens. Other admins see the menu items greyed out.
Set your subdomain and community landing page
The subdomain is the foundation. It gives your community its own address, in the form yourcompany.betatesting.com, and several other features stay locked until you set one.
How to set it up
Go to Settings, then Company Branding.
Find the Community Landing Page section.
In the Subdomain field, type the name you want. The .betatesting.com part is added for you.
In Header text, write the headline visitors see, for example an invitation to join your beta program.
Under Landing page image, click Upload new image and choose the picture that sits beside your headline.
Use Landing page primary text to write the paragraphs below the headline. This is a rich text editor, so you can bold text and add links.
Your changes save on their own about a second after you stop typing, and a Saved confirmation appears. There is no separate save button in this section.
What visitors see
Your landing page shows your logo at the top, your header text as the headline, your landing page image, and your primary text, with Create an account and Login buttons. If you leave the header text blank, the page falls back to a generic invitation using your company name, and if you leave the image blank it uses a stock photo, so it is worth filling both in.
Who can actually get through those buttons is a separate setting. Registration can be open to anyone who reaches the page, or limited to invite codes, an approved list of email addresses, or your identity provider, as described in How people get into your community.
Subdomains are unique across BetaTesting. If the name you want is already claimed you will see an error when it tries to save, and you will need to pick another.
Upload your logos
You upload two versions of your logo, because the platform places it on both light and dark surfaces and picks whichever version stays readable.
How to upload them
Go to Settings, then Company Branding.
In the Company Logo section, find the slot labelled White background (dark logo) and click Upload new image.
Choose your file. You can upload from your computer, or from Google Drive, Dropbox, Box, OneDrive, or Gmail.
Repeat for the slot labelled Dark background (white or light colored logo), using a version of your logo that reads against a dark color.
Accepted file types are PNG, SVG, JPEG, JPG, and WEBP. Each slot holds one image. Uploading a new one replaces what was there, and you can clear a slot instead if you want to fall back to the BetaTesting logo.
Your logos appear in the top navigation for your members, on your community landing page, and in the header of the emails BetaTesting sends on your behalf.
Choose your colors
Colors are set in the Company Colors section of Company Branding, grouped so you can start with the broad strokes and only go into detail if you want to.
The color groups
Base palette sets Primary, Secondary, and Tertiary. These drive buttons and accents across the platform, and the rest of the interface follows them unless you override it.
Top nav sets the Background, Font & icons, and Bottom border of the bar across the top.
Left nav sets the Background, Font, and Right border of the side menu.
Test submenu sets the Background, Font, and Bottom border of the bar inside a test.
Sections sets the Section background used behind page content.
How to change a color
Open the group you want and click the pencil icon on the color card.
Pick a color with the picker, or type a hex value into the field.
Click Apply to put it into the preview, or Cancel to leave it alone.
Repeat for any other colors you want to change.
Click Save changes when you are happy. Cancel discards everything you have not saved yet.
Below the color cards is a live Preview with two tabs, Admin View and Tester View, showing how your palette looks to your team and to your participants. The preview updates as you edit and before you save, so you can try a color without committing to it.
If you want to start over, click Restore default colors. You will be asked to confirm, because it replaces your palette with the default BetaTesting platform colors and cannot be undone.
Your primary, secondary, and tertiary colors also carry into the emails sent to your community, so the header bar of those emails matches your brand.
Add your terms and policies
The Terms & Policies section lets you put your own wording in front of people at the three moments they are deciding whether to join.
Login Terms appear on your branded login page.
Account Creation Terms appear when someone signs up.
Landing Page Terms appear on your community landing page.
Each one has its own editor supporting bold, italic, and links, and its own Save button, so you can update one without touching the others. This section stays hidden until you set a subdomain. Until then you will see a note telling you to enable a subdomain on the Community Landing Page first.
These are your own terms, shown alongside the standard BetaTesting participant agreement rather than in place of it. If you need participants to sign a document such as an NDA, that is handled separately through agreements rather than here.
Write a welcome message for new members
The welcome message is a one-time greeting for people who have just joined your community. It is the first thing they see after signing up, and it is a good place to explain what your program is, how often you will invite them to test, and what they get out of it.
How to set it up
Go to Settings, then Tester Onboarding.
Scroll to the Welcome Message section.
Turn on Show the welcome page.
Enter a Title.
Under the desktop Hero image field, click Upload new image and choose a portrait image. Use a 3:4 shape, at least 600 by 800 pixels, with 900 by 1200 recommended.
Under the mobile Hero image field, upload a landscape image. Use a 16:9 shape, at least 800 by 450 pixels, with 1280 by 720 recommended.
Write your greeting in the Body editor. It supports bold, italic, underline, lists, links, and headings.
Set the Accept button label, the wording on the button that dismisses the message. Leave it blank to use Get Started.
Like the landing page, this section saves on its own shortly after you stop typing.
Things to know about the welcome message
It shows once. After a member dismisses it, they do not see it again, so changing it later only affects people who join afterwards.
It needs a subdomain. Without one the section shows a note asking you to add a subdomain on the Community Landing Page first.
It needs content. If both the title and the body are empty, nothing is shown even with the toggle on.
Both hero images are optional. Leave one or both empty and the message shows as text only.
Members who are on your waiting list do not see it. They see it once they are released into the community.
Things to know
Set the subdomain first. Terms and policies, the welcome message, and single sign-on all depend on it.
Only full company admins with super admin rights can edit branding. Everyone else sees the menu items greyed out.
Every branding image slot holds a single image, and uploading a new one replaces the old one.
Colors and logos apply to what your participants see on your subdomain and to your admins working inside your company, not to the public BetaTesting site.
The landing page and welcome message sections save automatically, while colors and terms need you to click their save buttons.
Changing your subdomain changes the address your community uses, so any links you have already sent out will stop working. Settle on a name before you start recruiting.
Related articles
Single sign-on overview, which requires a subdomain and lets members sign in with your identity provider.
Importing Testers into Your Community, for bringing an existing list of participants in.
Recruiting from Your Community, for inviting your members to a test once they have joined.