Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Updated subdomain delegation docs with reverting the control to customer #36

Merged
merged 2 commits into from
Dec 15, 2023
Merged

Updated subdomain delegation docs with reverting the control to customer #36

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
28a2447
Updated subdomain delegation docs with reverting the control to customer
Dec 15, 2023
1650564
Improved revoke delegation docs
Dec 15, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 12 additions & 2 deletions docs/messaging/email-settings.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,16 +10,26 @@ sidebar_position: 1
[[SDK](https://www.npmjs.com/package/@epilot/email-settings-client)]
[[Setup Docs](https://help.epilot.cloud/hc/de/articles/5573710208412-E-Mail-Konfigurationsmen%C3%BC-im-Detail-epilot-360-#h_01GA1JYMPGHRE0XDCHW9N61G57)]

Epilot not only provides the capability to send emails using our domain but also allows clients to bring their own subdomains. This enables messages to be sent and received via epilot, acting on behalf of your own organization. It is highly recommended that an IT professional from your company, who is well-versed with DNS records, handle this integration.
Epilot not only provides the capability to send emails using our domain but also allows customers to bring their own subdomains. This enables messages to be sent and received via epilot, acting on behalf of your own organization. It is highly recommended that an IT professional from your company, who is well-versed with DNS records, handle this integration.

### Subdomain Delegation:
While setting up the subdomain, a process known as 'subdomain delegation' is required. With this setup:

- The subdomain will be managed by epilot.
- The subdomain will be managed by epilot by giving complete control.
- Its primary role will be to enable the sending and receiving of emails.
- This subdomain can be further configured to serve as a dedicated portal for end customers or installers.
- More on the portal domain setup [here](https://help.epilot.cloud/hc/de/articles/4417739340050-Kundenportal-einrichten-epilot-360-#h_01GC9GHGN6788D2GDVE6H0BVVQ).

### Optional: Managing the subdomain yourself

During the initial subdomain setup we require the subdomain to be delegated to epilot nameservers for provisioning, however after the initial setup is complete customers may opt to manage the subdomain using their own DNS.

Get in touch with [epilot support]([email protected]) if you would like to transfer the nameservers for your own subdomain, and we will provide the required DNS setup to manage your own epilot subdomains.

:::note
For customers managing their own subdomain, you may be asked to manually change DNS records from time to time to ensure epilot works correctly and securely. This is not needed when the subdomain is delegated to epilot.
:::

### SPF, DMARC, and DKIM Implementation:
- After the domain is delegated to us, we handle the creation of all the necessary MX & TXT records in our AWS hosted zone. This includes:
- SPF (Sender Policy Framework) to specify the servers that are allowed to send email for your domain.
Expand Down