---
title: Email Domain Setup
slug: email-domain-setup
docTags: 8mz5QSGhEgh1yvfbZJtXt,j9seF7qYq2Rc_-OLJd8rE
createdAt: 2025-07-10T11:57:32.686Z
---

This guide outlines the steps to verify a domain for sending newsletter emails or for sending a large volume of no-reply emails via Ashby (over 1,000 emails a day). The setup process involves updating DNS records on a domain owned by your organization, so you’ll likely want to provide these instructions to your IT team or to someone who can configure DNS records for your organization’s domains.

Please note that verifying a domain for sending newsletter or no-reply emails can only be configured on the Enterprise plan.

| Foundations | Legacy Plus | Plus | Enterprise |
| ----------- | ----------- | ---- | ---------- |
| ❌           | ❌           | ❌    | ✅          |

## Overview

To send newsletters using Ashby's Newsletter feature, you'll need to configure at least one domain for email sending. Configuring a domain is also beneficial if you send a high volume of no-reply emails and would prefer to use an email branded to your company, rather than using the default Ashby no-reply email address.

Configuring a domain is necessary because email providers like Google and Microsoft restrict the use of their platforms for bulk emailing and sending newsletters.  Google and Microsoft email accounts have daily sending limits, so you can't directly send newsletters or large numbers of emails from these accounts. To work around this restriction, you'll need to grant Ashby permission to send emails from one of your organization's domains on your behalf.

To do this, you’ll set a few DNS records on one of your organization’s domains so that Ashby can verify that you own the domain and so that Ashby has permission to send emails from this domain on your behalf.

### Prerequisites

