We set up the space
Another school is set up by the platform operator, on request from Support, on the same owner account: a trial account from the form is a standalone school.
Support Who it is for: School network
Cerium for school networks
Several branches in one school, or several schools in one network. Shared staff, a timetable you can narrow to one branch, and money, contracts and payroll where they belong.
A new branch, from the first room to a closed month
The simplest network setup is one Cerium space with several addresses: one staff, one student register and one timetable. Each step is a module.
- Settings
The branch and its rooms
In Settings you add the branch to the “Branches and places” catalogue, and every room points to the branch it is in.
- Team
Staff across addresses
A teacher who works at two branches is one person on the staff, with one contract and one monthly payroll.
- Students
Front desk on site
The front desk at each branch adds students and guardians to the same register, without access to staff pay.
- Groups
Groups in rooms
A group gets a room from the catalogue, so it is clear which branch it meets at, and it can have several teachers.
- Schedule
Timetable by branch
The “Rooms” view in the Schedule groups lanes by branch, and a filter leaves just one on screen.
- Rentals
Things in stock
Rentals and Orders take the place from the same catalogue, so you know where the coursebooks are and where a purchase is going.
- Finance
Money
Instalment plans, payments and the cash desk in one Finance module, with a payment link and invoices sent to KSeF through your accounting software.
- Observations
Lesson observations
Management observes lessons at every branch with the same set of criteria and shares the sheet with the teacher when it is ready.
- Settlements
A closed month
Payroll counts lessons taught at every branch and closes the month for the whole staff with one button.
A day in network management
Management travels between addresses. The state of the day at both branches fits on one phone screen.
DashboardToday, Thursday
- 16:00 Group B1 Mokotów, room 3 now
- 17:00 Group A2 Ursynów, room 1
- 18:00 Kasia, 1:1 online
Both branches, today 9/10 present
- Lessons
- 4 of 7 taught
- Paid today
- PLN 1,240
- Overdue instalments
- 3
- Open items
- 2 due today
-
You open the Dashboard
The NOW panel shows lessons running at both branches, with open items from the enquiry funnel, Rentals, Finance and Projects below it.
-
Rooms by branch
In the Schedule the “Rooms” view groups lanes by branch, and a filter leaves just one.
-
Limits and usage
How many students and teachers the school has and how much space files take, against the plan and with a history of overruns.
-
Monthly payroll
One button closes the month for the whole staff, counted from lessons taught.
-
Staff and observations
Teaching assignments, contracts and lesson observation sheets the teacher sees only once they are shared.
-
Support from the panel
A ticket to us straight from the panel, with a screenshot.
The panel works in the phone’s browser and is designed from a 390 px width up. An App Store and Google Play app with push notifications is in preparation.
What is here for networks
Seven things that start to matter once a school has more than one address.
Branch catalogue
Branches and places are one school catalogue used by rooms, Rentals and Orders.
Module: SettingsA timetable narrowed to one branch
Each room points to its branch, so the Schedule groups lanes by it and shows one on request.
Module: ScheduleOne account across schools
Teachers and management sign in once, and have a separate membership with its own role in each school of the network.
Module: TeamLesson observations
The school’s own criteria on a 1 to 5 scale, and a sheet the teacher sees only once it is shared.
Module: ObservationsFiles for every address
Folders shared with the whole school or with chosen people, so policies and templates live in one place.
Module: DocHubProjects
An open day or a new term as a project with phases, tasks and a team drawn from several branches.
Module: ProjectsLimits and usage
Students, teachers and file storage against the plan, with a history of overruns.
Module: LimitsA second school in the network
When a location needs its own team, its own money and its own timetable, it gets a separate workspace on the same account. The schools do not see each other's data, and one of them can pay the subscription for all.
Demo or agreement
A new school starts as a demo with an end date, or straight away with an agreement the owner accepts in the panel.
Data from CSV
You load students, guardians and groups from CSV files exported from your current system.
StudentsThe same staff
Someone who works at two schools signs in with the same account and has a separate membership, contract and payroll in each.
TeamIts own money
Each school has its own Finance, its own Stripe account for payments, its own invoices and its own subscription.
FinanceA shared dashboard with the numbers of all schools does not exist today. Every school sits in the workspace switcher under the same account, and one of them can pay the subscription for all.
Who sees what
One school, four points of view. The server enforces the boundary on every save, not a hidden button in the menu.
| Role | Sees | Changes |
|---|---|---|
| Network management | Its schools in Limits and Subscription, and in each school where it has a membership, whatever its role shows. | Whatever its role allows in a given school. Writing never crosses from one school to another. |
| Branch director | Their whole school: finance, groups, staff, reports, limits and every message thread. | Payment plans, teaching assignments, contracts, price lists, staff payroll and school settings. |
| Teacher | Their own groups and lessons at every branch where they teach, and a covered group only around the cover. | Attendance, topic, grades, homework and materials, but only for their own lessons. |
| Front desk | The school’s registers: students, guardians, companies, groups and enquiries from the funnel. | Edits the registers and moves lessons like a teacher, without deleting and without staff contracts, price lists or payroll. |
What Cerium connects to, and what it does not
The “no” list is here on purpose: better to know before the demo than after the rollout.
Available
- Stripe: online payments and automatic card charges
- KSeF via Fakturownia, wFirma, iFirma or inFakt
- Email: messages to students, guardians and payers
- Built-in video lessons in Cerium, with the group whiteboard
- CSV: import and export of lists
- API key for the enquiry form on your website
Not available today
- Zoom, Google Meet, Microsoft Teams
- Google and Apple Calendar
Questions we hear most often
Short answers, no overpromising. What is missing is listed alongside.
What Cerium does not do here
- A shared dashboard with the numbers of all schools does not exist today: you open each school from the workspace switcher. A non-public primary school has a separate plan with the Classes module (pilot).
- No central network templates: each school keeps its own contract and certificate templates, price lists and catalogues.
- Writing does not cross between schools: a student, a payment and a contract belong to one space.
- This is not a register for public schools: Librus and Vulcan cover what the ministry requires.
The School plan includes three branches, and Enterprise has no limit. Addresses within one school, such as rooms, a storeroom or a front desk, go into the “Branches and places” catalogue in Settings.
It depends on the setup. In one space the timetable and staff are shared, and the Schedule narrows to one branch in the “Rooms” view. A branch set up as a separate school in the network has its own staff, students, timetable and money.
Not on one screen. Every school sits in the workspace switcher under the same account, so you open it in one click, and one school can pay the subscription for all of them. A shared dashboard with the numbers of all schools does not exist today.
Yes. In one space it is simply the same person assigned to groups at both branches. Across schools in a network it is one account with a separate membership in each, and each school keeps its own contract and payroll.
Locations in one workspace share Finance and one subscription. Separate schools of one client can share one subscription: one school pays, and the students and teachers of the others count towards its subscription and overage. Student payments and their invoices stay with each school, on its own Stripe account.
You add an address in the same school yourself in Settings, and rooms point to their location. A separate school is set up by us, on request from Support: on the same owner account and, if you want, on the same invoice. Students, guardians and groups load from CSV.
See Cerium from the inside.
14 days on your groups and instalments. No card, no strings.