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.
What you'll need
How sending actually flows
Here's what happens when a sub-user requests a password reset on your subdomain:
How to set it up
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).
- 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.- Fastmail
smtp.fastmail.com· port 465 (SSL). Generate an app-specific password under Settings → Privacy & Security → App passwords.
Open Email → Settings and paste the credentials.
The SMTP block sits at the top of the Settings card. Here's what it looks like:
noreply@yourbrand.com, your From email must be the same address (or a configured alias on that mailbox).
Set the sending identity.
Below the SMTP block, set your From email + From name. The From email must match the SMTP user above. Reply-to is optional — leave empty to default to From.
Send a test.
At the bottom of the Settings card, drop your own email into the test-send field. Test sends bypass the Whitelabel toggle and the hosting gate, so you can verify the loop before flipping anything live.
Flip the Whitelabel toggle on.
The toggle sits at the very top of Email under the tab bar. Once on (with hosting active + creds saved), every transactional email to your sub-users ships from your SMTP. The Active transport pill flips to Whitelabel SMTP · <your host>.
What gets sent from your SMTP
Currently routed through tenant SMTP when the toggle is on:
- Welcome — sub-user signup
- Triggered when a new sub-user signs up on your tenant subdomain. Uses your welcome_user template.
- Password reset
- Triggered when a sub-user requests a reset from your tenant subdomain. Uses your forgot_password template.
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.