To follow the steps below, you’ll need to be able to update DNS records associated with the domain you want to use for sending newsletters or no-reply emails. To access the [Email domains admin page](https://app.ashbyhq.com/admin/organizational-settings/domains), you’ll need to be an Ashby organization admin.

### Video Walkthrough

A video walkthrough of the email domain setup process is available below.

Note: In the walkthrough, the page is named Newsletters, but it’s since been renamed to Email Domains. The functionality is unchanged.

::loom{url="https://www.loom.com/embed/4bbfda9330754c46ba7fe5d3acdc3936?sid=6fdfb94e-3388-46d5-b468-23bac9d2ab4d"}

- Log into your Ashby account and navigate to Admin in the top nav bar.
- Search for ‘Email Domains’ or visit the page directly at [this link](https://app.ashbyhq.com/admin/organizational-settings/domains).

### Steps to Configure a Domain

![](https://api.archbee.com/api/optimize/0p8tQ--ZZOxRtkVp6Qr-e/dSfn7uA9HY2FParG1DynK_cleanshot2024-07-24at1023352x.png)

- Click on `Add Domain` in the top right-hand corner of the page. Provide the domain you’d like to use for sending emails and click `Add`.&#x20;
- Once you click `Add`, you’ll have 72 hours to update your domain’s DNS records before your domain setup is considered Failed.
  Once your domain’s setup status is Failed, you’ll need to remove the domain in Ashby and re-add it in order to start the setup process again. For that reason, we recommend waiting to add the domain in Ashby until you’re ready to update the domain’s DNS records.

![](https://api.archbee.com/api/optimize/0p8tQ--ZZOxRtkVp6Qr-e/ZpYEPps00DxULBBJlMvA3_cleanshot2024-07-24at1023572x.png)

- After clicking Add, you’ll see a list of three CNAME records, one MX record, and one TXT record. You’ll need to set these DNS records on your domain.

![](https://api.archbee.com/api/optimize/0p8tQ--ZZOxRtkVp6Qr-e/UuXg35bDdZGv6zkULH4sj_cleanshot2024-07-24at1026122x.png)

- Depending on where your domain is managed, the instructions for updating your DNS records will vary slightly. Below you can find links to documentation for updating DNS records from a few common providers.

**Cloudflare** See Cloudflare’s guide to managing DNS Records [here](https://developers.cloudflare.com/dns/manage-dns-records/how-to/create-dns-records/#create-dns-records)&#x20;

**Route 53** See Route 53’s guide to managing DNS records [here](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resource-record-sets-creating.html)&#x20;

**GoDaddy** See GoDaddy’s guide to managing DNS records [here](https://www.godaddy.com/en-uk/help/manage-dns-records-680)&#x20;

**Other Providers** If your provider isn’t listed above, you can generally find documentation on updating DNS records by Googling ‘manage \{domain name provider} DNS records’&#x20;

:::hint{type="warning"}
A Note on the MX record Depending on your domain registrar, you may need to provide the priority, which is at the start of the MX record's expected value, in a separate input. This refers to the '10' at the beginning of the record. In most cases, you can leave it formatted as it is in Ashby. However, some providers may require you to put the '10' in a separate input or on a different line.
:::

- Once you’ve configured the DNS records, head back to the Email Domains page in Admin and click on Check DNS Records in the bottom left of the domain’s configuration window. This will run a check to see if the DNS records have been found on your domain. It may take up to 72 hours for the records to be published and for the statuses to update to Verified.

  ![CleanShot 2024-07-24 at 10.26.40@2x.png](https://api.archbee.com/api/optimize/0p8tQ--ZZOxRtkVp6Qr-e/-JGuCnzoP9zobx81SnTPW_cleanshot2024-07-24at1026402x.png)
- Once your DNS records have all been verified, you can specify the email addresses you want to use. To add an email address, click `Add Sender Email Address` in the bottom lefthand corner.

  ![CleanShot 2024-07-24 at 10.27.19@2x.png](https://api.archbee.com/api/optimize/0p8tQ--ZZOxRtkVp6Qr-e/q5I4PJJz2zS6_cKt3FdTo_cleanshot2024-07-24at1027192x.png)
- In the Name field, provide the name you want email recipients to see when they receive emails from this address. In the Email Address field, provide the email address you want to use for sending  emails. The email must be a part of the domain you configured. For example, if you configured ‘acmecorp.com’ as your domain, you could provide an email here that ends with ‘@acmecorp.com’. Once both fields are filled out, click `Add` to add the email address.

  ![CleanShot 2024-07-24 at 10.28.05@2x.png](https://api.archbee.com/api/optimize/0p8tQ--ZZOxRtkVp6Qr-e/sCQk2VLq9s97DtJyOTiuC_cleanshot2024-07-24at1028052x.png)
- Once an address is added, it will appear beneath the domain, as in the example below. To remove an address, click on the trash icon on the far right. To add more email addresses, click `Add Sender Email Addres`s in the bottom left corner and repeat the same steps. You can add as many addresses as you want.

  ![CleanShot 2024-07-24 at 10.28.42@2x.png](https://api.archbee.com/api/optimize/0p8tQ--ZZOxRtkVp6Qr-e/PCEkIt_N4u4avE9MZJ9OP_cleanshot2024-07-24at1028422x.png)

### Using Addresses in Newsletters

To use the email addresses you’ve configured to send Newsletters, open or create a newsletter and click on `Settings` on the top right of the page. In the settings menu, you’ll see a ‘From’ field (highlighted below). In this field, you can select the from address you want your newsletter to be sent from. The dropdown here will include all the addresses you’ve configured by following the steps above.

![CleanShot 2024-05-22 at 16.50.19@2x.png](https://api.archbee.com/api/optimize/0p8tQ--ZZOxRtkVp6Qr-e/lDYTrXRpz5wxuKTFJfAaE_cleanshot2024-05-22at1650192x.png)

### Switching your default no-reply address after setting up your new sender address

Once you’ve added your new sender address on the [Email Domains](https://app.ashbyhq.com/admin/organizational-settings/domains) page, navigate to Admin > Organization Setup > [Shared Email Aliases](https://app.ashbyhq.com/admin/organizational-settings/shared-email-aliases). Click `Manage No-Reply Address`.

![](https://cdn.zappy.app/5a0526c59e99f1be4b34cbac0c54ec01.png)

From here, you’ll be able to view your current no-reply address and select your newly configured sender address from the New No-Reply Address dropdown. Once you’ve selected your new no-reply address, click `Update` to confirm. This email address will now be used for all default no-reply emails.

If you’d like to return to the default Ashby no-reply email for future no-reply emails, click `Unshare` beside the configured no-reply address.

::Image[]{src="https://cdn.zappy.app/2bcdfb0415d862d7675073fe6012c956.png" size="78" width="576" height="288" darkWidth="576" darkHeight="288" position="center" showCaption="false"}

:::hint{type="info"}
Please note that if your default no-reply address is not configured to sync emails to Ashby, replies that go to this email address will not appear in Ashby.
:::

## FAQ

:::ExpandableHeading
### Why does my domain status still show as ‘Verifying’ in Ashby after I’ve set the required DNS records on my domain?

If you’ve set the DNS records on your domain, try clicking on `Check DNS Records` in Ashby to refetch the domain’s verification status. This ensures the status you see in Ashby is fully up-to-date.

It can take up to 72 hours for records to finish verifying, so if your status still shows as ‘Verifying’, it’s possible the records are still being published.

You should also confirm that the records were copied exactly as they’re displayed in Ashby. Verify that the quotes around the TXT record’s expected value were included in the record you published on your domain. Also verify that the MX record’s priority (the ‘10’ at the beginning of the MX record’s value in Ashby) is entered correctly in the format required by your domain registrar.
:::

:::ExpandableHeading
### My domain’s verification status shows up as ‘Failed’ in Ashby. What should I do now?

Once your domain’s status shows up as failed, you’ll need to delete the domain’s registration in Ashby, remove any DNS records you’ve set on your domain, and restart the verification process. To delete the verification in Ashby, click on `Remove Domain` in the bottom right corner of the domain’s entry in Ashby.
:::

:::ExpandableHeading
### When and where can a no-reply email be used or is used by default in Ashby?

The following tools in Ashby can be configured to or automatically use the default no-reply email address (either no-reply\@ashbyhq.com or the default you configure):

| Tool                                                 | Description                                                                                                                                                                          | Notes                                                                                                                                                                           |
| ---------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Application confirmation email                       | An automated email sent to the candidate if they submit an application via your job board. This will always use the default no-reply email.                                          | More on configuring this at [Email Template Creation and Management](docId\:wQ6UOYDzwfAtDmZhOPsfJ)                                                                              |
| Referral confirmation email                          | An automated email sent to the referred candidate once they've been referred.                                                                                                        | More on configuring this at [Email Template Creation and Management](docId\:wQ6UOYDzwfAtDmZhOPsfJ)                                                                              |
| Auto-Reject emails                                   | An email sent to the candidate if they've been rejected by auto-reject rules you've configured on job postings. These can be scheduled so they aren't sent immediately on archiving. | More on this at [Auto-Reject Applications](docId\:pDGw-WRUBWyFNzHKa9ota)                                                                                                        |
| Survey automation                                    | Configure automation to send an email to the candidate containing a link to to a survey or questionnaire.                                                                            | Used by default if another email isn’t selected in the automation configuration. More on survey automation options at [Surveys & Questionnaires](docId\:RlbgZsGQLmqCKGbBnYQyp)  |
| Newsletter                                           | Send out newsletters to your talent pools to keep them updated.                                                                                                                      | More on configuring newsletters at [Newsletters](docId\:h9M9sIQyi8ESS69a3z0mr)                                                                                                  |
| Event confirmation emails                            | If a lead signs up to attend a hiring event, an email confirmation is sent out to them.                                                                                              | For more on setting up events, check out [Events](docId\:Eqn6EvlXlKTZOERO21svS)                                                                                                 |
| Initial consent and consent extension requests       | If you have automation configured as part of your consent rules, an email will be sent out to a candidate for their consent or a consent extension.                                  | Want to know more about configuring consent rules and automation? Check out [Data Privacy and Compliance: Configuration](docId:0xpIflEKfhKukBuFqKhi9)                           |
| Bulk application review                              | Rejection emails can be sent from a no-reply email within the bulk application review view.                                                                                          | Read more at [Application Review](docId\:d_nxB_Kdz4fJru4hBCaLb).                                                                                                                |
| Interview confirmation emails                        | An email sent to the candidate at the point an interview is scheduled (if configured).                                                                                               | For more on configuring interview activities, check out [Setting up Schedule Interview Activities](docId:0Z5jM_EQkvZQ_Oqc03Rer)                                                 |
| Candidate activity automations                       | If an automated activity is configured to send an email to the candidate, then this can be sent from a no-reply email.                                                               | More information can be found at [Automated Activities](docId\:MTFnByCNcVNb4MtdsGeqB)                                                                                           |
| Alerts and scheduled dashboard notifications         | When alert or scheduled dashboard notifications are sent, these are sent from a no-reply email.                                                                                      | For further info, check out [Alerts](docId\:fCkR-kKHNMJZ6vuU3kRvW) and [Scheduled Dashboards](docId\:Ttr2OmUg9YQPx1nkCMJS9).                                                    |
| Sending an email to the candidate from their profile | You can opt to use a no-reply email when reaching out to the candidate via the `Email` option on the candidate profile.                                                              | Further information can be found at [Candidate Profile](docId\:xUxT7U73X6OdwYPl89LAV).                                                                                          |
:::

:::ExpandableHeading
### Can you have multiple custom email domains for Newsletters?

Yes, multiple custom email domains can be configured per organization, but additional configuration is required to allow sending.

Users cannot automatically send from verified domains once the DNS settings have been properly configured. Once DNS settings have been configured, an admin must add specific sender email addresses to each domain. Only those explicitly added addresses will appear in the Newsletter `From` dropdown and can be used for sending.
:::

::::ExpandableHeading
### Can verified domain email addresses be used for bulk email sending?

Yes, with the following requirement: 

:::Paragraph{listStyleType="circle" indent="2"}
Email aliases must be shared: Even if the address is verified, the addresses must be shared with users via the shared email alias system. To determine whether the user is allowed to send an email from a given alias, we check that:
:::

:::Paragraph{listStyleType="square" indent="3"}
The email address is verified and available for sending (part of an organization email identity)
:::

:::Paragraph{listStyleType="square" listStart="2" indent="3"}
The user has access to the email address via shared email aliases
:::
::::

:::ExpandableHeading
### What are your bounce rate thresholds?

One important note for sending emails from custom domains - make sure your email lists (e.g. for Newsletters) are clean and debounced.We’ve instituted the following bounce and complaint rate monitoring for custom domain emails to prevent from having our own sending accounts blocked by our email provider.

Bounce rate thresholds:

- Warning: 4% — alerts sent; monitoring closely
- Limit: 5% — sending may be restricted

Complaint rate thresholds:

- Warning: 0.08% — alerts sent; monitoring closely
- Limit: 0.1% — sending may be restricted

How this work&#x73;**:**

- Metrics are checked hourly
- If rates exceed the limit for 2 consecutive hours, sending may be automatically disabled to protect domain reputation.&#x20;

We recommend keeping bounce rates below 4% and complaint rates below 0.08% to avoid restrictions and maintain deliverability.
:::

