Skip to main content

​
Layers and components

Marketplace, Business, School and Learning are four commercial layers using existing applications, not four technical platforms. Marketplace and the SaaS portal use shared identity, permissions, CountryConfig, verification, payments, communications and audit services. OPS administers those services within its authorised scope.

​
One OHADA school, one installation

Ardoise School uses a Django installation for each school, with a dedicated PostgreSQL database in production. Pupil records, grades, private learning evidence, finance and payroll are processed in this school data plane. Staff browsers contact the school’s server; this cross-origin connection is an intended part of the architecture. See installation and backups.

​
What the platform manages

The shared platform manages identities, public profiles, consenting affiliations, enquiries, authorised CRM contacts, Marketplace contracts, lessons and necessary payment/acquisition metadata. It also supports activation and authorised exchanges with the school installation. It is not a general replica of private school records. Configured integrations have specific flows: admission requests and tracking, identity linking, notifications, backups to a selected Drive, video services or eligible payments. Avoid saying “no data ever leaves the school”. Check what is sent and to whom before enabling an integration. Remote R1/R2 inference is limited to non-personal resource metadata; private evidence stays local: Learning.

​
Institutes and countries

An institute remains in Marketplace/Business and has no access to schools’ Django data. Operators observe only authorised organisation contracts; they do not decide for parents/tutors or receive their private messages. See Business. Ardoise School, school payroll and accounting are not an Austrian offering. Technical compatibility does not alter that commercial boundary. CountryConfig is configuration, not legal certification; rules and providers must be checked per country.

​
Access and retention

APIs and MCP enforce scopes, countries and consent; they do not grant general access to grades, payroll or pupil records. Account deletion removes access and the profile according to the journey. Necessary school and financial history can remain for record integrity.