Skip to main content
The sending domain is the domain your app’s automation and notification emails come from. Until you assign a verified domain to your app, they send from Meridian’s own address. Choose your own domain and they come from you, which is also better for inbox placement. Domains are managed per organization, in Organization settings → Email, and are available to its apps. Each app selects its sender separately in App settings → Email. Custom sending domains are included on every tier.

​
Adding a domain

Give the From email you want to send from (hello@yourdomain.com) and, optionally, a From name. Meridian generates the DNS records for that domain. The records come in two groups:
  • Required: all of them must resolve before the domain verifies and can send.
  • Recommended: SPF and DMARC. They improve inbox placement but aren’t part of automatic verification.
Add them at your DNS provider exactly as shown, then recheck. Each record shows Found or Not found so you can see which one is holding verification up, and propagation can take up to 48 hours.

​
Using it

A verified domain can be set as the organization default. That does not assign it to your apps. In App settings → Email, select the Meridian platform sender or one of your verified domains for that app. Pending domains are listed but not selectable, because a domain has to verify first. Once an app is pointed at a verified domain, that domain sends its automation and test emails.

​
Removing a domain

Apps using it fall back to the Meridian platform sender, and you can delete the DNS records afterwards.

​
Who can manage a domain

A domain belongs to the organization, but it sends for every app pointed at it. So the Emails permissions stop at a role’s app scope:
  • Changing or removing a domain needs Emails: Edit or Emails: Delete on every app that sends from it. A role limited to some apps can manage the domain only those apps use. It can’t touch a domain another app also sends from.
  • Changing or removing the organization default, adding a domain and setting the default need a role that covers every app. The default is the organization’s own sender (see below), so choosing it is an organization-wide decision.
  • Rechecking DNS only needs Emails: Edit. It reads the records you published and changes nothing else.
Buttons you can’t use are hidden. Choosing which domain an app sends from is part of App settings and needs Applications: Edit on that app.
Password resets and email verification always come from Meridian. Team invitations and the reminder to turn on two-factor authentication come from the organization’s default domain once it is verified (or, with no default, from the most recently verified domain). Everything else a custom domain sends is your apps’ mail to merchants.
Last modified on October 9, 2026