# Email Domains {% hint style="info" %} The number of email domains that can be added depends on the subscription plan. {% endhint %} {% hint style="warning" %} Requires the **Manage/View email template alerts & domains** user permissions to edit or view. {% endhint %} *** ## Purpose Email domains are the custom email address domains or subdomains (e.g. *acme.com* or *mail.acme.com*) that your live agents can use to reply to a ticket's emails. If an email domain is not configured, emails will be sent and received from a default ** address. To manage email domains, go the [settings panel](https://documentation.proto.cx/docs/settings/settings) and select **Email Domains**. *** ## Add an Email Domain 1. Select **Create Email Domain**. 2. In the opened settings panel, set the options only available during creation: * **Domain** — the domain or subdomain to be used for sending and receiving emails, e.g. *acme.com* for a domain or *mail.acme.com* for a subdomain. * **Automatic security** — sets the security protocol: * **Enable automatic security** — uses CNAME records to verify domain ownership. Only works for subdomains, such as *mail.acme.com*. * **Disable automatic security** — uses MX and TXT records to verify domain ownership. Best for verifying root domains, such as *acme.com*. 3. Select **Create**. #### Add Email Domain Icon 1. Select **Create Email Domain.** 2. In the opened settings panel, choose Upload Icon. 3. Select **Create.**

*** ## Setup an Email Domain Select an **Email Domain** from the table to open its settings. ### DNS Records For an email domain to operate, the [DNS records](https://en.wikipedia.org/wiki/List_of_DNS_record_types) provided by Proto AICX need to be added to the domain host's DNS settings. These records enable the secure trafficking of emails between different systems. Popular domain hosts like GoDaddy and Namecheap will automatically add your root domain to DNS records. For instance, if your domain is *acme.com*, and your CNAME record is *mail.acme.com*, you should add *mail* as the host instead of *mail.acme.com*. The "@" symbol is used to represent the root domain. For example, if adding a record for *website.com*, you should add "@" as the host. Be sure to check your domain host's documentation for specific instructions. In the **Installation** tab, see the records required and their verification status. Press **Verify** to run a new verification check. *** ### Email Addresses Once email domain is verified in the DNS Records tab above, the **Email Addresses** tab will be enabled, allowing you to configure different addresses for sending and receiving emails within a ticket. #### Add Address 1. Go to the the Email Addresses tab. 2. Select **Create Email Address**. 3. In the opened menu, set the: 1. **Domain** — the actual address. 2. **Name type** — the name associated with the email address. 3. **Create tickets from emails** — toggles if new tickets wil be created from each inbound email not associated with an existing ticket. 4. Press **Create**. It is not possible to modify an existing email address. #### Delete Address 1. Go to the Email Addresses tab. 2. Select one or more **email addresses** from the table. 3. Press **Delete email addresses** and confirm. *** ## Delete Email Domain 1. Select an **email domain** from the table. 2. In the opened subpage, select **Delete Email Domain** and confirm. *** ## DNS Examples The following examples illustrate the DNS records setup process in conjunction with the Installation tab above. ### NameCheap In Namecheap, the DNS system automatically adds the domain name to the values submitted during record creation. Make sure that your domain name is not duplicated in the values (e.g., that you enter your subdomain just like *mysubdomain* and not like *mysubdomain.company.com*). "*@*" will point to the root domain (for example *company.com*). The MX records go in a different section.

Records for the *company.com* email domain in Proto AICX.

*** ### AWS Route 53 In AWS dashboard, don't add the whole domain to the **Record name** field while creating a record. To route traffic for the name of the domain, such as *example.com*, leave the **Record name** field blank. The default value is the name of the hosted zone. To route traffic for a subdomain, such as *[www.example.com](http://www.example.com)*, enter the subdomain name but without the domain name. For example, to route traffic for *[www.example.com](http://www.example.com)*, enter only *www*. Once the record us created, the **Record name** field contains full info with subdomain and domain names. All records (MX, TXT, etc) are in the same section.