Two tabs, one screen
"Workspace" holds the school's choices, "Account" holds the signed-in person's name, address and password. Account is always there, because a password belongs to a person, not to a school.
All modules
Back office
Settings
A school makes decisions that are not a row on any list: whether a teacher sees their own contract, how contracts are numbered. This screen is where those are made, and where each person edits their own details.
SchoolJournalContractsPayments
Rooms
What this school teaches in. Groups, Journal and Schedule pick from this catalogue.
Sala 1Sala 2Sala 3PracowniaŚwietlicaAula Save rooms 6/40
School logo
One file for the whole school. The public sign-up form and surveys use it.
C 512 KB · 2048 px
auto space settings · a section is a row
Settings
What this module does
4
space settings tabs, kept in the address
10
sections, each with its own condition
512 KB
and 2048 px: two caps on the school logo
5
rows on Account, from name to password
A setting is a row
Name and description on the left, controls on the right, a hairline between rows. The left column reads like a table of contents instead of a hunt for the right switch.
Saved as you change it
A switch is stored the moment you flip it, with no "Save" button: these are single decisions, not a form to fill in and submit.
Settings belong to modules
Every card goes through the route of the module that introduced it and appears only to someone who has that module. Without it the screen never asks for the data.
Cards for the owner
Next to the school's choices sit the subscription and the agreement with Cerium: whether it is accepted, when and by whom, with a copy of the accepted text to download.
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 tab and every section they hold the module for. | Every space setting, both building catalogues and their own Account. |
| Methodologist | Nothing until the school grants this module - it is not given by default. | Once granted, only the building catalogues: places and rooms. The rest stays with the owner. |
| Teacher | No such screen. The grading scale and the mail switch are the school's call. | Their own Account: name, language, theme, address and password. |
| Student | The same: no space screen, but an Account like everyone else. | Their own Account and nothing beyond 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
- tables of its own beyond the school contract party - the rest sits in its modules' columns
- the space name, address or time zone - those are kept by the Cerium operator
- a change history - who flipped which switch, and when, is recorded nowhere today
- a limit of its own - settings are single decisions, and only what multiplies is capped
Right here, in two school catalogues: “Places” (branch, building, floor, cupboard) and “Rooms”. Orders and Rentals read the first one, Groups, the Journal and the Schedule the second. Both are saved as a whole set, and an entry pulled off a list that something already hangs on is archived rather than deleted - the API decides that, not the screen.
No. A methodologist runs the school alongside the owner, but whatever belongs to the school as a company - settings, module grants, the platform agreement and the subscription - stays with the owner, because whoever hands out screens could hand themselves Settings. They do not even get the module by default. Once granted, they see and save the building catalogues only.
From one file uploaded here. The public pages - the sign-up form and surveys - take it wherever no image address of their own was entered, and the space card in the rail draws it instead of the initial square. There are two caps, because weight says nothing about pixels: 512 KB and 2048 px on an edge. A new file deletes the old one, so a school holds exactly one logo.
A switch saves on change, because it is a single decision rather than a form. Only four things go by button, and only because they are whole sets: the grading scale with its categories, the places catalogue, the rooms catalogue and the eleven fields describing the school on a student contract. There, half a saved set would mean a catalogue nobody intended.
Both on Account, under the cog next to your name - but they belong to different owners. The language is a field of the account: it follows the person onto every device and the mail they receive is written in it. The theme belongs to the device, so a phone may differ from a desk, and it can switch itself at sunset or at a chosen hour.
No. Those are space data, and the Cerium operator keeps them on the client screen, together with the limits. The line is simple: the school decides how it works, the operator how much it may have. The only name typed in here is the legal name for a student contract, and leaving it empty means “use the space name”, so nobody enters it twice.
Because this module owns no setting at all - it owns a screen. Every section belongs to the module that introduced it and travels that module's route, so one row grows here per module that has something to decide. A tab exists when a person has at least one section in it, and with a single tab there is no track at all. Under the last section stands a sentence saying the rest arrives with the modules it concerns.
No. How much room a school has is shown by the separate Limits screen, and there too it is read only; raising them is the Cerium operator's job. All that shows up here is the counter next to the button in the building catalogues - how many places and rooms out of how many - so nobody saves a set that would break the limit anyway.
See Cerium from the inside.
14 days on your groups and instalments. No card, no strings.