> For the complete documentation index, see [llms.txt](https://docs.eventflowapp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eventflowapp.com/eventflow-cms/email-settings.md). # Email settings The Manage Emails page allows you to configure global email settings used across Eventflow. This includes setting the Support Email, Reply-To Email, and the From Email Address. ### Global email settings #### Support & Reply-To Email Address The Support Email and Reply-To Email serve as the main contact email for your application: * This address is used across all emails sent from Eventflow. * Any replies from exhibitors or other recipients will be directed to this address. * This is especially useful if your support email is different from the domain used for your exhibitor manual. * To set the Support / Reply-To Email, simply enter the desired email address in the Support / Reply-To Email field. #### From Email Address The From Email Address determines the sender address for all outgoing emails from the application. * By default, this is set to an Eventflow system email address. * If you want to use your own domain, Eventflow staff will need to make this change for you. Please contact us to request an update. #### Stand-share approval notifications Under **Admin > Emails**, use: * **Send approval requests to** to choose where new stand-share requests are sent for review. * **Approval request Reply-To** to choose where replies to those notifications are delivered. If either field is left blank, Eventflow uses the application’s **Support / Reply-To Email**. #### Protecting email-delivery DNS records If Eventflow sends email using your organisation's domain, your DNS administrator may need to maintain email-authentication records supplied by Eventflow. These can include a CNAME record for the email Return-Path. Treat these records as production dependencies: * Do not remove or change them while Eventflow sends from the domain. * Preserve them during website migrations, DNS-provider changes and agency handovers. * Mark them as protected or business-critical with your DNS provider where possible. * Contact Eventflow before making changes. If Eventflow emails experience delivery or authentication problems, ask your DNS administrator to confirm that the supplied records still exist and retain their original values. Do not copy DNS values from another organisation or event, as the required configuration may differ. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.eventflowapp.com/eventflow-cms/email-settings.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.