The card edits in place
Title, priority, due date, assignees, labels and steps are edited in place, with no drawer and no dialog. "Add card" starts typing straight away instead of opening a form.
All modules
Back office
Team tasks
A head teacher hands out a dozen small jobs a day: call a parent, book room 3, order toner. Without one place for them, half live in a chat app and half on a sticky note, and nobody knows whether anyone picked them up.
All Mine Add card
To do 2
In progress 1
Done 1
Zadzwoń do opiekuna Nowaka
Sprawdź listę podręczników
Rezerwacja sali na próbny
Zamów wodę do sekretariatu
auto one board for the whole school · who does what
Team tasks
What this module does
2
layouts of one board: cards and a table
4
urgency levels, from low to urgent
30
assignees fit on a single card
90 days
after that a done card leaves the limit
The school sets the stages
Columns come from the school's own catalog: name, tone and a system kind - to do, doing, done. Completion follows the column the card sits in, not a separate field.
You see the landing spot
The dragged card is its own ghost: it already sits in the target slot and travels there instead of jumping. Order within a column is stored data, so two hands on one card give one result.
Board or table
The same cards under one address: stage columns you drag across, or the shared table with sorting, search and columns you add yourself.
Anyone creates, you see yours
Anyone can create a card for anyone, but the owner sees the whole board while everyone else sees cards they are assigned to or created. Only staff can be assigned.
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 | The whole school board, in both layouts, with the “All / Mine” track. | Every card, plus the board columns in the “Board stages” drawer. |
| Methodologist | The same as the owner: every card in the school. | Every card and the stage catalogue - they run the school with the owner. |
| Teacher | Cards they are assigned to and cards they handed to someone else. | Those same cards; creates new ones for anyone. Columns stay untouched. |
| Student | Nothing. No module by default, and not a single card of their own here. | Nothing. Only school staff can be assigned. |
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
- a card archive - a done card stays on the board, and an unwanted one is deleted for good
- comments, attachments or a change history - past that line Projects begin
- mail on assignment - the assignee finds out by opening the board
- recurring cards or templates - every card is created from scratch
You, the assigned person and the management - the owner and the methodologist see the whole board, because they are the ones handing out work. Everyone else sees only cards they are assigned to or created themselves, and that narrowing is one function in the handler, not a setting on the screen. The cost is deliberate: handing over a task, you will not see the twelve other overdue cards that desk already has.
“Add card” opens no form; it starts typing in place. A title is enough, up to two hundred characters, and the card stands in the first column of the “to do” kind. Urgency, due date, assignees, tags and steps are edited on the same card, and a value is handed over when you leave the field, like a table cell. No drawer and no dialog along the way.
One order comes out, not two. A card's position in a column is data rather than a sorting result, and a move recalculates the target column under a row lock - the same route as a cash document number. You can see it before letting go: the dragged card is its own ghost, already standing where it will land, and the ride takes 160 ms.
From the school catalogue, not from the code. A column has a name, one of eight tones and a system kind: to do, doing, done. The kind is how the system recognises completion - the database sets and clears the moment of completion when a card enters a “done” column, rather than a separate field on the card. A school with no catalogue gets three columns to start with, and one save accepts at most twenty.
No. The limit counts the load, not the history: unfinished cards plus those finished within the last ninety days. An older card stays on the board and in the table but stops taking up room. That is five hundred cards on the Pro plan and one thousand five hundred on the Szkoła plan. The counter is also checked after a stage change, because pulling an old card out of “done” raises it.
No, and this is not a filter on a list. An assignee is a key into the school staff, so neither a student nor a guardian gets onto a card by any route - including straight through the API, where a foreign key is refused with a message instead of being saved in silence. One card holds thirty people and fifty steps; both numbers are constants in the code, not limits to be bought.
The name. An assignee is a key plus a snapshot of the name: the key answers “who has to do this today”, the snapshot “who had it”. When a person leaves, the key goes and the text stays, so the card still says whose it was. The “Who is on it” cell in the table draws only people with an active membership - the full list is on the card.
No. A card is one duty: “call the guardian”, “order toner”. An undertaking with phases, a team, comments and attachments is Projects; lesson times are the Schedule, purchases are Orders, and a conversation with a prospect is the CRM. There is not even room for a paragraph here - the description is a table column only, because a task that needs a paragraph is a project.
See Cerium from the inside.
14 days on your groups and instalments. No card, no strings.