> For the complete documentation index, see [llms.txt](https://academy.synap.ac/doc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.synap.ac/doc/integrations/custom-email-sender.md). # Custom Email Sender Send Synap emails from your own verified domain. Send Synap emails from an address on your organisation's domain. This provides a more consistent sender identity for your users. {% hint style="success" %} Custom email senders are available on Pro, Business, and Enterprise plans. {% endhint %} ### Before you begin You must own the domain that you want to use. Ask your Synap account manager or support team to enable a custom sender. We will provide DNS records for you to add to your domain. These records confirm that you authorise our email provider, SendGrid, to send email on your behalf. They also support required anti-spam checks. This helps receiving email services trust and deliver your messages. ### Use domain authentication We strongly recommend authenticating the whole domain. This is the most reliable option for email delivery. Single sender verification only confirms one email address. It can be unreliable and is increasingly less trusted by receiving email services. Once you have added the DNS records, tell us. We will verify them and complete the custom sender setup. --- # 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://academy.synap.ac/doc/integrations/custom-email-sender.md?ask=&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.