Home › Messaging & Communication
A group chat treats every member the same. All Mighty Sync doesn't: who can message whom is governed by role and group, students under 13 have a hard messaging block that no setting can override, and every conversation and announcement is scoped instead of broadcast to everyone by default.
Request a DemoA thread started by a parent or student begins as "pending" - the recipient, a teacher or admin, has to accept it before it becomes a full conversation.
A thread started by an admin or teacher opens directly, with no pending step, since staff-initiated contact doesn't need the same gate.
A reply from either side automatically flips a pending thread to open - no separate "accept" click required once the conversation is actually happening.
Admins can message anyone. Teachers can message students and parents within their own groups only. Parents and students can message teachers of their own group only - never each other.
Announcements are one-to-many and tied to a group, or optionally to a specific class instance. Targeting options include sending directly to students who were absent from a particular class - useful for reaching exactly the people who missed something, not everyone. Admins can also send organization-wide announcements when something applies to the whole organization.
Students under 13 cannot send messages under any circumstances. This is enforced unconditionally, regardless of any organization setting - there is no toggle that changes it.
Students aged 13 and above can message only if the organization has explicitly enabled student messaging - off by default, not on by default.
Students granted teaching capability for specific groups are treated as teachers for messaging purposes - but only within those specific groups, not organization-wide.
Every message and announcement triggers a push notification to its relevant recipients. The in-app notification center keeps the full history regardless of whether the push itself was actually delivered, and per-user notification preferences are enforced server-side - applying the same way no matter which part of the system generated the notification.
No. Messaging follows fixed rules by role. Admins can message anyone. Teachers can message students and parents within their own groups only. Parents and students can message teachers of their own group only. Students under 13 cannot send messages under any circumstances, regardless of organization settings. Students 13 and older can message only if the organization has enabled student messaging.
A thread started by a parent or student begins as pending until the recipient - a teacher or admin - accepts it. A thread started by an admin or teacher opens directly, no acceptance step required. A reply from either side automatically flips a pending thread to open.
Yes. Announcements are one-to-many and tied to a group or, optionally, a specific class instance. Targeting options include sending directly to students who were absent from a specific class. Admins can also send organization-wide announcements.
Yes. Students under 13 cannot send messages under any circumstances - this is enforced unconditionally and cannot be overridden by any organization setting. Students granted teaching capability for specific groups are treated as teachers for messaging purposes within those groups only.
Every message and announcement triggers a push notification to its recipients, and the in-app notification center stores the full history regardless of whether the push itself was delivered. Per-user notification preferences are enforced server-side and apply identically no matter which part of the system generated the notification.
Request a demo and see how threads, announcements and the student safety gate work together in practice.