Use SkoleElev on top of Aula
Parents stay in Aula. Teachers and pedagogues work in SkoleElev. Every message, announcement and after-school event mirrors automatically — with per-school control and a resilient queue.
Five pillars of the integration
Each pillar has its own toggle — municipality and school choose the pace.
- PILLAR 1
Two-way message mirror
Teachers write in SkoleElev — the message lands in the Aula thread too. Parent replies flow back as beta.
Read more - PILLAR 2
Calendar & announcements
Arrangements and announcements from SkoleElev publish directly into Aula — with attachments, attendees and consent.
Read more - PILLAR 3
After-school check-in/out
Check-in/out events mirror to Aula's institution API — parents see it where they already look.
Read more - PILLAR 4
Inbound replies (beta)
When parents reply in Aula we poll every 2 minutes and land it in the original SkoleElev thread.
Read more - PILLAR 5
Per-school opt-in
The municipality rolls out one school at a time. Each school admin controls which surfaces are mirrored.
Read more
How a school gets on
Discovery
Enter the institution code — we validate against KOMBIT.
Roster sync
Profiles link to UNI-Login via unilogin_id.
Mock-mode test
Mirrors run dry, no real Aula calls.
Go live
mTLS certificates land, the school flips its toggle.
Why it's real integration — not a wrapper
- No migration — Aula stays the parents' familiar channel
- Resilient queue — Aula downtime never blocks a SkoleElev message
- Idempotent delivery — retries never duplicate a message
- Echo guard — messages pulled from Aula are never mirrored back
- UNI-Login mapping — profiles link via unilogin_id, not name-match
- Audit log — every mirror action is traceable per school and surface
FAQ
Ready to connect your school?
We set up mock-mode in 15 minutes so you can test the mirror before mTLS certificates land.
Request a pilot