Adoption depends on trust
Families need predictable labels, clear publication timing, mobile readability, and support for linking mistakes.
For parents and guardians
Give families one login for linked children, fees, receipts, attendance, grades, exams, transport, and school communication. See the workflow, ownership, rollout sequence, and boundaries before choosing a school management platform.

Dashboards, approvals, and cross-department visibility.
Product screenshots
Captured from a demo school, at a size search engines can fetch. Open the module for the rest of the workflow.
At a glance
Give families one login for linked children, fees, receipts, attendance, grades, exams, transport, and school communication.
Use the linked product and documentation pages to validate the workflow against your school’s data, roles, policies, and deployment.
Read the supporting materialHow it works
A clear sequence makes ownership, exceptions, and the next system action visible.
Receive an invite and confirm the guardian-to-student relationship.
Switch between children and see only the records linked to the family account.
Pay fees, download receipts, respond to notices, and follow attendance or exam updates.
Use the portal as the durable record instead of searching through message threads.
Product truth
Good school software copy should answer who owns the work, what the handoff produces, and which parts still depend on deployment decisions.
This page describes the supported workflow boundary. Confirm configuration, integrations, data, and policy requirements in a representative pilot before committing to production.
Deep dive
Use these details to turn a product page into an implementation conversation.
Families need predictable labels, clear publication timing, mobile readability, and support for linking mistakes.
A parent login should expose linked children only; split custody and guardian changes need a school-owned process.
A receipt download or published attendance view gives families a reason to return. Add grades, exams, transport, and notices only after links and publication timing are reliable.
Evidence layer
Read the supporting product and implementation material before making a capability claim.
Straightforward answers for visitors evaluating the product.
Yes. The parent dashboard is designed for multi-child families.
Test the guardian link and publication boundary with a sample family before inviting the wider parent community. Confirm that each linked child exposes only the records the school intends.
No. Grades and report cards should become visible only after the school publishes them.
Treat that boundary as an explicit procurement or deployment decision. Document the responsible owner and any supporting process before rollout.
Parents and students use password sign-in, with a fifteen-minute magic link available. Single sign-on and multi-factor authentication are not available.
Treat that boundary as an explicit procurement or deployment decision. Document the responsible owner and any supporting process before rollout.
Continue exploring
Follow the next link based on the question your team needs to answer.
Fees to receipt
Configure fee structures, generate installments, collect online or counter payments, and give families a receipt that finance can reconcile.
Read the pageParent portal adoption plan
Make the parent portal useful on day one with correct guardian links, clear publication rules, mobile-friendly help, and a support loop.
Read the page
We can walk through the workflow with your school’s roles, calendar, data, and first-term priorities.
Already using Schoolyi? Sign in