25-Aug-2026 — contact-us delivered to the shared inbox #338

build 855 — commit 172d618 · build 857 — commit 2d1162b

What's new

Website enquiries on direct-to-inbox sites could still be sent straight to committee members' personal addresses. The enquiries rename migration had backfilled contact-us delivery overrides from the forwarding settings of the time, and those snapshots kept their pre-inbox routing after a site switched over to the shared inbox. A migration now clears those legacy overrides on sites whose inbox provider delivers direct to the inbox, so enquiries store into the shared inbox under the role and notify its configured recipients.

With the overrides cleared, roles with no stored override showed an empty "Send contact-us submissions to" selection in Committee Settings, even though the delivery summary beneath it was correct. The form now initialises the selection to the effective target - the role's forwarding target, with the custom address or recipients list filled in when that is the fallback - so the dropdown always shows what actually happens.

At a glance

• Contact-us form submissions on direct-to-inbox sites arrive in the shared inbox under the role, and the role's notify recipients get a notification
• Legacy delivery overrides that sent enquiries to personal addresses are cleared automatically by a migration
• Committee Settings always shows the effective contact-us delivery target instead of a blank selection
• Migration scripts now use typed enums instead of string literals for config keys, delivery targets and role values