School ERP access and login management
Follow the product paths your school can inspect: administrator-managed accounts, role-aware workspaces, configured login verification, selected audit visibility and controlled file routes.
Request a review without sharing student records, login credentials, OTPs, payment details or confidential documents.
Real product evidence
Start with current Schylva screens using sample school data. Expand each image, review the workflow and keep the stated limitation attached to the evidence.
The administrator workspace groups administrator, teacher, parent or guardian and student login records by role.
This screen demonstrates a product workflow; it is not evidence of infrastructure isolation or a breach-prevention guarantee.
Review user and access management
The account preparation screen shows the administrator context and permissions available in the current product workflow.
Available permissions do not imply arbitrary custom RBAC, unlimited role creation or enterprise identity administration.
Understand available permissions
The teacher workflow shows how study material can be prepared for the relevant school audience.
This screen does not prove encryption, a storage quota, unlimited storage or support for every file type.
Review homework and study materials
The parent experience shows study materials in the context of the relevant linked child.
This screen does not imply unrestricted or offline access, synchronisation of every resource or support for every file type.
Review the parent experienceAccess, authentication and permissions
Review how a school relationship, account, configured login-verification step, role workspace and relevant record connect. Then test the path with representative users before activation.
Configured school
Each school works in its configured Schylva environment, which provides the context for its accounts and workflows.
School account
Administrators can create and maintain administrator, teacher, parent and student accounts and work with their account status.
Role-aware workspace
Administrators, teachers, parents and students receive focused experiences shaped by their role and the available permissions.
Relevant record
The role experience connects the user to the records and workflows relevant to that school relationship.
Configured school
Each school works in its configured Schylva environment, which provides the context for its accounts and workflows.
School account
Administrators can create and maintain administrator, teacher, parent and student accounts and work with their account status.
Role-aware workspace
Administrators, teachers, parents and students receive focused experiences shaped by their role and the available permissions.
Relevant record
The role experience connects the user to the records and workflows relevant to that school relationship.
Prepare administrator, teacher, parent and student records, including the relevant class, guardian and child relationships.
Administrators can create and maintain role accounts within the configured school environment.
The administrator can work with account status and the permissions currently available in Schylva.
The current verified web flow accepts a configured six-digit code. It does not generate or send that code by SMS.
The account reaches its role-aware experience and the records relevant to that school relationship.
Review school configuration, people, accounts, operations, records and authorised summaries.
Work with the relevant schedule, classes, attendance, homework, materials, circulars, remarks and exam context.
Review information for children linked to the parent account, including acknowledgement and payment paths where configured.
Review the student’s school-day information without administrator or parent-account complexity.
Operational evidence
Use representative actions and files to evaluate what can be reviewed today. Record any additional coverage, retention or file requirements for follow-up.
Selected school and platform actions can be recorded for audit and review. Coverage and retention depend on the release and school agreement.
Schylva does not publicly claim that every action is recorded, immutable or retained forever.
Ask in the demo: Which actions matter to our approval, and who needs to review them?
Review user and access managementStudy materials and other supported files use controlled product routes. Demonstrate the teacher-to-recipient path with a representative file.
Schylva does not publicly claim every file type, unlimited storage, end-to-end encryption or unrestricted offline access.
Ask in the demo: Can we follow one representative file from publication to the intended recipient?
Review homework and study materialsSecurity review and disclosure register
See what can be inspected in the product, what belongs in the school agreement and what still needs an approved answer.
These labels describe the current source of the answer—not a certification or guarantee.
Open a topic for the exact public boundary.
Each school works in its configured Schylva environment. Administrators, teachers, parents and students receive focused experiences, while account status and available administrator permissions help shape access.
The current verified web flow accepts a configured six-digit code. Product-managed SMS delivery is not currently available.
Selected school and platform actions can be recorded for review, while files use controlled product routes such as the available paths for study materials.
Open a topic for the exact public boundary.
Applicable data-export, product-data retention and deletion terms are addressed in the school’s agreement.
Open a topic for the exact public boundary.
A product-data hosting country or region and encryption scope in transit or at rest are not currently published. Product-data location cannot be inferred from the marketing website’s hosting.
Backup frequency, retention, restore testing, recovery targets, uptime percentages and service-level guarantees are not currently published.
A public incident-response process, reporting contact or notification commitment is not currently published.
No security certification, certification logo or blanket Digital Personal Data Protection Act compliance claim is made on this website.
Use these six questions to test the product and record every requirement that still needs an approved answer.
Use representative, privacy-safe school data to follow these paths.
Record the terms and unanswered requirements that need written confirmation.
Copies all six questions. Nothing is submitted or stored.
How open questions are resolved
The Remonthub product team reviews requirements that are not answered by the product evidence or school agreement.
Use the security-review request to describe the decision your school needs to make.
The product team separates demonstrable behaviour, agreement terms and technical details that are not yet published.
The school receives the available answer, the evidence to inspect or the confirmation needed before approval.
School security FAQs
Review the current product scope and note what your school still needs to confirm.
No. Each school works in its configured Schylva environment, and administrators, teachers, parents and students receive role-appropriate experiences. Test representative users against the records and workflows your school needs.
The current verified web flow accepts a configured six-digit code before the account enters its school and role experience. Schylva does not currently generate or send that code by SMS.
No. WhatsApp and non-login SMS are not product channels. Login verification SMS delivery is not currently available; school updates use Schylva’s in-app and push notification experience at launch.
Schylva does not currently claim SSO, SCIM, arbitrary custom roles, MFA or product-managed verification delivery. Administrators can work with the four school-role accounts, account status and available permissions.
Selected school and platform actions can be recorded for audit and review. Confirm the actions covered and applicable retention for your release and agreement; not every action is claimed to be immutable or retained forever.
The website does not currently publish a product-data hosting country or region or encryption scope in transit or at rest. Do not infer product-data location from the marketing website’s hosting; bring the requirement into the security review.
Not yet. Backup frequency, retention, restore testing and disaster-recovery targets remain unpublished. Bring any required terms into the security review.
No current security certification or certification logo is claimed on this website. Evaluate a certification only with its verified scope, issuer, validity and supporting record.
Applicable data-export, retention and deletion terms are addressed in the school’s agreement. Formats, self-service workflows and timelines are not currently published.
No blanket Digital Personal Data Protection Act compliance claim is made on this website. Review the applicable responsibilities, notices and agreement terms for your school’s context.
Confirm account ownership, roles and relationships, permissions, login verification and delivery requirements, audit and file needs, plus any required export, retention, deletion, hosting, encryption, backup or incident terms.
Security review
Bring the roles, login path, audit needs, file workflows and agreement terms your school wants to confirm.