Product Update - June 03, 2026

Product Changelog — June 3, 2026

---

Recurring Event Per-Occurrence Editing — Google-style scope chooser for recurring events

Editing a recurring event in the Calendar now opens a scope chooser — "This event," "This and following," or "All events" — so you can adjust a single instance without disrupting the entire series. Per-occurrence overrides (title, description, location) are stored independently and inherit from the series when not changed. This solves the long-standing all-or-nothing limitation where changing one meeting required editing the entire recurrence rule.

Use case: A weekly team standup has a one-off agenda change for next Tuesday — the organizer edits just that occurrence without affecting any other meeting in the series.

Available in: Calendar → Events → Recurring Events

---

Enforced Broadcast Approval Workflows — Hard editorial gate before broadcasts go live

Admins can now bind an approval workflow to the broadcast surface and mark it as "enforced," preventing non-admin senders from publishing or scheduling any broadcast without a prior approved request. In advisory mode the existing direct-send path remains available; in enforced mode the publish and schedule buttons are blocked until approval is granted. Per-actor logic ensures admins always bypass the gate, and a dedicated "pending requests" view lets authors resubmit if a request is rejected or withdrawn.

Use case: An HR communications manager wants to ensure all company-wide announcements are reviewed by legal before going live — enforced mode stops any unreviewed broadcast from being scheduled.

Available in: Comms Hub → Broadcasts → Approval Workflows

---

Attribute-Based Audience Targeting for Emergency Alerts — Precise targeting replaces all-or-nothing fan-out

Emergency alerts now support the same rich audience picker available in broadcasts: target recipients by department, location, job title, organizational role, named groups, specific individuals, or everyone. A live recipient-reach counter updates as you build the audience so senders know the estimated head count before the alert goes out. Alerts can also be routed through an approval workflow consistent with broadcast governance, ensuring critical communications follow the same review controls as standard messaging.

Use case: A facilities manager needs to alert only employees physically located at the downtown office about a building evacuation — they target by location and see the exact recipient count before sending.

Available in: Critical Alerts → Comms Hub → Emergency Alerts

---