Skip to main content

Messaging module

In-app direct messages and group chats, with mute, reactions, attachments, and real-time delivery — for quick coordination that doesn't belong in a public Engage thread.

Optional module Enable in Settings → Modules

Messaging is the in-app chat layer. Members can start one-on-one conversations or named group chats, attach files, react with emoji, and receive new messages in real time on web and mobile. It is the right surface for short, time-sensitive coordination — anything that would otherwise become a half-thread in Engage.

Who this module is for​

  • Members — direct messages with chapter brothers and sisters, group chats for committees and pledge classes
  • Officers — small-team coordination for exec board, recruitment, philanthropy chairs
  • Org admins — turning the module on, configuring auto-created chats, setting attachment limits

What gets enabled​

When Messaging is turned on for an org:

  • Messaging becomes reachable through the unified messaging + GreekManageAI panel — the floating icon in the bottom-right corner of every page, shared with the AI Services module. The panel shows human conversations and GreekManageAI (one ongoing conversation, not a history of threads) together in one recency-sorted list with search and an in-panel "new message" recipient picker. (If AI Services is also enabled, the same icon opens both; if only Messaging is enabled, the panel shows human conversations only.)
  • Members can open direct (1:1) and group conversations, with named groups that admins can rename, add/remove members from, and promote others within
  • Each conversation tracks unread counts and lets members mute the conversation
  • Members can react with emoji to any message, and the reaction is visible to every other participant
  • Messages support file attachments, governed by an org-level max size and an allowed-types list
  • Delivery is real-time — new messages stream through a WebSocket and arrive without a refresh, on web and inside the mobile app
  • Push notifications fire for new messages on iOS and Android
  • Read receipts are recorded per message per user

A dedicated admin panel (Org → Settings → Messaging) surfaces toggles for auto-created chats (per chapter, per region, per pledge class, per exec board) — when enabled, the platform creates and maintains the relevant group chat and keeps its membership in sync as chapters, regions, pledge classes, and the exec board roster change over time.

Common workflows​

For members​

For org admins​

After enabling​

What's not in this module today​

  • Per-user read-receipt opt-out. Every read is recorded for every user. There is no switch to turn this off either at the user level or at the org level.
  • Automatic retention or expiry. Messages and conversations are kept until manually deleted or until the underlying org is deleted. There is no auto-purge after N days.
  • Legal hold / e-discovery. No in-product workflow to freeze or export a conversation under legal hold.
  • Group-size cap. Groups are not capped in code. Set a policy if your org needs a limit.
  • "Delete for everyone." Members can edit and delete their own sent messages (a deleted message renders as "This message was deleted" for all participants), but there's no admin/sender tool to remove a message from every participant's view beyond that.
  • Per-response AI features. Source citations, thumbs-up / thumbs-down, and persisted conversation history belong to the AI chatbot, not to Messages.

Where to go deeper​

Dependencies​

  • Storage — attachments live in your org's storage bucket
  • Notifications — for delivery alerts
  • Mobile push — for real-time delivery on iOS and Android
  • Community — the public alternative; use Engage when the conversation belongs in the open
  • AI Services — the chatbot can summarize a long conversation thread

Last verified against v0.65.37 (2026-07-12). The "if only Messaging is enabled, the panel shows human conversations only" behavior is enforced in the UI as of v0.65.37 — before that, the Chat with GreekManageAI button appeared even without AI Services licensed (the backend still blocked it). Corrected stale "auto-chat admin panel not wired" claim (MessagingSettingsPanel mounted at Org → Settings → Messaging since v0.63.22; toggle-driven reconciliation wired v0.65.11); updated to the unified messaging+GreekManageAI panel framing (replaces the old floating-chat-widget-only entry point, v0.65.23); removed stale "no edit/delete UI" and "mute toggle not surfaced" claims (both shipped v0.63.22, per org-admins/messages-admin.mdx).