Maintain the core school people records.
- School record
- Student, teaching staff or guardian record
- Connected relationship
- The person's school context
- Where it is used
- Administrator people workflows
Student information system for schools
Keep school people and relationships organised.
Authorised administrators can manage core student, teaching staff, guardian, class and section records in one school context. They can link a guardian to one or more students and use those relationships in the Schylva workflows that support them.
Login accounts are separate: create and manage them through User Access Management.
Administrator People overviewOpen detail
Visible evidencePeople overview and supported record categories
Shows the administrator People context and supported record categories with fictional counts—not admissions, workforce or document-management scope.
Privacy-safe focused crop · surrounding controls intentionally excluded- People recordsStudents, teaching staff and guardians
- School relationshipsClasses, sections and guardian links
- Relevant role accessSeparate account and status controls
A relationship-led foundation
Connect each person with the right school context.
A people record becomes useful when its class, section, guardian or role context is clear.
- People record
Prepare the core person record.
An authorised administrator maintains the core student, teaching staff or guardian information.
- School relationship
Make the school relationship clear.
Connect the student to a class and section, and connect each guardian to the appropriate student or students.
- Workflow use
Use the relationship where it is supported.
Schylva workflows can use the relationship they support; login access remains separate.
People relationship map
See how one record connects across school work.
Follow each record from the relationship the school maintains to the workflow that uses it.
Student information relationship stages
Choose a stage to review the record, its connection and where it is used.5 stages · Swipe or scroll to explore
Place the student in the relevant class and section context.
- School record
- Student and class-section records
- Connected relationship
- Student placement in the relevant class and section
- Where it is used
- Relevant class-context workflows
Connect each guardian to the appropriate student or students.
- School record
- Guardian and student records
- Connected relationship
- One guardian linked to one or more students
- Where it is used
- Linked-child Parent context
Handle account creation and status separately.
- School record
- Maintained school person record
- Connected relationship
- Relevant school role and relationship context
- Where it is used
- Separate account and status controls
Use the relationship where Schylva supports it.
- School record
- Relevant student, class or guardian record
- Connected relationship
- Maintained class-section or guardian-student link
- Where it is used
- The workflow that needs that context
Role-specific responsibility
Give each role the relationship context it needs.
Administrators maintain records and relationships. Teachers, Parents and Students see only the supported context available to their role.
Maintain people and their school relationships.
Authorised administrators manage core student, teaching staff, guardian, class and section records and guardian links.
Explore Schylva for school administratorsWork from the relevant assigned context.
Teachers use the class and student context available to their responsibilities; workforce and HR administration are outside this page's scope.
Explore Schylva for teachersUse the active linked-child context.
Parents use the active student context linked to their account, including families with more than one linked child.
Explore Schylva for parentsUse the relevant personal school context.
Students use information available to their own school-role context; they do not receive administrator people controls.
Explore Schylva for studentsFictional product evidence
Inspect valid loaded states without production identities.
These focused interfaces use wholly fictional school data and demonstrate only the visible people overview, populated class roster and read-only linked-student relationship state.
Populated class and section rosterOpen detail
Visible evidenceClass, section and populated roster context
Current product interface · fictional school dataPopulated class and section roster
Review a valid populated class context.
Shows one fictional class and section with its assigned teaching and student context—not transfer, promotion or enrolment history.
Privacy-safe focused crop · surrounding controls intentionally excludedLinked-student relationship panelOpen detail
Visible evidenceRead-only linked-student relationship state
Current product interface · fictional school dataLinked-student relationship panel
Review a visible multiple-child relationship state.
Shows two fictional students connected to a Parent login in the same school context—not automatic family matching or account activation.
Privacy-safe focused crop · surrounding controls intentionally excludedScope & evaluation
Keep people records distinct from adjacent systems.
Review what is available today, what your school must decide and what remains outside scope.
Supported today
- Authorised administrators manage core student, teaching staff, guardian, class and section records
- A guardian can be linked to one or more students in the same school
- Class and section relationships provide context to relevant Schylva workflows
- Parent views use the active linked-child context available to the account
- Available administrator permissions apply to supported people-management actions
Confirm for your school
- Who owns each people and relationship record
- Class, section and teaching-assignment conventions
- How guardian-student links are reviewed before use
- Which existing records are covered by the written migration scope
- The separate account creation, activation and status process
Current boundaries
- No admissions CRM or transfer, withdrawal, promotion or enrolment-history automation
- No teaching-staff HR, payroll, leave or workforce management
- No document management, alumni management or complete multi-campus administration
- No automatic relationship matching or universal real-time propagation across every module
- No bulk import, export or third-party integration outside the written implementation scope
- No SSO, SCIM or arbitrary custom RBAC; login access is handled separately
Prepare your evaluation
Bring one representative example.
Use fictional or redacted information to trace the record, its school relationship, the owner and the workflow that needs it.
Which core record should the school maintain?
Choose a fictional student, teaching staff member or guardian to keep the demo specific.
Which class or family relationship must be explicit?
Map the relevant class-section placement or guardian-student link.
Who owns review and correction?
Separate administrator record maintenance from Teacher, Parent and Student use.
Which adjacent workflow needs the context?
Confirm the intended use without assuming automatic propagation or account activation.
Student information questions
Questions to settle before your demo.
Confirm the record, school relationship, access responsibility and current boundary.
Which people records can authorised administrators manage?
Schylva supports core student, teaching staff and guardian records with class and section context. This is not complete admissions, HR or document management.
Can one guardian be connected with more than one student?
Yes. An authorised administrator can link one guardian with one or more students in the same school. Parent views use the active linked-child context available to the account.
How do classes and sections relate to student records?
The class and section relationship supplies context to relevant workflows. This page does not claim automated transfer, promotion or enrolment history.
Does creating a person record activate a login account?
No. Account creation, role, status and available administrator permissions are handled separately through the supported User Access Management workflow.
Can Schylva migrate existing student information?
Data migration is an included implementation service only where it is recorded in the written scope. The source records, ownership and validation approach must be confirmed for the school.
Does this replace admissions, HR, payroll or document systems?
No. Admissions CRM, workforce HR, payroll, leave, document management, alumni management and complete multi-campus administration are not current claims.
Relationship-focused next step
See your people workflow in Schylva.
Bring one representative student, class or guardian example. We will map the record, relationship, separate access responsibility and relevant workflow.
Use fictional or redacted information only—no real student names, contact details, files or screenshots. Share an approximate student count and priorities. We respond within two working days.