Communications

Notifications carry a recipient, an actor, a kind, a title and body, a link back to what they concern, and read state. Delivery runs over four channels — in-app, email, SMS and browser push — with per-user, per-kind preferences.

Email is branded per organization: the organization’s abbreviation and name lead, its theme colours and support address are used, and mail is sent from the organization’s own sender address where configured.

Threads are organization-scoped and come in two kinds: private conversations between administrators and one member, and shared threads where administrators coordinate. A thread can be bound to a membership application, which keeps the correspondence with the record it concerns.

Participants carry their own read state, so unread counts are per person.

The signed-in member feed. Members post with images, like and comment. Alongside member posts, the platform generates entries for organization activity — new events, courses, publications and members — each with per-user read state so the feed can show what is new.

A managed communications service, available to organizations that subscribe. It runs campaigns with milestones and tasks, content workflows from brief through draft to channel placement, multi-step approval workflows, publication and metric collection, brand asset management, monitoring with escalations, and reporting on a defined cadence. Every action is recorded on an append-only audit timeline.

Engage has its own operations console for the service team, separate from the organization-facing screens under /admin/engage (opens in a new tab).