Student information system for schools

Student information system for school records and family relationships

Schylva’s student information system helps authorised school administrators organise student, teaching staff and guardian records, classes and sections. Link guardians to the right students and use those relationships in supported school workflows.

Book a student information demo Explore the relationships

A useful record has context

The person.
The relationship.
The school day.

A people record becomes useful when its class, section, guardian or role context is clear.

People record: An authorised administrator maintains the core student, teaching staff or guardian information.
School relationship: Connect the student to a class and section, and connect each guardian to the appropriate student or students.
Workflow use: Schylva workflows can use the relationship they support; login access remains separate.

The relationship ledger

Not just who.
How they belong.

Follow each record from the relationship the school maintains to the workflow that uses it. Each entry separates the record, its relationship and the supported use. Expand an entry for responsibility and limits.

Authorised administrator

Prepare people records

School record: Student, teaching staff or guardian record
Connected relationship: The person's school context
Where it is used: Administrator people workflows

Responsibility and limits: prepare people records

Maintain the core school people records.

An authorised administrator enters the supported student, teaching staff or guardian details in the correct school.

The record is ready for a school relationship. Admissions, HR and document management remain outside this page's scope.

Class organisation

Place class and section

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

Responsibility and limits: place class and section

Place the student in the relevant class and section context.

Assign the student to the class and section used by the relevant school workflows, then review that roster.

The class context is clear without implying transfer, promotion or enrolment-history automation.

Family relationship

Link guardians

School record: Guardian and student records
Connected relationship: One guardian linked to one or more students
Where it is used: Linked-child Parent context

Responsibility and limits: link guardians

Connect each guardian to the appropriate student or students.

An authorised administrator can link one guardian with one or more students in the same school.

Parent views can use only the active linked-child context available to that account.

Separate access responsibility

Prepare role access

School record: Maintained school person record
Connected relationship: Relevant school role and relationship context
Where it is used: Separate account and status controls

Responsibility and limits: prepare role access

Handle account creation and status separately.

Manage the school-role account, status and available administrator permissions in User Access Management.

A people relationship supplies context; it does not by itself create, activate or secure a login account.

Understand the separate account responsibility

Supported school workflows

Reuse connected context

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

Responsibility and limits: reuse connected context

Use the relationship where Schylva supports it.

Class, student and linked-child context can inform the relevant Schylva workflow. This page does not promise universal or real-time propagation.

Follow-up begins from a maintained school relationship rather than an assumption about the person.

A relationship guide, not a live record editor or an automated setup sequence. Relationships are maintained explicitly; no universal real-time propagation is implied.

An important distinction

A person record
is not a login.

A people relationship supplies school context. It does not by itself create, activate or secure an account.

Explore User Access Management

Student information

Maintain the relationship.

Core people records, class-section placement and explicit guardian-student links.

User Access Management

Manage the account separately.

Account creation, role, status and available administrator permissions belong to the supported access workflow.

Ownership and relevant views

One school context.
Different responsibilities.

Administrators maintain records and relationships. Teachers, Parents and Students see only the supported context available to their role.

Maintains the foundation

School administrators

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 administrators

Teachers

Work 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 teachers

Parents

Use 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 parents

Students

Use 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 students

Real interface · fictional people

Inspect the records.
Keep real identities out.

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. The populated roster is shown in the hero.

Administrator · People overview

Start with the core categories.

Current product interface · fictional school data

Shows the administrator People context and supported record categories with fictional counts—not admissions, workforce or document-management scope.

One guardian · More than one child

The linked students,
in one school context.

Focused Schylva Linked Students list using fictional data and showing two students connected to a Parent login — Read-only linked-student relationship · static product screenshotEnlarge screenshot: Read-only linked-student relationship

Current product interface · fictional school data

Shows two fictional students connected to a Parent login in the same school context—not automatic family matching or account activation.

Useful foundations, clear limits

People management.
Not every people system.

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

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

Bring a representative example

Start with one record.
Agree who owns it.

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.

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

Questions before your demo

Records, relationships
and access.

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.

Your school, clearly connected

See where
each record belongs.

Bring one representative student, class or guardian example. We will map the record, relationship, separate access responsibility and relevant workflow.

One fictional student, teaching staff or guardian record
Its class-section or guardian-student relationship
The school role responsible for review
One supported workflow that needs the context

Book a student information demo Get a custom quote

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.