Email Configuration
Settings → Email Configuration is where you manage the identities your workspace sends email from - the display name and address recipients see - plus the Reply-To and BCC addresses campaigns and journeys may use.
- Email Providers (Settings → Email Providers) = the sending infrastructure (SendGrid, SES, etc.).
- Sending domains are attached and verified (SPF/DKIM) by your administrator; their health is shown read-only under Analytics → Deliverability.
- Email Configuration (this page) = the sender identities and address lists you build on top of those verified domains.
Sender identities
A sender identity is a display name + address on one of your verified sending domains (e.g. Acme News <news@acme.com>).
To add one, click Add Configuration and set:
- Display name - what recipients see (e.g. "Acme Support").
- Local part - the part before the
@(e.g.news). - Domain - a locked dropdown of your workspace's SPF+DKIM-verified sending domains. You can only build senders on verified domains; if the list is empty, ask your administrator to attach one.
- Reply-To (optional) - a default reply-to for this sender (see precedence below).
- Default - the sender pre-selected when creating a campaign.
Sender identities are workspace-scoped - shared by everyone on the workspace, not personal.
Reply-To & BCC address lists
Below the senders, you maintain the workspace's allowed Reply-To and BCC addresses. The per-message Reply-To and BCC pickers (in the campaign composer and journey email steps) are limited to these lists - to use an address it must be added here first.
- Require a BCC address for all your email campaigns - when on, every email must pick a BCC (the "No BCC" option is removed in the composer). A separate workspace compliance BCC (Settings → Subscriptions) is always applied on top of any per-message BCC and de-duplicated, so an archive copy is never lost.
Per-message sender (campaigns & journeys)
When composing an email, the Sender section lets you:
- Pick a saved sender from the dropdown, or
- Customize From - tick to override with a custom display name + local part on a verified domain (the domain stays locked).
- Reply-To - choose a managed reply-to address, or "Exclude" (replies go to the From address).
- BCC - choose a managed BCC address (or "No BCC", unless a BCC is required).
Per-variant in A/B tests
For campaigns, the sender is per A/B variant - each variant can send from its own identity (and its own Customize-From, Reply-To and BCC). This lets you A/B test the From line, one of the biggest open-rate levers. See A/B Testing.
For journeys, the sender is set per email node.
Reply-To & BCC precedence (at send time)
- Reply-To: a per-message reply-to wins; otherwise the selected sender's own reply-to; otherwise replies go to the From address.
- BCC: the recipient gets the per-message BCC plus the workspace compliance BCC (unioned, de-duplicated). Adding a BCC sends a copy to that address - it doubles your billable emails.
- Custom From: the platform refuses to send from a domain that isn't SPF+DKIM verified for the workspace (it never silently substitutes a different sender).
Related
- Email Deliverability
- Subscription Management - List-Unsubscribe header (default or custom), compliance footer, and the workspace compliance BCC
- Email Campaigns