# 05-Jul-2026 — Social admins can send notifications too

## [build 746](https://github.com/nbarrett/ngx-ramblers/actions/runs/28757133999) — [commit 3f69f23](https://github.com/nbarrett/ngx-ramblers/commit/3f69f23f577f455d3d4a33034e5157a5010a53c9)

_____

## What's new

- Until now, only committee members could open the email composer and send a notification. A social admin (someone who runs social events but is not on the committee) who clicked Send Notification was bounced back to the home page.
- Social admins can now use the email composer and send notifications as well. The inbox and walks admin stay committee-only.

_____

## Catch-all email: a clear prompt when a forwarding address needs verifying

## [build 746](https://github.com/nbarrett/ngx-ramblers/actions/runs/28757133999) — [commit e85448c](https://github.com/nbarrett/ngx-ramblers/commit/e85448cdc7592c5e2593c4373bcd3856f7a47843)

_____

## What's new

When you forward catch-all email to a single address (for example a connected Gmail inbox), that address has to be verified with Cloudflare first. Before, there was no sign when it was not verified, so saving simply failed, and if the address was already registered but not yet confirmed there was no way to send the verification email again.

- The catch-all editor now shows a clear "Destination not verified" warning, with a "Register & Verify" or "Resend verification" button, whenever the chosen forwarding address has not been verified. It checks the live status each time you open the editor.
- The button sends a fresh verification email, so the owner of that address gets a new link to confirm it. If you have hit Cloudflare's limit on how often this can be done, the editor tells you.

![](https://ngx-ramblers.org.uk/api/aws/s3/site-content/2e5c695a-3dad-483a-96af-52918528c871.png)