Team only
Only people who work at the school write and read. Students and guardians have no way in; Messages serve them.
All modules
People and contact
Chat
"Room 3 or 4?", "the printer is stuck", "who covers the class?". Today the team handles it on WhatsApp next to holiday photos. Here the conversation lives in the panel, team only, with an expiry.
ZA MZ RE EK team only
Zastępstwa group · 6 people live
M. Zając Drukarka w sekretariacie znowu stoi.
Zgłoszone, ma być dziś.
M. Zając is typing…
Message the room… _
auto a team room · no subject and no students
Chat
What this module does
2
kinds of room: a 1:1 pair and a group
200
people in one group, a constant, not a limit
4000
characters in a single message
50
messages per read, the rest pulled upwards
Conversation or group
A 1:1 conversation is one per pair, a group has a name and a founder. Anyone adds people and leaves; the founder and management run the group.
Live, no refresh
A message shows up on the other side the moment it is sent, and "typing..." says a reply is on its way. After a dropped connection the window catches up by itself.
Endless history, with a term
Scrolling up loads earlier messages. The operator can set after how many days they disappear: chat does not have to stay forever.
Private rooms
The owner sees only conversations they are in. Authors edit and delete their own messages; someone else's, in a group, only whoever runs it.
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 | Only the rooms they sit in. There is no “Whole school” track here. | Their own messages, and in a group they belong to: name, members, deletion. |
| Methodologist | The same as the owner: their own rooms and not one other. | The same: their own messages and charge of the groups they sit in. |
| Teacher | Their own rooms. People to write to come from the list of staff with accounts. | Their own messages and the groups they founded. Nothing in someone else's pair. |
| Student | Nothing. The routes answer “no such screen”, not “not allowed”. | Nothing. A school talking to a student belongs to Messages. |
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 or files - a pointer to DocHub comes in stage 2, the bytes stay in the bucket
- mail about unread messages - whoever is not in the panel sees the badge on arrival
- an “online” marker, reactions, mentions or searching the history - that is stage 2
- chat above a school - a branch network has none, a talk never leaves its space
Because it does not belong to the school. The history walks out with the person, private numbers circulate around the team, and once somebody leaves there is nothing to hand back. Here the circle of people is school membership: a deleted membership takes the person out of the rooms, a pair conversation with nobody left disappears, and the history has a term after which it clears itself.
No, and three independent locks see to it. A team gate stands first in every handler and answers “no such screen” rather than “not allowed”. The permission matrix grants a student not a single action on chat. The default set does not give them the module. Granting the module by hand changes nothing either, because the routes never ask about the grant.
No. Rooms are private: a room the asker is not in does not exist, for the owner as well. The “Whole school” track that opens every thread in Messages is deliberately absent here. Running the school gives admin rights inside a group you sit in, not a view of all of them.
As long as the operator sets on the client's card; an empty field means “never clear”. Once a term is set, the scheduler takes a batch of a thousand oldest messages per school every ten minutes, so a year of history goes in a few hours and the table is never locked for longer than one short transaction.
Nothing that cannot be caught up. Every write goes over ordinary HTTP, and the live channel is only a doorbell: on return the window reloads the room list and pulls the messages newer than the last one it holds. A lost frame loses no message, because the truth is the database, not the channel.
The author edits and deletes their own message, and an edited one carries a mark that it was changed. Someone else's is deleted, in a group, by whoever runs it. In a pair conversation nobody deletes it, the owner included: there is no moderation in a pair, and that is a decision rather than a gap.
Anyone on the team can found a group and becomes its admin, together with the people who run the school: name, members and deletion belong to them. Any member can add people and leave. The last one leaving deletes the room along with the messages, because nobody would be left to read them. One group holds two hundred people.
No, that is a separate module. Messages is post: a thread with a subject, the student and the whole team as recipients, a “you have mail” note to the inbox and a “Whole school” track for the owner. Chat is a team messenger: no subject, no student and not a single email. Whoever is not in the panel sees the badge on their next visit.
See Cerium from the inside.
14 days on your groups and instalments. No card, no strings.