25-Aug-2026 — multiple email addresses and notify recipients per committee role #364

build 852 — commit be92a79 · build 853 — commit b6393a9 · build 854 — commit 65bd81d

What's new

Committee role mailboxes can now notify any number of people when new mail arrives in the shared inbox, closing the gap left when a group moves from Cloudflare worker forwarding (which could copy a shared address out to several personal inboxes) to the shared inbox (which could previously notify only the one assigned member). Each role can also have several addresses on the group's domain, so an officer can use both a role-style address and a name-style address, plus extras, with incoming mail to any of them arriving in the same role inbox and outgoing mail able to use any of them as From.

Note: A step-by-step guide, with screenshots, is in Committee role mailboxes and inbox notifications.

At a glance

• In Mail Settings, under Inbox, each role mailbox has a notify choice: no notification, a list of members or addresses, or the same people already set on another role. A role with no assigned member can still have a notify list.
• Members on a role can manage their own notification choice on their profile Email Subscriptions page, which also shows who else is assigned to that role.
• Inbox digest emails and browser notifications go to every opted-in recipient, including when a role reuses another role's list.
• Committee Settings Outbound Email lists the role's addresses: a generated address from the role description, one from the person's name where it differs, and extras added as a local part only. Choose the default sender with the radio list.
• Incoming mail to any of those addresses arrives in the same role inbox, and the inbox shows which address was used. Replies can send from the address the message was received on, and the composer can send from any of the role's addresses.
• Create Senders registers every listed address with Brevo. View senders opens the senders table on the role, defaulting to This role, with All senders when you need the rest of the account.
• Mapped means the address is on the role's list. Removing an address from the role keeps the Brevo sender and marks it unmapped. Two Brevo records for the same address show a duplicate warning so the extra can be deleted.
• The route-to-inbox action creates Cloudflare routing rules for any role address that does not have one yet.
• Two committee roles with the same description keep their own notify lists, and saving Committee Settings gives each a distinct role type so they no longer overwrite one another.

Refinements in builds 853 and 854

The notify list on Mail Settings was offering committee role addresses (and other addresses on the group's own domain) as if they were people to email when new inbox mail arrived; choosing those would send the notification back into the shared inbox. That list now only offers addresses outside this site's inbox routing - a personal address, or a member's address on another NGX site, is fine. You can add more than one by typing and pressing Enter, and the field matches the size of the controls around it.

Long committee role titles that list several jobs in one description produced email addresses that mail providers reject, because the part before @ was too long. The role address now uses the first part of the title (before a comma, or a similar break), so each role still has a unique, valid address and Create Senders can register it. And when a long role title is shortened to a valid address, the previously generated address no longer stays behind on the Email addresses list as if it had been typed in - the leftover is removed, while addresses you added yourself are kept.

• Addresses that route into this site's shared inbox no longer appear in Add people to notify and cannot be typed in; any address outside this site's routing works, including a member's address on another NGX site
• Type a complete address and press Enter to add it; existing addresses stay on the list
• A long role title uses only its first part for the role email, keeping the part before @ within limits; if two roles would share that first part, the second address is made unique from the member's name
• Shortening a role title removes the superseded generated address; Create Senders is not offered for it; typed extras are unchanged

Also in build 852: the public Codebase Evolution dashboard was refreshed with figures as of 24 August 2026.