{"id":"69d6d4eed380f58f346f1638","title":"Email Forwarding","path":"how-to/committee/email-articles/email-forwarding","contentMarkdown":"# Email Forwarding and Contact-Us Configuration\n\nThis guide covers how to set up email forwarding for your committee roles, including sending emails to multiple recipients and configuring who receives contact-us form submissions.\n\n## Where to Configure Email Forwarding\n\nAll email forwarding is configured in **Admin → System Configuration → Committee Settings**. Select a committee member to see their settings tabs. The key tabs are:\n\n- **Inbound Forwarding** - controls where emails sent to the role's address (e.g. chairman@your-group.org.uk) are forwarded\n- **Contact Us** - controls where contact-us form submissions for this role are sent\n- **Outbound Email** - configures the sender address used when emails are sent from this role\n- **Email Logs** - shows a log of inbound emails processed for this role (available when forwarding is active)\n\nEach tab includes built-in help documentation at the top explaining its purpose.\n\n## Forwarding Options\n\nFor each committee role, you can choose from three forwarding modes using the dropdown:\n\n- **Member Email** - forwards to the committee member's personal email address from their member record\n- **Custom** - forwards to a specific email address you type in\n- **Multiple** - forwards to several email addresses simultaneously\n\n## Setting Up Multiple Recipients\n\nTo have emails forwarded to more than one person:\n\n1. Go to **Admin → System Configuration → Committee Settings**\n2. Select the committee member/role you want to configure\n3. Click the **Inbound Forwarding** tab (for inbound role-address emails) or the **Contact Us** tab (for contact form submissions)\n4. Change the dropdown to **Multiple**\n5. Add each recipient's email address - you can select from existing members or type addresses manually\n6. Click **Save**\n\nWhen set to Multiple, a Cloudflare Worker is deployed that forwards incoming emails to all the listed recipients simultaneously.\n\nIf an existing Cloudflare Worker is already set up for this role, the system will detect it and offer to import the existing recipients automatically.\n\n## Forwarding Status\n\nA status banner on each role shows the current state of the forwarding rule:\n\n- **Forwarding Active** (green) - the rule is deployed and working\n- **Not Configured** (amber) - no forwarding rule has been set up yet\n- **Outdated** (amber) - the rule needs updating (e.g. recipients have changed)\n- **Not Available** - forwarding is not applicable for this role\n- **Error** (red) - there is a problem with the rule\n\nUse the **Create**, **Update**, or **Delete** buttons to manage the routing rule directly from the page - there is no need to log into Cloudflare.\n\n## Verifying Destination Addresses\n\nEach email address that receives forwarded emails must be verified. When you add a new recipient, the system automatically registers the address with Cloudflare and sends a verification email. The recipient needs to click the confirmation link in that email.\n\nCheck spam/junk folders if the verification email doesn't arrive.\n\n## Configuring Contact-Us Recipients\n\nThe contact-us form on your website sends enquiries to a configured committee role. To change who receives these:\n\n1. Go to **Admin → System Configuration → Committee Settings**\n2. Select the role that handles contact-us enquiries (often Support or Secretary)\n3. Click the **Contact Us** tab\n4. Choose who should receive the form submissions using the forwarding dropdown\n5. For multiple recipients, add all email addresses\n6. Click **Save**\n\nThe Contact Us tab also generates a ready-to-use markdown link that you can embed in your page content. This link directs visitors to the contact form pre-filled with the correct role.\n\n## Email Logs\n\nWhen a role has active forwarding via a Cloudflare Worker, the **Email Logs** tab shows timestamped logs of all inbound email processing, including:\n\n- Sender and recipient addresses\n- Delivery status\n- SPF, DKIM, and DMARC validation results\n\nLogs are sortable and filterable for easy troubleshooting.\n\n## Common Scenarios\n\n### \"I want contact-us emails to go to three committee members\"\nSet the contact-us role's forwarding to **Multiple** and add all three email addresses.\n\n### \"I want to share walk coordinator duties\"\nSet the Walks role's email forwarding to **Multiple** so both coordinators receive walk-related emails.\n\n### \"I'm handing over a role to someone new\"\nChange the committee member assigned to the role, or switch the forwarding to the new person's email using **Custom** or **Member Email**.\n\n### \"I want someone else to be able to edit the website\"\nThis is a separate setting - see [Member Privileges](https://ngx-ramblers.org.uk/how-to/committee/member-admin/member-privileges) for how to assign admin roles.\n\n## Related Guides\n\n- [Member Privileges](https://ngx-ramblers.org.uk/how-to/committee/member-admin/member-privileges) - how to assign admin roles so committee members can edit the site\n- [Walk Leader Contact Settings](https://ngx-ramblers.org.uk/how-to/committee/walks/leader-contact) - how to configure walk leader contact methods\n- [Email Configurations](https://ngx-ramblers.org.uk/how-to/committee/email-articles/mail-settings/email-configurations) - how to set up email templates and sending\n- [Mail Settings](https://ngx-ramblers.org.uk/how-to/committee/email-articles/mail-settings) - overview of all mail settings\n- [Sending Transactional Emails](https://ngx-ramblers.org.uk/how-to/committee/email-articles/sending-transactional-emails) - how to send notification emails","contentHtml":"<h1>Email Forwarding and Contact-Us Configuration</h1>\n<p>This guide covers how to set up email forwarding for your committee roles, including sending emails to multiple recipients and configuring who receives contact-us form submissions.</p>\n<h2>Where to Configure Email Forwarding</h2>\n<p>All email forwarding is configured in <strong>Admin → System Configuration → Committee Settings</strong>. Select a committee member to see their settings tabs. The key tabs are:</p>\n<ul>\n<li><strong>Inbound Forwarding</strong> - controls where emails sent to the role&#39;s address (e.g. <a href=\"mailto:chairman@your-group.org.uk\">chairman@your-group.org.uk</a>) are forwarded</li>\n<li><strong>Contact Us</strong> - controls where contact-us form submissions for this role are sent</li>\n<li><strong>Outbound Email</strong> - configures the sender address used when emails are sent from this role</li>\n<li><strong>Email Logs</strong> - shows a log of inbound emails processed for this role (available when forwarding is active)</li>\n</ul>\n<p>Each tab includes built-in help documentation at the top explaining its purpose.</p>\n<h2>Forwarding Options</h2>\n<p>For each committee role, you can choose from three forwarding modes using the dropdown:</p>\n<ul>\n<li><strong>Member Email</strong> - forwards to the committee member&#39;s personal email address from their member record</li>\n<li><strong>Custom</strong> - forwards to a specific email address you type in</li>\n<li><strong>Multiple</strong> - forwards to several email addresses simultaneously</li>\n</ul>\n<h2>Setting Up Multiple Recipients</h2>\n<p>To have emails forwarded to more than one person:</p>\n<ol>\n<li>Go to <strong>Admin → System Configuration → Committee Settings</strong></li>\n<li>Select the committee member/role you want to configure</li>\n<li>Click the <strong>Inbound Forwarding</strong> tab (for inbound role-address emails) or the <strong>Contact Us</strong> tab (for contact form submissions)</li>\n<li>Change the dropdown to <strong>Multiple</strong></li>\n<li>Add each recipient&#39;s email address - you can select from existing members or type addresses manually</li>\n<li>Click <strong>Save</strong></li>\n</ol>\n<p>When set to Multiple, a Cloudflare Worker is deployed that forwards incoming emails to all the listed recipients simultaneously.</p>\n<p>If an existing Cloudflare Worker is already set up for this role, the system will detect it and offer to import the existing recipients automatically.</p>\n<h2>Forwarding Status</h2>\n<p>A status banner on each role shows the current state of the forwarding rule:</p>\n<ul>\n<li><strong>Forwarding Active</strong> (green) - the rule is deployed and working</li>\n<li><strong>Not Configured</strong> (amber) - no forwarding rule has been set up yet</li>\n<li><strong>Outdated</strong> (amber) - the rule needs updating (e.g. recipients have changed)</li>\n<li><strong>Not Available</strong> - forwarding is not applicable for this role</li>\n<li><strong>Error</strong> (red) - there is a problem with the rule</li>\n</ul>\n<p>Use the <strong>Create</strong>, <strong>Update</strong>, or <strong>Delete</strong> buttons to manage the routing rule directly from the page - there is no need to log into Cloudflare.</p>\n<h2>Verifying Destination Addresses</h2>\n<p>Each email address that receives forwarded emails must be verified. When you add a new recipient, the system automatically registers the address with Cloudflare and sends a verification email. The recipient needs to click the confirmation link in that email.</p>\n<p>Check spam/junk folders if the verification email doesn&#39;t arrive.</p>\n<h2>Configuring Contact-Us Recipients</h2>\n<p>The contact-us form on your website sends enquiries to a configured committee role. To change who receives these:</p>\n<ol>\n<li>Go to <strong>Admin → System Configuration → Committee Settings</strong></li>\n<li>Select the role that handles contact-us enquiries (often Support or Secretary)</li>\n<li>Click the <strong>Contact Us</strong> tab</li>\n<li>Choose who should receive the form submissions using the forwarding dropdown</li>\n<li>For multiple recipients, add all email addresses</li>\n<li>Click <strong>Save</strong></li>\n</ol>\n<p>The Contact Us tab also generates a ready-to-use markdown link that you can embed in your page content. This link directs visitors to the contact form pre-filled with the correct role.</p>\n<h2>Email Logs</h2>\n<p>When a role has active forwarding via a Cloudflare Worker, the <strong>Email Logs</strong> tab shows timestamped logs of all inbound email processing, including:</p>\n<ul>\n<li>Sender and recipient addresses</li>\n<li>Delivery status</li>\n<li>SPF, DKIM, and DMARC validation results</li>\n</ul>\n<p>Logs are sortable and filterable for easy troubleshooting.</p>\n<h2>Common Scenarios</h2>\n<h3>&quot;I want contact-us emails to go to three committee members&quot;</h3>\n<p>Set the contact-us role&#39;s forwarding to <strong>Multiple</strong> and add all three email addresses.</p>\n<h3>&quot;I want to share walk coordinator duties&quot;</h3>\n<p>Set the Walks role&#39;s email forwarding to <strong>Multiple</strong> so both coordinators receive walk-related emails.</p>\n<h3>&quot;I&#39;m handing over a role to someone new&quot;</h3>\n<p>Change the committee member assigned to the role, or switch the forwarding to the new person&#39;s email using <strong>Custom</strong> or <strong>Member Email</strong>.</p>\n<h3>&quot;I want someone else to be able to edit the website&quot;</h3>\n<p>This is a separate setting - see <a href=\"https://ngx-ramblers.org.uk/how-to/committee/member-admin/member-privileges\">Member Privileges</a> for how to assign admin roles.</p>\n<h2>Related Guides</h2>\n<ul>\n<li><a href=\"https://ngx-ramblers.org.uk/how-to/committee/member-admin/member-privileges\">Member Privileges</a> - how to assign admin roles so committee members can edit the site</li>\n<li><a href=\"https://ngx-ramblers.org.uk/how-to/committee/walks/leader-contact\">Walk Leader Contact Settings</a> - how to configure walk leader contact methods</li>\n<li><a href=\"https://ngx-ramblers.org.uk/how-to/committee/email-articles/mail-settings/email-configurations\">Email Configurations</a> - how to set up email templates and sending</li>\n<li><a href=\"https://ngx-ramblers.org.uk/how-to/committee/email-articles/mail-settings\">Mail Settings</a> - overview of all mail settings</li>\n<li><a href=\"https://ngx-ramblers.org.uk/how-to/committee/email-articles/sending-transactional-emails\">Sending Transactional Emails</a> - how to send notification emails</li>\n</ul>\n"}