Skip to main content
Schoolyi
Sign inContact us

Secure sign in, roles, and school wide settings

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. Onboarding staff and provisioning accounts should not become a second full-time job. Schoolyi centralises user management, role assignment, and school configuration so your team spends less time chasing access requests and more time running the school. Leadership can review activity when needed. A deployment can hold several schools, each with its own branding and settings, though a user belongs to one school and only a platform administrator can move between them.

Request demoAll modules
Illustrative school scene for Features Platform

Outcomes

What changes when this module is live

Practical results schools report after rolling out this area on the shared calendar and roster.

  • Sign-in with password reset and email verification

    New hires get the right access on day one without IT back-and-forth

  • User accounts with bulk import and role assignment

    Sensitive data stays limited to the roles that need it

  • Permission matrix per role - gates every page and workflow

    One place to update branding, grading rules, and school profile

  • School settings: branding, grading scale, notifications

    Leadership can trace important changes when questions come up

Product truth

What to verify before rollout

Good school software copy should answer who owns the work, what the handoff produces, and which parts still depend on deployment decisions.

Validate for your rollout

Capability status

This page describes the supported workflow boundary. Confirm configuration, integrations, data, and policy requirements in a representative pilot before committing to production.

Teams in the workflow

  • Platform admins
  • IT coordinators
  • School leadership

Deep dive

Decisions, handoffs, and boundaries

Use these details to turn a product page into an implementation conversation.

Why schools upgrade platform & access

Onboarding staff and provisioning accounts should not become a second full-time job. Schoolyi centralises user management, role assignment, and school configuration so your team spends less time chasing access requests and more time running the school. Leadership can review activity when needed. A deployment can hold several schools, each with its own branding and settings, though a user belongs to one school and only a platform administrator can move between them.

Connected to the rest of your SMS

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. Because Platform & access shares roster and calendar data, teams stop reconciling exports between spreadsheets and the parent portal.

Evidence layer

Read the supporting product and implementation material before making a capability claim.

Key capabilities

Everything included in this module, from daily workflows to exports your team relies on.

  • Sign-in with password reset and email verification
  • User accounts with bulk import and role assignment
  • Permission matrix per role - gates every page and workflow
  • School settings: branding, grading scale, notifications
  • Several schools on one deployment, each with its own branding and settings
  • Activity log with CSV export for operational review
  • Data-quality and setup tools for administrators

Who uses this

Role-scoped workspaces so each team sees only the tasks they own.

  • Platform admins
  • IT coordinators
  • School leadership

From the blog

Role-based access control: keeping school data on a need-to-know basis

Teachers, finance, admissions, and families should each see a scoped workspace - with audit trails when sensitive records change.

Read the guide →

Capability deep dives

Focused pages for evaluators comparing specific platform & access workflows during an SMS rollout.

Workflow

How teams run it week to week

A typical path from setup through daily use on Schoolyi.

  1. 01

    Sign-in with password reset and email verification

    Part of the Platform & access workflow on Schoolyi, connected to roster, calendar, and role permissions.

  2. 02

    User accounts with bulk import and role assignment

    Part of the Platform & access workflow on Schoolyi, connected to roster, calendar, and role permissions.

  3. 03

    Permission matrix per role

    gates every page and workflow

  4. 04

    School settings: branding, grading scale, notifications

    Part of the Platform & access workflow on Schoolyi, connected to roster, calendar, and role permissions.

Deep dive

Built for school operations, not generic ERP

Long-form context for evaluators comparing modules during an SMS rollout.

School IT administrator managing secure access and roles

Why schools upgrade platform & access

Onboarding staff and provisioning accounts should not become a second full-time job. Schoolyi centralises user management, role assignment, and school configuration so your team spends less time chasing access requests and more time running the school. Leadership can review activity when needed. A deployment can hold several schools, each with its own branding and settings, though a user belongs to one school and only a platform administrator can move between them.

School finance manager reviewing fee records and receipts in an administration office

Connected to the rest of your SMS

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. Because Platform & access shares roster and calendar data, teams stop reconciling exports between spreadsheets and the parent portal.

Related modules

These areas work closely with platform & access and share the same calendar, roster, and role model.

Questions, answered

Straightforward answers for visitors evaluating the product.

Can we mirror our existing role names and permission matrix?+

Yes. Administrators map school roles to module access. Teachers, finance, admissions, and family portals inherit only the pages their job requires.

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.

How do multi-campus groups switch between schools?+

Users with access to multiple campuses pick the active school after sign-in. Rosters, fees, and calendars stay scoped to that tenant.

Confirm the campus scope and reporting boundary with a representative deployment before treating the capability as group-wide. Record which work remains local when the school group plans its rollout.

Do families get separate accounts for each child?+

Guardians link to every child in one parent portal. Fees, attendance, and published grades appear per student without duplicate logins.

Before the first collection cycle, reconcile one paid, partially paid, and overdue student account so the family receipt and finance view agree. Keep any tax, gateway, refund, or accounting boundary as an explicit deployment decision.

Can leadership export activity for audits?+

Platform admins can review operational activity and export CSV snapshots when investigating access or configuration changes.

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.

Students walking together across a school campus at sunset

See Platform & access in a live walkthrough

We'll show how this module fits your school's workflows and which teams benefit first.

Book a demoSee all modules

Already using Schoolyi? Sign in