> For the complete documentation index, see [llms.txt](https://help.dscout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.dscout.com/private-panels/organization-settings/custom-domain-for-emails.md).

# Custom domain for emails

Your panelists can receive emails from your company's domain, such as <recruitment@abc-research.com>.

{% hint style="info" %}
**Note:** If you have not verified your email domain, you will be limited to sending 50 emails per campaign within a Study.
{% endhint %}

### Create Email Domain

We'll need to verify that you own the domain you'd like to use, for example "abc-research.com". For our own account, this is what the **Domains** section looks like.

![](https://content.gitbook.com/content/T7fhyut5rrQHwe5QRGot/blobs/S1VnvSu1DGXWiB0JF4MC/38087398140436)

{% stepper %}
{% step %}
Navigate to the **Settings** page, scroll down to **Email Domains**, then click **+ Add domain**.
{% endstep %}

{% step %}
Input your website or email domain name, such as `abc-research.com`.
{% endstep %}

{% step %}
You will now be shown a few DNS entries. Please forward them to your IT team in order to complete domain verification.

It may take anywhere from 1 hour to 24 hours for the new DNS entries to show up for our system to verify.
{% endstep %}

{% step %}
After the DNS entries are added, click **Verify** to finalize the process.
{% endstep %}

{% step %}
If the domain is now verified, proceed to the **Create Sender Profile** section below.
{% endstep %}
{% endstepper %}

If you receive a DNS server error after adding records:

{% stepper %}
{% step %}
Confirm your records have propagated using a tool like **dnschecker.org**.
{% endstep %}

{% step %}
Copy and paste the domain name you want to verify.
{% endstep %}

{% step %}
Click the **X** to delete the current request.
{% endstep %}

{% step %}
Add the new domain again.
{% endstep %}

{% step %}
Verify the domain.
{% endstep %}
{% endstepper %}

### Create Sender Profile

Sender profiles are individual email addresses you'll use, for example "<recruitment@abc-research.com>". This is what our own Sender Profiles section looks like.

{% hint style="info" %}
**Note:** The **Sender profiles** section, including the **Add sender profile** button, are only displayed after you've added a custom domain.
{% endhint %}

![](https://content.gitbook.com/content/T7fhyut5rrQHwe5QRGot/blobs/pD6ELh6wb5bgzO3xddrN/38087398142356)

{% stepper %}
{% step %}
Navigate to the **Settings** page, scroll down to **Email Domains**, then click **+ Add sender profile**.
{% endstep %}

{% step %}
After the email domain has been verified and sender profiles have been created, your settings page will look like this:
{% endstep %}
{% endstepper %}

After all is done, your mass emails will look like this:

![](https://content.gitbook.com/content/T7fhyut5rrQHwe5QRGot/blobs/G1TPCXpz5NJIin4DDozK/38087349037076)

{% hint style="info" %}
**Note:** Private Panels was previously managed outside of Dscout, so you may see a different logo and URL in some places. If you have any questions, contact <support@dscout.com>.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.dscout.com/private-panels/organization-settings/custom-domain-for-emails.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.