Product Update - September 25, 2026

Delegated Sending in Communications — Send internal announcements on behalf of an executive

Communications now lets one person send messages as another. An executive, a site leader or a department head can name a delegate — an assistant or a member of the communications team — who writes and sends on their behalf, with the leader's name on the byline. The leader can ask to review each message before it goes out, and approves or returns it from a Reviews page. Admins also get a single "Who can send what" page that sets which roles may send each type of message, how far a manager's messages can reach, and which channels, such as SMS, each sender may use. A message scheduled for later is checked again when it goes out, so it never reaches people its sender is no longer allowed to message.

Use case: A regional director lets their chief of staff draft and send the weekly update under the director's name, and reviews each one before it reaches the 400 people in the region.

Available in: Communications → Delegates

---

Contract Events and Learned Approvals — Contract lifecycle automation and auto-approval for repeat contracts

Contracts now announce the moments that matter — signed, activated, renewed, expired, terminated, and upcoming obligation or renewal dates — to webhooks and automation rules, so other systems and workflows can act on them without anyone copying the details across. For approvals, the platform notices when the same vendor and contract type have been approved several times on the same terms without a rejection, and proposes that pattern to a Contracts admin. Once the admin accepts it, matching contracts are approved automatically, each one logged and announced to the approvers, and any approval can be reversed within 30 days until the contract is signed. Automatic approval pauses whenever the organisation pauses automation, and it never applies above the legal review threshold or to contracts flagged as risky.

Use case: A procurement team that renews the same software subscription with the same vendor every quarter stops routing each renewal through three approvers, while a new vendor or changed terms still goes through full review.

Available in: Contracts → Settings → Approvals

---

Client Portal Reply Control and Leave Workspace — Read-only client portal for project updates

Workspace owners who share project updates with clients can now decide whether those clients may reply. A new "Clients can reply" switch sits on the External access card. It is on by default, so existing portals keep working as they do today. Turned off, the portal becomes a read-only view of the updates, and invitation and digest emails no longer invite a reply. Separately, members and viewers can now leave a workspace they no longer need, from the web, the phone app or the API. A workspace's only owner cannot leave until they hand ownership to someone else.

Use case: An agency shares weekly progress with a client's executives through the portal but wants feedback to come through their account manager, so they switch client replies off and the portal becomes a status page.

Available in: Workspace → Workspace → External access → Clients can reply