Mail, not chat
A thread carries a subject that does not change and a flat list of messages: no replies to replies, no connection held open in the background. New matter, new thread.
All modules
People and contact
Messages
A teacher writes "bring your book tomorrow", a student replies "I am away on Thursday". Today it runs through private email, and the school keeps nothing of it. Here the conversation is a record.
Inbox Whole school
Wyjazd na konkurs
Podręczniki na B2
Zebranie zespołu
Wyjazd na konkurs 2 in the thread
E. Kołodziejteacher wt 14:02 Lista chętnych na sobotę jest zamknięta, jedzie ośmioro.
M. Zając wt 14:20 Dobrze, rezerwuję bus na 7:30.
Reply… you have a message
auto school inbox · a thread has a subject, not a room
Messages
What this module does
5
inbox tracks, “Whole school” included
50
messages at a time, then “Earlier”
5000
characters of body, subject up to 120
500
recipients in a single thread
Who may write to whom
The team writes to anyone in the school, a student writes to the whole team, because "I am away on Thursday" belongs at reception too. Student to student, never.
A screen split in half
Threads on the left, the conversation on the right: clicking a row opens it alongside, so moving to the next thread never means closing anything first.
Email says only this much
The notification carries "you have a message": who, in which school, under what subject, and it leads to the inbox. At most one per thread per hour.
Nobody removes someone else's text
The owner sees every thread in the school but deletes none: there is no moderation here. Archiving is a participant's own state, and only your unread message can be taken back.
Who sees what
A module is a permission, and which records may be touched is settled on write, not in the menu.
| Role | Sees | Changes |
|---|---|---|
| Owner | Every thread in the school, other people's included, on “Whole school”. | Writes to anyone. Does not delete other people's posts: there is no moderation. |
| Methodologist | The same as the owner: every thread in the school. | Just as much, and under the same limit: nobody else's text is removed. |
| Teacher | The threads they take part in, and nothing beyond them. | Writes to anyone in the school: students, front desk, management. |
| Student | Their own threads. Someone else's conversation is out of reach. | Writes to the whole team. Writing to another student is not possible. |
The details nobody asks about during a demo
The things that only surface in the third week of working with the module.
What this module does not do
- attachments - the file stays in DocHub and the message carries a link at most
- editing a sent message - undo works until it is read, after that the text stands
- moderation - nobody removes another person's message or another person's thread
- an inbox for guardians - the recipient is an account in this school, and they have none
In pace and in shape. Here a thread has a subject that does not change and a flat list of replies, with no reply to a reply; nothing hangs open in the background, and the unread counter refreshes with navigation. Chat is a separate module: a room without a subject, a live socket, and conversation inside the team only. One is mail, the other a messenger.
No, and the server enforces it rather than the layout. A student writes to the WHOLE team, because “I will not be there on Thursday” belongs at the front desk as much as with the teacher; the “Write” dialog offers them the team and nothing else. Student to student does not pass, because the school has no way to moderate it, and correspondence nobody watches is a promise without cover.
Yes: the owner and the methodologist have a “Whole school” track showing every thread, including those without them. A reply in someone else's thread adds the replier to the conversation, so nobody writes from behind glass. That view cannot be turned into moderation, though: no message and no conversation of another person can be removed from there.
No, because the recipient is a membership, not a student record. Such a person appears dimmed in the picker, labelled “no account”, with a link to Students where the envelope creates the way in: hiding them was worse than useless, because a school with no accounts saw an empty list and the sentence “nothing matches”. Someone invited who has not clicked yet IS a recipient; the message waits.
Your own message yes, but only while nobody else has read it; after that the server refuses, because a history that can be rewritten after the fact is not a history. Editing a sent message does not exist at all. Nobody takes back somebody else's message, the owner included, and the undo is hard: no trace of it is left in the conversation.
For yourself, yes. “Delete for me” takes the conversation off my inbox, which means deleting my participation; for everyone else it stands untouched. A thread the last participant has left disappears along with its messages, since nobody would ever see it again. The archive is gentler and also mine: it hides a thread, and a new reply pulls it back.
They get a letter in their mailbox, but without the text: it says only who wrote, in which school and under what subject, and it leads to the inbox with that thread open. At most one such letter per thread per hour per person, so a conversation does not turn into a stream of notifications. A reply to that letter never comes back into Cerium.
Neither. The recipient is always an account with a way into this school, and a guardian has no account today. Reminders about arrears and about a return date are letters from Finance and Rentals, not messages: the sender here is always a person. Answering an enquiry from outside belongs to CRM.
See Cerium from the inside.
14 days on your groups and instalments. No card, no strings.