Start from a template
The new project dialog writes stages, tasks and roster in a single save, so the board opens with a dozen cards already on it. A finished project moves to the archive and frees its slot.
All modules
Back office
Projects
An open day, a stand at an education fair, getting a term ready: things that run for weeks and break into dozens of small jobs. A project holds the stages, the team, the dates and why it went the way it did.
Project Dzień otwarty 0%
Planning -
Materials -
Delivery -
Review -
auto school project · open day
Projects
What this module does
3
layouts of one dataset, layout in the URL
12
stages per project, a constant, not a limit
30
people on a project and on one task
300
tasks per project, finished ones included
Stages belong to the project
Stages live on the project, not in a school-wide catalog: "order the banner" belongs to Materials and stays there after it is ordered, because done is a checkmark, not a column.
Three layouts, one dataset
A stage board you drag cards across, a task table with your own columns, and a team board where dragging changes who is assigned. The layout sits in the address; your default is remembered.
Cards that carry the detail
The task drawer holds a full description, a checklist, links to a group, a lesson or a file, plus comments and system trail read as one timeline.
The roster gates access
Management sees every project in the school, everyone else sees the ones they are on. Only staff can be assigned: these are not student assignments.
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 project in the school, including those they are not a member of. | Settings, membership, stages, archiving and deletion - in any project. |
| Methodologist | The same as the owner: the whole school. Management hands out the work. | The same: settings and membership of any project, not only their own. |
| Teacher | Projects they are a MEMBER of. One they started themselves is always theirs. | Tasks in their projects. Settings and membership only where they are the founder. |
| Student | No access to this screen. | Nothing. Only staff can be assigned, and a foreign key enforces it. |
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
- work for students - only staff can be assigned, and a foreign key enforces it
- a timeline or a Schedule strip - that grid counts minutes of a day, not weeks
- uploading of its own - an attachment points at a DocHub file or at a link
- mail on assignment - the assignee finds out by opening the board
In the depth of a card. Team tasks are for the small matters of a day, so a card there has six fields and nothing more. Here a task has a paragraph of description, a checklist, pointers to a group, a lesson or a file, plus comments and a system trail read as one timeline. Three things that module deliberately lacks.
One dialog. You pick a template card - Open day, Term preparation, Year review, or “From scratch” - type a name and choose the members. A template carries four stages and about ten tasks spread across them, and it all goes in ONE write, so a board never appears without columns to put anything on.
No, and that is a decision. A stage says which part of the work a duty belongs to, while a tick on the card says it is finished - “order the banner” belongs to Materials and stays there after it is ordered. A “Done” column would give two answers to one question and the first contradiction between them. There are at most twelve stages, and they shape THIS project, not the school.
Membership is the access list: management sees every project in the school, everybody else sees the ones they are named in. There is no separate rule about authorship and none is needed, because whoever starts a project joins its membership automatically - otherwise they would lose their own project on the first refresh.
No. There are two levels: settings - the name, dates, membership, stages, archiving and deletion - belong to management or to the FOUNDER; tasks are created and edited by anyone on the team, because that is the part meant to be shared. Without the split, the first person added could throw everybody else out.
Because it answers a different question: not “where does this stand” but “who has it”. A column is a person, and dragging changes the ASSIGNEES: it removes the source column's person and adds the target one, so a task done by two people does not lose the second. Order there comes from the due date, and all three layouts read one store.
There is none, and we are not pretending it arrives tomorrow. The shared time grid in this system counts MINUTES OF A DAY, because it draws lessons, while a project runs for weeks - a different drawing, not different data. Dates are watched by the dashboard instead: it takes tasks overdue, due today and due this week, but only where the asker is assigned.
Neither. An attachment POINTS at a DocHub file or at a link, because a file already has its place and its visibility, and a third one would be a third to maintain. Only a member of staff can be assigned, and a foreign key enforces that rather than a filter - work set for students is E-learning and Exercises.
See Cerium from the inside.
14 days on your groups and instalments. No card, no strings.