Sender domains and reply-to
Verify your domain and choose the addresses used for end-user email
Invitebase sends end-user email on your behalf through its own Resend account. You verify a domain you control; you do not need a Resend account or API key. End-user emails use your domain, never an Invitebase address. Invitebase team invitations and integration-health alerts are developer emails and use sales@invitebase.com.
Set up your sender
During onboarding, or under App settings → Email sender, enter:
- Sending domain: a domain you control, such as
mail.example.com. - From address: an address on that exact domain, such as
hello@mail.example.com. - Reply-to address: a mailbox you monitor on that exact domain, such as
support@mail.example.com.
The sender is configured once per organization and shared by its apps. Both addresses must use the exact verified domain: verifying mail.example.com does not authorize hello@example.com. To change the domain after setup, contact Invitebase support. You can update the addresses in settings.
Add DNS records
After you save, the dashboard shows the DNS records returned by the email provider, including each record's type, host, value, TTL, priority where applicable, and verification status. Add those records at your DNS provider exactly as shown.
Some DNS providers append your domain to the host automatically. Check the resulting full record name so you do not accidentally add the domain twice. Keep existing records needed by other email services; if records conflict, check with your DNS administrator before replacing them.
Choose Verify DNS after adding the records. Verification is asynchronous. The dashboard checks every 30 seconds while the domain is unverified; Check status lets you refresh it immediately. DNS propagation can take time. If verification fails, check the record values and host names, then retry verification.
Send a test email
Once the domain is verified and both addresses are saved, enter your email in Test recipient and choose Send test email. Check the from address in your inbox and confirm that replying targets your configured reply-to mailbox. An accepted test means the provider accepted the request; it does not guarantee inbox delivery.
End-user email is blocked until verification succeeds. Invitebase also rechecks the provider before sending, so removing the DNS records or losing verification blocks later sends. There is no fallback to an Invitebase sender.
The reply-to address controls where replies go. Domain verification does not create that mailbox or prove that it can receive replies; provision and monitor it with your own email service.
Environments
Sender identity is shared across your organization's app modes. The explicit test-email action sends a real email to the address you enter. Use your own inbox for testing. This setup provides the domain and delivery boundary; welcome and payout notifications have separate delivery workflows.