Go-live gate
A successful sign-in does not prove a rollout is safe; test least-privilege access, publishing, email, backups, and recovery.
For platform admins
School platform administration and IT
Control accounts, roles, school settings, integrations, sessions, audit exports, and rollout readiness from one administration layer. See the workflow, ownership, rollout sequence, and boundaries before choosing a school management platform.
Dashboards, approvals, and cross-department visibility.
Product screenshots
The Schoolyi screen for this work
Captured from a demo school, at a size search engines can fetch. Open the module for the rest of the workflow.
At a glance
A useful page should answer the next operational question
Control accounts, roles, school settings, integrations, sessions, audit exports, and rollout readiness from one administration layer.
Who this is for
- IT coordinators
- Platform admins
- School leadership
Start with the evidence
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
Follow the handoffs, not just the feature list
A clear sequence makes ownership, exceptions, and the next system action visible.
- 01
Model access
Map school responsibilities to role permissions before inviting staff.
- 02
Configure
Set school identity, academic structure, notifications, grading, and operational defaults.
- 03
Test
Use representative staff and family accounts to verify route visibility and handoffs.
- 04
Govern
Review activity, deactivate leavers, export evidence, and maintain deployment runbooks.
Product truth
What to verify before rollout
Good school software copy should answer who owns the work, what the handoff produces, and which parts still depend on deployment decisions.
Validate for your rollout
Capability status
This page describes the supported workflow boundary. Confirm configuration, integrations, data, and policy requirements in a representative pilot before committing to production.
Teams in the workflow
- IT coordinators
- Platform admins
- School leadership
Deep dive
Decisions, handoffs, and boundaries
Use these details to turn a product page into an implementation conversation.
AI boundary
AI help and integrations should be enabled with clear role, data, and infrastructure decisions.
Deployment checklist
Record the server owner, scheduled jobs, email and payment settings, backup arrangement, recovery owner, and role-review date before declaring administration ready.
Evidence layer
Read the supporting product and implementation material before making a capability claim.
Questions, answered
Straightforward answers for visitors evaluating the product.
Can roles be customised?+
The platform uses role-based access; map local job titles to the available permission model during setup.
Record the responsible administrator and verify the control in the target deployment before production data is loaded. Keep the evidence with the school’s procurement or access-review record.
Is enterprise SSO included?+
No. Sign-in uses credentials and parent or student magic links; schools requiring SSO or MFA should treat those requirements as unmet.
Treat that boundary as an explicit procurement or deployment decision. Document the responsible owner and any supporting process before rollout.
Continue exploring
Related planning and product pages
Follow the next link based on the question your team needs to answer.
Schoolyi security architecture
Review authentication, role-based access, data boundaries, sessions, audit visibility, and operational controls before rollout.
Read the pageSchool data privacy and RBAC review
Review who can access student, family, finance, HR, and operational data before expanding the school platform.
Read the page
Turn the page into a rollout conversation
We can walk through the workflow with your school’s roles, calendar, data, and first-term priorities.
Already using Schoolyi? Sign in