Confirm school.
- Account input
- Person + school
- Access decision
- Confirm holder
- Controlled handoff
- Choose category
- Current action
- Use the account record and school relationship.
- Connected outcome
- People records do not create or activate logins.
Connect people, accounts and access.
Connect relationships, status and permissions.
Move from school to role workspace.
Six stages show setup, access and verification boundaries.
Separate administration from recipient access.
School Administrators maintain supported account controls; other roles use their own context.
Inspect three states.
Fictional school data proves only visible states.
State 2 · Permission groups.
Focused fictional example. On smaller screens, expand to inspect all eight groups; selections are not defaults or recommendations.
State 3 · Linked Student.
Linked Student—not automatic matching, creation or activation.
Separate controls from identity claims.
Review scope, rollout decisions and boundaries.
Supported today
- Four categories: School Administrator, Teacher, Parent/Guardian and Student
- Overview and category lists
- Role-specific paths and statuses
- Eight named interface permission groups
- Representative requests resolve school, role and account
Validate before rollout
- Account ownership and statuses
- Administrator permissions
- Assignments and family relationships
- Verification delivery
- Migration and deprovisioning
Current boundaries
- No SMS delivery, resend or server-backed expiry claim
- No SSO, SCIM, TOTP, passkeys, WebAuthn or MFA claim
- No arbitrary custom roles, user-defined RBAC or policy engine
- Visible administrator designations are not separate authorization roles
- No automated provisioning, directory sync or access reviews
- No universal revocation or complete account-change audit claim
Bring fictional role paths.
Trace controls without production identities.
Clarify access boundaries.
Answers reflect the verified release.
Which school account categories are supported?
School Administrator, Teacher, Parent/Guardian and Student each have a path.
Can module access differ by School Administrator?
Yes. Select eight named interface groups per School Administrator; effective access follows mapped checks—not custom roles.
Are the administrator designation choices security roles?
No. Designations are labels; supported permission checks determine effective access.
Does Schylva currently send a login code by SMS?
No public SMS delivery is verified. Approve delivery for the code interface before rollout.
Does creating a Parent/Guardian account link a Student automatically?
No. Account creation does not prove automatic family matching or Student linking; maintain the relationship separately.
Does User Access Management include SSO, SCIM or custom RBAC?
No. SSO, SCIM, directory sync, custom roles, user-defined RBAC and policy engines are outside scope.