Home / School networks and governing bodies
Central managementSeveral schools on one base, each with its own separation
A governing body or a central management follows all its schools in the same Odoo instance, without mixing their accounts: each school keeps its own balances, its own settings and its own canteen.
Each school remains sealed off from the others
A school's bursar sees only their own school
A bursar accesses the wallets, bookings and invoices of their own school. No data from another school in the network appears in their workspace or in their exports.
Central management views the whole network
A central management account sees the schools side by side, school by school, without having to log in to several databases.
The network connects Mensavo to its existing tools
Synchronisation with the Enseignement pupil database
Pupils, classes and school years are synchronised with the Enseignement pupil database, by API or by file depending on the tool the network already uses, to avoid entering enrolments twice.
Export to the governing body's accounting
The movements of each school are exported with their accounting codes, by individual account or grouped, to join the accounting software already used by the governing body.
Taking over the data from the current operator
Balances, cards and histories from the tool currently used by the network are taken over at go-live, school by school.
Hosting, GDPR and subcontracting: documentation to be provided for a public tender
A governing body subject to public procurement will receive the expected documentation: hosting location, role of processor within the meaning of the GDPR, record of processing activities and conditions for returning the data at the end of the contract.
Request a Mensavo demo
About thirty minutes to see the wallet, the canteen, the invoicing and the families portal on the cases you choose.
Request a demo