Auth, RBAC, sessions, and audit export
Secure sign-in, role-based access on every route, session management, activity audit export, and clear data-handling boundaries for school evaluators. Schools trust SMS vendors with student records. Schoolyi documents authentication, capability paths, session policy, and activity logging so IT teams and leadership evaluate security before rollout, not after an incident.
Outcomes
Practical results schools report after rolling out security & data inside platform & access.
Sensitive modules stay gated to authorised roles
Leadership exports activity when investigating changes
IT teams review RBAC before go-live
Parent magic links reduce password support load
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.
Schools trust SMS vendors with student records. Schoolyi documents authentication, capability paths, session policy, and activity logging so IT teams and leadership evaluate security before rollout, not after an incident.
Secure sign-in, role-based access on every route, session management, activity audit export, and clear data-handling boundaries for school evaluators. Because security & data lives inside platform & access on Schoolyi, teams stop reconciling exports between spreadsheets and the parent portal.
Evidence layer
Read the supporting product and implementation material before making a capability claim.
Everything included in this capability, from daily workflows to exports your team relies on.
Role-scoped workspaces so each team sees only the tasks they own.
Full module
Platform & access
Every user gets the right access from day one. Schoolyi gives administrators fine-grained control over who can view and change student records, fees, exams, and settings, so each role sees a workspace built for their job.
Explore Platform & accessWorkflow
A typical path from setup through daily use on Schoolyi.
Part of the Security & data workflow on Schoolyi, connected to roster, calendar, and role permissions.
Part of the Security & data workflow on Schoolyi, connected to roster, calendar, and role permissions.
Part of the Security & data workflow on Schoolyi, connected to roster, calendar, and role permissions.
Part of the Security & data workflow on Schoolyi, connected to roster, calendar, and role permissions.
Deep dive
Long-form context for evaluators comparing capabilities during an SMS rollout.
Schools trust SMS vendors with student records. Schoolyi documents authentication, capability paths, session policy, and activity logging so IT teams and leadership evaluate security before rollout, not after an incident.
Secure sign-in, role-based access on every route, session management, activity audit export, and clear data-handling boundaries for school evaluators. Because security & data lives inside platform & access on Schoolyi, teams stop reconciling exports between spreadsheets and the parent portal.
Straightforward answers for visitors evaluating the product.
Role-based access gates pages and API routes, keeping sensitive modules available only to authorised staff and administrators.
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.
The activity log supports operational review and CSV export when leadership or IT investigates access and configuration changes.
Test the answer with a representative record and role before making it part of a live term workflow. Capture the expected result and the exception path so the team can verify it after launch.
Schoolyi provides password policy, email verification, session management, sign-out controls, and magic-link onboarding for parents.
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.
The security overview documents authentication, capability paths, session policy, activity logging, and PWA/offline asset boundaries for evaluation.
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.
We'll show how security & data fits your school's platform & access workflows and which teams benefit first.
Already using Schoolyi? Sign in
