Custom Email Domain

The Email Domain page lets your workspace send outbound email from your own domain (e.g. hello@acmeit.co.uk) instead of the default @concorbit.com sender. This is used by concorbit's shared platform email service (Postmark under the hood) for deliverability, adding DKIM signing and a proper Return-Path CNAME so receiving servers trust the mail. If you prefer to run email through your own SMTP provider instead, use SMTP settings.

URL: /settings/email/domain
Required permission: settings.tenant

Mail domain vs app custom domain

This page is for outbound mail only. It is independent of the Custom Domain page, which controls the URL where concorbit serves your workspace's UI.

It's very common to want different domains for the two: the app on a subdomain, mail from the bare brand domain. For example:

Where the customer sees it	Setting	Example
Browser URL when logging in	Custom Domain	app.example.com
Marketing / public website	(managed outside concorbit)	example.com
From address on outbound email	Email Domain (this page)	hello@example.com

Verify whatever domain you want emails to come from. It does not have to match (and usually shouldn't match) the subdomain where the app is served.

Once a mail domain is fully verified, the from address is automatically used by every system email concorbit sends (form autoreplies, ticket alerts, CSAT surveys, signing requests, etc.) and by campaign emails sent from your workspace. If your Brand kit's "from email" field is left blank, concorbit uses hello@your-domain.example; setting it to a specific mailbox (e.g. support@your-domain.example) is allowed as long as the address sits on the verified domain. Addresses on other domains are rejected at save time so you don't accidentally configure a from address that Postmark would silently drop.

How to get there

Go to Settings from the sidebar.
Open the SMTP card.
Click Set up or Manage on the "Custom sending domain" tile at the top.

Or navigate directly to /settings/email/domain.

The five states

The page is a state machine: what you see depends on where your domain is in the verification lifecycle.

State	Badge	What you see
Not configured	Not configured	Setup form to register a domain.
Pending DNS	Pending verification	The two DNS records you need to add, a Verify button.
DKIM verified	Partially verified	DKIM is found but the Return-Path CNAME is missing. Emails can send but bounce handling is incomplete.
Fully verified	Verified	The From name and From email editor.
Failed	Verification failed	Troubleshooting tips and a Retry button.

State 1: Setting up a domain

Enter your domain in the format acmeit.co.uk (no http://, no trailing slash, no leading www. unless you actually want to send from @www.acmeit.co.uk).
Click Set up.
concorbit registers the domain with the email service and returns the DNS records you need to add.

What gets rejected:

Free email providers: you cannot register @gmail.com, @outlook.com, @yahoo.com, @icloud.com, @proton.me, etc. The email service cannot issue DKIM keys for domains it does not own. Use your own business domain.
Domains already registered to another concorbit workspace.
Domains verified in a different email-service account entirely: these need to be removed from the other account first.

If we detect the domain is already registered in our system but to an unknown workspace, the page tells you to contact support to manually attach it.

State 2: Adding DNS records

After registration, the page shows two records. Add both to your DNS provider (Cloudflare, GoDaddy, Namecheap, Route 53, Squarespace, etc).

Record 1: DKIM (TXT)

Signs your emails so receiving servers can verify they really came from you.

Type:  TXT
Host:  concorbit._domainkey.yourdomain.com   (or similar — see the page)
Value: k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4G...

The exact host and value are shown on the page; copy them with the Copy button. Different providers want the host either as the short prefix (concorbit._domainkey) or as the full FQDN (concorbit._domainkey.yourdomain.com); try the short form first.

Record 2: Return-Path (CNAME)

Routes bounces back to the email service for processing.

Type:  CNAME
Host:  pm-bounces.yourdomain.com
Value: pm.mtasv.net

After both records are saved at your DNS provider, click Verify DNS records.

Per-record status

Below the domain name, two tick or cross indicators show which records have been verified:

DKIM ✓ / ✗
Return-Path ✓ / ✗

This lets you diagnose which half is failing if verification is only partial.

State 3: Partially verified (DKIM only)

If only some of the DNS records have propagated, the domain shows as partially verified. Emails may send in this state but bounce handling is incomplete: we won't automatically mark addresses as undeliverable when mail bounces. Add the missing record(s) shown in the list and click Verify again. (The exact records depend on the platform's mail provider — Postmark shows a DKIM TXT and a Return-Path CNAME; Lettermint shows its own TXT/CNAME/MX set.)

State 4: Fully verified

Both records are verified, so you can now edit the sender identity:

Field	Effect
From name	The display name on outbound emails (e.g. Acme IT Support). Prefilled to your workspace name the first time you verify.
From email	The sender email address. Must use the verified domain: you cannot set hello@somewhere-else.com because the email service hasn't been authorised to sign for that domain. Prefilled to hello@yourdomain.com.

Save, and the next outbound email sent through the platform email service will use this sender identity.

State 5: Verification failed

If verification keeps failing after multiple attempts, the page shows a troubleshooting card. Check:

The DKIM TXT record is exact (host and value both match, no trailing whitespace or quotes added by your DNS provider)
The Return-Path CNAME exists and is correct
DNS has had time to propagate: changes can take up to 48 hours, often an hour or less
Your DNS provider has not added extra quotation marks around the TXT value (some do this automatically and it breaks the signature)

Click Retry verification once you've fixed the issue.

Removing a domain

Click Remove next to the domain name at the top of the page. Emails will revert to the default @concorbit.com sender. The domain is also removed from the platform email service so it can be re-registered later if needed.

Notes

DNS propagation is typically under an hour but can take up to 48 hours in worst cases. Be patient before panicking.
This page only controls the sender identity on the shared platform email service. If you've added your own SMTP provider on the SMTP page, that provider's From address is used instead for any mail routed through it.
SPF and DMARC are not verified by this page but are strongly recommended for deliverability. See the SMTP guide for example SPF and DMARC records.