{"id":"6a8cdc5be8de7e4ce62240be","title":"Committee Role Inbox","path":"how-to/committee/email-articles/committee-role-inbox","contentMarkdown":"# Committee role mailboxes and inbox notifications\n\nThe recommended way to run committee email is the **shared inbox**.\n\nMail sent to a role address (for example `walks@your-group.org.uk`) is delivered into **Admin → Inbox**. The committee reads and replies there. Replies go out from the role address, and the conversation stays with the role when the person holding it changes. Several people can be notified that new mail has arrived, without copying the message into personal inboxes.\n\nThe older [Email Forwarding](https://ngx-ramblers.org.uk/how-to/committee/email-articles/email-forwarding) guide uses a Cloudflare worker to copy role mail on to personal inboxes. That is still supported if a site already uses it. It is not the path to choose for a new setup.\n\nIf the shared inbox is not connected yet, set that up first:\n\n- [Direct-to-inbox](https://ngx-ramblers.org.uk/how-to/technical-articles/2026-07-09-direct-inbox-setup) (no Gmail account)\n- [Gmail inbox](https://ngx-ramblers.org.uk/how-to/technical-articles/2026-05-29-gmail-inbox-setup)\n\nThis page is what you do after that: several addresses on one role, and several people notified when mail arrives.\n\n## Where to configure it\n\n| What | Where |\n|---|---|\n| Role addresses and Brevo senders | **Admin → Committee Settings** → edit a role → **Outbound Email** |\n| Who is notified when new mail arrives | **Admin → Mail Settings → Inbox** → **Role mailboxes** |\n| Your own notify choice | **Profile → Email Subscriptions** → **Inbox notifications** |\n| Read and reply | **Admin → Inbox** |\n\n## Several addresses on one role\n\nOne role can have more than one address on your group's domain. Mail to any of them arrives in the **same** inbox for that role. When you send, you can choose any of them as From.\n\nOpen **Admin → Committee Settings**, edit the role, and open **Outbound Email**.\n\n![](https://ngx-ramblers.org.uk/api/aws/s3/site-content/5eb38f13-cecc-4718-8d10-ff7d6f33b132.png)\n\n*Committee Settings → Outbound Email: generated role and name addresses, default sender, extra local-part field, and the Brevo senders list for this role.*\n\n### Addresses that appear automatically\n\nNGX creates two addresses for you when it can:\n\n- One from the **role description** (for example `ngx-project-lead@your-group.org.uk`)\n- One from the person's **full name** (for example `nick.barrett@your-group.org.uk`)\n\nThey use the group's domain. You do not type the `@domain` part.\n\nIf the role already had a stored address that is neither of those (a leftover such as `walks@`), that stays in the list until you remove it.\n\n### Extra addresses\n\nType only the local part (the bit before `@`) and choose **Add**. NGX rejects an `@` in that field. Every address on the list uses the group's domain.\n\nPick the **default sender** with the radio button. That is the From address when this role sends mail, unless you choose a different one in the composer.\n\nSave the role (and Committee Settings) so extras persist. You do not have to create Brevo senders in order to save the addresses.\n\n### Register the addresses in Brevo\n\nMail cannot be sent from an address until it is a Brevo sender.\n\n1. Use **Create Senders** for any role address that is not registered yet.\n2. **View senders** opens the Brevo senders list on this page (it does not take you to Mail Settings).\n3. **This role** (the default) shows senders for this role. **All senders** shows every sender in the Brevo account.\n4. **Mapped** means the address is on this role's mailbox list. If you remove an address from the list above, the Brevo sender stays. Mapped switches to a cross: it still exists in Brevo, it is just not attached to the role. Delete it with the bin if you no longer want it.\n5. If two Brevo records share the same address (an old name and a new name), a **Duplicate Brevo senders** warning lists the address. Keep the one named like **Role (Person)** and delete the extra.\n\nThe sender **Name** in Brevo is set when the sender is created, as **role description (full name)**. Older records may show only the person's name. **Update Sender Name** renames a record. It does not merge two records for the same address.\n\n![](https://ngx-ramblers.org.uk/api/aws/s3/site-content/14df4232-7294-446f-9038-a41a5e4d133b.png)\n\n*View senders on the role, defaulting to This role. Mapped means the address is on this role's list.*\n\n## Several people notified for one role\n\nThe shared inbox is one mailbox per role. **Notification** is separate: an email (and optional browser notification) that says new mail has arrived. More than one person can be notified for the same role, including a role that has no assigned member.\n\nThis applies however the shared inbox receives mail: direct delivery through Cloudflare, or a connected Gmail account.\n\n### In Mail Settings (the full list)\n\nOpen **Admin → Mail Settings**, **Inbox** tab, and scroll to **Role mailboxes**.\n\nEach role address is a row. Extra addresses for that role are listed under it. For **Notify**, choose one of:\n\n- **No notification** — nobody is emailed when mail arrives. People who can see the inbox still find it in **Admin → Inbox**.\n- **Chosen members or addresses** — add as many people as you need. Search for a member, or type an email and choose **Add**. Each person can later change their own destination in their profile (member address, a different address, or off).\n- **Same recipients as another role** — pick another role and reuse its notify list, so you do not maintain the same people twice.\n\nChanges here save as you go (you will see **Saved**). You do not need to open Committee Settings to add a second person.\n\nRoles and who holds them are still set in **Committee Settings**. This list only decides who is *notified*.\n\n![](https://ngx-ramblers.org.uk/api/aws/s3/site-content/798ec4fd-b622-4060-a2d0-ad9a389fe202.png)\n\n*Mail Settings → Inbox → Role mailboxes: extra addresses listed under each role, and the notify choice (none, chosen people, or the same list as another role).*\n\n### In your profile (your own choice)\n\n**Profile → Email Subscriptions → Inbox notifications** lists the role addresses assigned to you.\n\nFor each one, choose:\n\n- **No notification**\n- **Notify me** (your member email)\n- **Notify a different address** (type a personal address)\n\nYou also see who else is assigned to that role. Use **Save** on the profile page. That change stays in step with the Mail Settings list.\n\n![](https://ngx-ramblers.org.uk/api/aws/s3/site-content/25c4a374-2c36-4556-af83-ef0e3b1da48e.png)\n\n*Profile → Email Subscriptions → Inbox notifications: your own notify choice for a role address assigned to you.*\n\n## What stays the same\n\n- **Admin → Inbox** is still one mailbox per role. Extra addresses do not create extra inboxes.\n- **Contact Us** is still configured on the role in Committee Settings. On an inbox site, those enquiries arrive in that role's inbox.\n- The composer still sends from a role address. If the role has several addresses, you can pick which one.\n\n## Common scenarios\n\n### \"Two people share Walks and both need to know when mail arrives\"\n\nKeep one Walks role and one shared inbox. On **Mail Settings → Inbox → Role mailboxes**, set Walks to **Chosen members or addresses** and add both people. They both open **Admin → Inbox** for that role. Each can turn their own notify email on or off in **Profile → Email Subscriptions**.\n\n### \"We want walks@ and jane.doe@ to be the same mailbox\"\n\nOn the Walks role, keep the generated role address, add `jane.doe` as an extra (or use the generated full-name address), set the default sender, **Create Senders**, and Save.\n\n### \"I removed an extra address and it vanished from the mailbox list, but it is still in Brevo\"\n\nThat is expected. Open **View senders**, stay on **This role**, and you should still see it with Mapped as a cross. Delete it from Brevo if you do not need it.\n\n### \"We still forward role mail to personal inboxes\"\n\nSee [Email Forwarding](https://ngx-ramblers.org.uk/how-to/committee/email-articles/email-forwarding). That is the older worker path and is not recommended for new setup.\n\n## Related guides\n\n- [Email Forwarding](https://ngx-ramblers.org.uk/how-to/committee/email-articles/email-forwarding) — Cloudflare worker copying mail to personal inboxes\n- [Direct-to-inbox setup](https://ngx-ramblers.org.uk/how-to/technical-articles/2026-07-09-direct-inbox-setup)\n- [Gmail inbox setup](https://ngx-ramblers.org.uk/how-to/technical-articles/2026-05-29-gmail-inbox-setup)\n- [Sending Emails](https://ngx-ramblers.org.uk/how-to/committee/email-articles/sending-emails)","contentHtml":"

Committee role mailboxes and inbox notifications

\n

The recommended way to run committee email is the shared inbox.

\n

Mail sent to a role address (for example walks@your-group.org.uk) is delivered into Admin → Inbox. The committee reads and replies there. Replies go out from the role address, and the conversation stays with the role when the person holding it changes. Several people can be notified that new mail has arrived, without copying the message into personal inboxes.

\n

The older Email Forwarding guide uses a Cloudflare worker to copy role mail on to personal inboxes. That is still supported if a site already uses it. It is not the path to choose for a new setup.

\n

If the shared inbox is not connected yet, set that up first:

\n\n

This page is what you do after that: several addresses on one role, and several people notified when mail arrives.

\n

Where to configure it

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
WhatWhere
Role addresses and Brevo sendersAdmin → Committee Settings → edit a role → Outbound Email
Who is notified when new mail arrivesAdmin → Mail Settings → Inbox → Role mailboxes
Your own notify choiceProfile → Email Subscriptions → Inbox notifications
Read and replyAdmin → Inbox
\n

Several addresses on one role

\n

One role can have more than one address on your group's domain. Mail to any of them arrives in the same inbox for that role. When you send, you can choose any of them as From.

\n

Open Admin → Committee Settings, edit the role, and open Outbound Email.

\n

\"\"

\n

Committee Settings → Outbound Email: generated role and name addresses, default sender, extra local-part field, and the Brevo senders list for this role.

\n

Addresses that appear automatically

\n

NGX creates two addresses for you when it can:

\n\n

They use the group's domain. You do not type the @domain part.

\n

If the role already had a stored address that is neither of those (a leftover such as walks@), that stays in the list until you remove it.

\n

Extra addresses

\n

Type only the local part (the bit before @) and choose Add. NGX rejects an @ in that field. Every address on the list uses the group's domain.

\n

Pick the default sender with the radio button. That is the From address when this role sends mail, unless you choose a different one in the composer.

\n

Save the role (and Committee Settings) so extras persist. You do not have to create Brevo senders in order to save the addresses.

\n

Register the addresses in Brevo

\n

Mail cannot be sent from an address until it is a Brevo sender.

\n
    \n
  1. Use Create Senders for any role address that is not registered yet.
    2. \n
  2. View senders opens the Brevo senders list on this page (it does not take you to Mail Settings).
    3. \n
  3. This role (the default) shows senders for this role. All senders shows every sender in the Brevo account.
    4. \n
  4. Mapped means the address is on this role's mailbox list. If you remove an address from the list above, the Brevo sender stays. Mapped switches to a cross: it still exists in Brevo, it is just not attached to the role. Delete it with the bin if you no longer want it.
    5. \n
  5. If two Brevo records share the same address (an old name and a new name), a Duplicate Brevo senders warning lists the address. Keep the one named like Role (Person) and delete the extra.
    6. \n
\n

The sender Name in Brevo is set when the sender is created, as role description (full name). Older records may show only the person's name. Update Sender Name renames a record. It does not merge two records for the same address.

\n

\"\"

\n

View senders on the role, defaulting to This role. Mapped means the address is on this role's list.

\n

Several people notified for one role

\n

The shared inbox is one mailbox per role. Notification is separate: an email (and optional browser notification) that says new mail has arrived. More than one person can be notified for the same role, including a role that has no assigned member.

\n

This applies however the shared inbox receives mail: direct delivery through Cloudflare, or a connected Gmail account.

\n

In Mail Settings (the full list)

\n

Open Admin → Mail Settings, Inbox tab, and scroll to Role mailboxes.

\n

Each role address is a row. Extra addresses for that role are listed under it. For Notify, choose one of:

\n\n

Changes here save as you go (you will see Saved). You do not need to open Committee Settings to add a second person.

\n

Roles and who holds them are still set in Committee Settings. This list only decides who is notified.

\n

\"\"

\n

Mail Settings → Inbox → Role mailboxes: extra addresses listed under each role, and the notify choice (none, chosen people, or the same list as another role).

\n

In your profile (your own choice)

\n

Profile → Email Subscriptions → Inbox notifications lists the role addresses assigned to you.

\n

For each one, choose:

\n\n

You also see who else is assigned to that role. Use Save on the profile page. That change stays in step with the Mail Settings list.

\n

\"\"

\n

Profile → Email Subscriptions → Inbox notifications: your own notify choice for a role address assigned to you.

\n

What stays the same

\n\n

Common scenarios

\n

"Two people share Walks and both need to know when mail arrives"

\n

Keep one Walks role and one shared inbox. On Mail Settings → Inbox → Role mailboxes, set Walks to Chosen members or addresses and add both people. They both open Admin → Inbox for that role. Each can turn their own notify email on or off in Profile → Email Subscriptions.

\n

"We want walks@ and jane.doe@ to be the same mailbox"

\n

On the Walks role, keep the generated role address, add jane.doe as an extra (or use the generated full-name address), set the default sender, Create Senders, and Save.

\n

"I removed an extra address and it vanished from the mailbox list, but it is still in Brevo"

\n

That is expected. Open View senders, stay on This role, and you should still see it with Mapped as a cross. Delete it from Brevo if you do not need it.

\n

"We still forward role mail to personal inboxes"

\n

See Email Forwarding. That is the older worker path and is not recommended for new setup.

\n

Related guides

\n\n"}