Sign in Get started

Whitelabel email

Send transactional emails (welcome, password reset, alerts) from your own SMTP — your users see your domain in the From line, not Linked.Codes.

Updated today 5 min read

Welcome emails, password resets, scan alerts — by default they all leave from hello@linked.codes. Switch on whitelabel email and they leave from noreply@yourbrand.com (or whatever address you configure) instead. The recipient never sees Linked.Codes anywhere in the From, Reply-To, or unsubscribe footer.

Hosting required. The toggle saves whenever you want, but the actual sending only fires for accounts on a hosting plan. Without hosting, your settings sit ready and your users get the platform default until you upgrade.

What you'll need

A mailbox A real inbox at your domain. Namecheap private email, Google Workspace, Fastmail — anything that gives you SMTP credentials. 5 minutes Paste host + port + user + password, click Test connection, send a test, flip the toggle. That's the whole flow. Active hosting Saving is free. Sending fires only on hosting plans — that's how Linked.Codes covers the cost of running the redirector + auth side.

How to set it up

  1. Get SMTP credentials from your mail provider.

    Most providers expose them in their account dashboard. The four you need: host, port, user (your full mailbox address), and password (the mailbox password or an app-specific password). Common values:

    • Namecheap private email: mail.privateemail.com · port 587 (STARTTLS) or 465 (SSL).
    • Gmail / Google Workspace: smtp.gmail.com · port 587. Generate an app password under Google account → Security → 2-step verification → App passwords.
    • Postmark: smtp.postmarkapp.com · port 587. User + password are both your Server API token.
    • AWS SES: email-smtp.<region>.amazonaws.com · port 587. Generate SMTP credentials under SES → SMTP settings.

  2. Open Email → Settings and paste the credentials.

    Host, port, user, password. Leave Secure on "auto" unless you specifically need 465+SSL. Click Test connection before saving — it runs an EHLO + AUTH session against the server and tells you if anything's wrong (wrong port, wrong password, blocked IP). A green "Connected — auth OK" means you're good.

    From address has to match the SMTP user. Most providers reject sends with a 553 error if your From email is different from the authenticated mailbox. If you authenticate as noreply@yourbrand.com, your From email must be the same address (or a configured alias on that mailbox).

  3. Set From email + From name.

    This is what your end users see in their inbox. The From email must match the SMTP user; the From name is whatever you want (your brand name usually). Reply-To is optional — leave empty so replies go back to From.

  4. Send a test.

    Use the Test connection button to confirm SMTP auth works. Then trigger any transactional flow (request a password reset on a sub-user account, for instance) — the email lands in their inbox from your domain.

  5. Flip the Whitelabel toggle on.

    This is the explicit on/off switch. With it OFF, sends still go through Linked.Codes' platform mailer (so you can configure ahead of time without breaking flows). With it ON + hosting active + creds saved, every transactional email to your sub-users ships from your SMTP. The Active transport pill on the connection card flips to "Whitelabel SMTP · <your host>".

What gets sent from your SMTP

Currently routed through tenant SMTP when the toggle is on:

  • Welcome emails to new sub-users who sign up on your subdomain
  • Password reset emails to sub-users who request one from your subdomain

Everything else (notifications about your own Linked.Codes account, billing receipts, hosting alerts) keeps coming from hello@linked.codes because those are between Linked.Codes and you, not between you and your users.

Why your reputation matters

Whitelabel email isn't just a branding lever. The sending domain accumulates reputation over time — Gmail, Outlook, Yahoo all track which domains send legitimate mail at scale. If your platform sends 5,000 password resets a month and they all open and click, that signal accrues to your domain. Recipients trust mail from your domain because they've seen it before.

The opposite is the trap with shared shortener-style mailers: when one tenant fires a bulk outreach campaign and gets flagged, every other tenant on that pool eats the deliverability cost. Whitelabel SMTP keeps your reputation isolated.

Templates

Open the Templates tab on the same page to override the default subject + body for any transactional email. Save a tenant override and it ships from your account; revert and you fall back to the Linked.Codes default. Variables like {{first_name}}, {{reset_url}}, {{app_url}} interpolate at send time — full list visible in the editor for each template.

Activity log

The Activity tab shows every email your account sent — to whom, which template, status (sent / failed / bounced), timestamp. Filter by status to find failures fast.

Troubleshooting

"Sender address rejected: not owned by user X" — your From email doesn't match the authenticated SMTP user. Either change the From to match the SMTP user, or add the From address as an alias on the mailbox.
"Connection timed out" on Test connection — usually a wrong port (try 587 for STARTTLS or 465 for SSL), or your provider blocks SMTP from outside their network. Check the provider's docs for the exact host + port.
Saved but emails still come from hello@linked.codes — check the Whitelabel toggle is ON, hosting is active, and all four SMTP fields are filled (the connection-card pill says "Whitelabel SMTP · <host>" when everything's lined up). If the pill says "Linked.Codes platform" instead, one of those is missing.

What's next