How to launch a white-label job board with branded emails

A white-label launch succeeds when the whole journey carries your identity: the link opens on your domain, the interface uses your brand, an employer can post a role, and a job seeker receives a working email from your sender.

This tutorial configures and verifies that journey in Cavuno. The white-label software comparison covers vendor selection and plan gates.

Define the finished journey

Write down what you will test:

An employer visits jobs.example.org, signs in, selects a posting option, and publishes a role. A job seeker finds it, subscribes to matching alerts, confirms the subscription, and later receives a weekly digest from Example Jobs <info@notifications.example.org>.

Assign one person access to Cavuno and the DNS provider before starting.

Step 1 — Connect the public domain

Use a subdomain such as jobs.example.org when the main website already uses example.org.

1. Open Settings → Domains.
2. Click Connect domain.
3. Enter the full hostname.
4. Add the DNS records shown. Use Cavuno's values, not an example from another board.
5. Select Refresh status.
6. When it shows Active, choose Set as primary.

The primary domain becomes the canonical host for board and email links. Cavuno provisions HTTPS after verification. Cloudflare users should keep the board CNAME set to DNS only. See connect a custom domain.

Open the URL privately. Check HTTPS and confirm job links remain on the same host.

Step 2 — Apply the visual identity

Configure the board name, logo, colors, typography, homepage copy, navigation, footer links, contact details, employer pricing copy, and email branding.

Review the homepage, search results, job detail, sign-in, employer pricing, and posting flow at narrow and wide sizes. Cavuno badge removal is included on Basic, currently $139 monthly or $109 monthly when billed annually. Current self-serve monthly plan prices are $29, $139, $239, and $439. Verify live pricing because packaging can change.

Do not stop at the homepage. Sign-in, checkout, confirmation messages, and emails often reveal inconsistent names or colors.

Step 3 — Verify a branded email sender

The website host and email sender are separate DNS configurations. If the board is jobs.example.org, the sender can be info@notifications.example.org.

1. Go to Settings → Email domain.
2. Click Add email domain.
3. Enter the sender name and review the address.
4. Click Create.
5. Add the displayed DKIM TXT, MX, and SPF TXT records at your DNS provider.
6. Add the suggested DMARC record if it fits your policy.
7. Wait or select Refresh status.
8. Continue when the sender shows Active.

Custom email sender domains are included on Basic, currently $139 monthly or $109 monthly when billed annually. While verification is pending, email continues from Cavuno's default sender. When Active, board-scoped transactional mail switches to the custom sender; platform team invitations remain from Cavuno.

Follow send email from your custom domain. The supplied MX record supports transactional delivery feedback, not a normal reply inbox.

Step 4 — Customize the launch emails

Open Email editor and update the templates you will trigger:

• Email verification or magic link
• Job-alert subscription confirmation
• Job-alert digest
• Public submission receipt, if used
• Billing verification or invoice message, if used

Edit the subject, preview text, and body. Keep required tokens such as {{action_url}}. Verify sender name, board name, logo, support wording, and footer. A preview proves layout, not delivery, so trigger each critical email in an inbox. See the email editor guide.

Step 5 — Configure employer posting

Choose free posting, paid public posting, member pricing, or members-only posting. You can build a board free. Keeping it public after the trial requires a paid plan, even when employer posting is free.

For association pricing, memberships belong to companies. Cavuno does not currently include automatic AMS or CRM sync or member SSO, so assign an owner to add, expire, and revoke memberships.

1. Create and publish the posting product under Settings → Products or payment settings.
2. If applicable, assign a test membership from Companies → Manage membership.
3. Open the public posting route, then sign in as the employer.
4. Confirm the expected public, member, or included-post option appears.
5. Complete the approved checkout test and verify the resulting job state.

See charge for job postings and memberships.

Step 6 — Publish a representative job

1. Click Jobs → Add job.
2. Select or create the employer company.
3. Add title, employment type, seniority, and description.
4. Choose on-site, hybrid, or remote and complete location constraints.
5. Add salary when the employer supplied it.
6. Choose native applications, an external URL, or an application email.
7. Set publish and expiry dates, then publish.
8. Select View live job and inspect it signed out.

Follow the application route to its destination. Confirm company, location, salary, expiry, and button label. See post a job.

Step 7 — Verify job alerts end to end

Subscription confirmation is prompt; matching alerts are weekly and only send for new matches.

1. Go to Settings → Features and enable Job alerts.
2. Subscribe on the public board with an inbox you control.
3. Inspect the confirmation email's From address, identity, and links.
4. Click the confirmation link.
5. Confirm the subscriber becomes Active rather than Pending confirmation.
6. Set preferences matching the representative job.
7. Publish a new matching job after activation.
8. At the next eligible weekly send, confirm the digest arrives and links to the primary domain.

No email is sent when there are no new matches. Use job alerts and email deliverability to check status, filters, timing, spam placement, and diagnostics.

Step 8 — Run a signed-out launch check

Ask someone who did not configure the board to find a job, begin applying, subscribe and confirm an alert, explain the employer offer, and publish through the intended employer option. Capture the URL, viewport, account state, expected result, and actual result for failures. Fix and repeat the journey.

White-label launch checklist

• Public domain is Active, primary, and serves HTTPS
• Homepage, search, job detail, sign-in, pricing, and posting use the approved identity
• Cavuno badge visibility matches the purchased plan
• Sender domain is Active with DKIM, SPF, and MX verified
• Critical email templates keep required tokens and correct links
• Public or member employer pricing appears as intended
• A representative job is live with a working application route
• Alert confirmation arrives from the branded sender
• Confirmed subscriber becomes Active
• A new matching job is eligible for the weekly digest
• Privacy, terms, contact, refund, and moderation links are published
• DNS, support, moderation, membership, and email owners are named

Keep the checklist as a regression test after domain, brand, price, or email changes.