> For the complete documentation index, see [llms.txt](https://docs.silkline.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.silkline.ai/configuration/email-configuration.md).

# Email Configuration

Add CNAME records (and optionally DMARC) so Silkline can send authenticated emails from your domain on behalf of users

## Overview

**Time to complete:** less than 5 minutes

**What this does:** This configuration allows users in Silkline to send emails through Silkline that come from their actual email address (e.g., <user@yourdomain.com>). This significantly improves supplier trust and engagement. Silkline uses a "fly-on-the-wall" account to read emails where we are a listed recipient. Silkline does not have access to a user's mailboxes.

### Steps

{% stepper %}
{% step %}

#### Add all of these records to your DNS settings for your domain

Your DNS settings are typically managed through your Domain name registrar (e.g., GoDaddy, Namecheap, etc.) or a dedicated DNS service (e.g., Cloudflare, AWS Route 53).

These records also appear in Silkline under **Organization Settings → Email Settings → Domain Authentication**, with copy buttons for each host and value.

{% hint style="warning" %}
In most DNS managers, **you do not need to enter your domain name in the host value**. Check your DNS manager's existing records and follow this pattern.
{% endhint %}

{% hint style="info" %}
If your DNS is managed in Cloudflare, set each record's proxy status to **DNS only** (gray cloud). Proxied records fail verification.
{% endhint %}

<table><thead><tr><th>Record</th><th width="122.53515625">Type</th><th width="288.2109375">Host</th><th>Value</th></tr></thead><tbody><tr><td>Mail CNAME</td><td>CNAME</td><td><mark style="color:purple;"><strong>emsl</strong></mark>.yourdomain.com</td><td><mark style="color:purple;">u34850381.wl132.sendgrid.net</mark></td></tr><tr><td>DKIM1</td><td>CNAME</td><td><mark style="color:purple;"><strong>sl._domainkey</strong></mark>.yourdomain.com</td><td><mark style="color:purple;">sl.domainkey.u34850381.wl132.sendgrid.net</mark></td></tr><tr><td>DKIM2</td><td>CNAME</td><td><mark style="color:purple;"><strong>sl2._domainkey</strong></mark>.yourdomain.com</td><td><mark style="color:purple;">sl2.domainkey.u34850381.wl132.sendgrid.net</mark></td></tr></tbody></table>
{% endstep %}

{% step %}

#### Add DMARC settings only if you do not have an existing policy defined

{% hint style="warning" %}
Most domain names should already have a DMARC policy defined. **If you already have a DMARC policy defined, you can skip this step.**
{% endhint %}

If you do not yet have a DMARC policy defined, please add this record:

<table><thead><tr><th width="122.53515625">Type</th><th width="288.2109375">Host</th><th>Value</th></tr></thead><tbody><tr><td>TXT</td><td><mark style="color:purple;"><strong>_dmarc</strong></mark>.yourdomain.com</td><td><mark style="color:purple;">v=DMARC1; p=quarantine; rua=mailto:pqjhnvzb@ag.ca.dmarcian.com; ruf=mailto:pqjhnvzb@fr.ca.dmarcian.com; sp=none; fo=0;</mark></td></tr></tbody></table>
{% endstep %}

{% step %}

#### Verify configuration

In Silkline, go to **Organization Settings → Email Settings → Domain Authentication** and click **Verify DNS** next to your domain. When all three records validate, the domain shows as **Verified** and sending on behalf of users is turned on.

If verification fails, check each record against the table above and try again. DNS changes can take up to 48 hours to propagate. You can also let Silkline support know once the records are in place, and we'll verify them for you.
{% endstep %}
{% endstepper %}
