White-label and configuration

Your school's name on it. Your way of working inside it.

Families, staff and students see your school—your logo, colours, web address and app. Underneath, School Niva fits your terms, workflows and forms, without custom code.

Two implementation leads review governed configuration, approval and rollback across three distinct school identities.

Your identity

Two schools. One platform. Each looks like itself.

Every school gets its own name, logo, colours and web address. Families never see someone else's brand—or ours, unless you want them to.

No separate system for each school.

Aster Grove SchoolGrow with curiosity
Example school
Riverside SchoolLearning that flows
Example school

White-label, everywhere

Everything that carries your school's name.

Branding isn't just a logo on the login page. It follows your school onto every screen, message and document—previewed before it goes live.

  • Sign-in and workspaces

    Your logo, colours and login background on every screen.

  • The mobile app

    Your school inside our app—or your own app in the app stores.

  • Your web address

    Families sign in at your own domain, verified and secured.

  • Emails and notifications

    Messages arrive from your school's name and sender address.

  • Report cards and certificates

    Printed and PDF documents carry your crest, colours and signatures.

  • Language and terms

    Your languages, and your names for years, terms, houses and roles.

Your way of working

Shape it around your school, without code.

Your administrators change terms, workflows, forms and templates themselves. No developer, no ticket, no waiting for a release.

  • Structures and terminology

    ExampleYear 7 → Grade 7 · Term 1 → Autumn term · Houses

  • Workflows and approvals

    ExampleFee concession: class teacher → finance → principal

  • Forms and custom fields

    ExampleAdd “Bus pass number” to the admission form

  • Letters and message templates

    ExampleTrip consent letter in English and Hindi

  • Rules and automations

    ExampleRemind guardians when consent is due

  • Dashboards and saved views

    ExampleEach head of year sees their own year

For school groups

Set it once for the group. Let each school add its own.

Settings stack in layers. A group sets shared policies once; each school keeps its own identity and choices on top—and a new school starts ready.

Related:Shared oversight for school groups

  1. Region

    Calendar, currency, language and local rules.

  2. Board or curriculum

    The academic structure your board expects.

  3. Group

    Policies every school in your group shares.

  4. School

    Each school's own choices, on top.

Change safely

Every change previewed, approved and reversible.

Configuration changes are versioned like the product itself, so a school can move quickly without breaking anything.

  1. Draft

    Make the change in a draft; nothing changes for the school yet.

  2. Preview

    See it on the login, the app, emails and report cards first.

  3. Approve

    Important changes need a second named approver.

    A person decides
  4. Publish

    It goes live as a new version, with its history kept.

  5. Roll back

    Restore the previous version in one step if needed.

    A person decides

What never changes

Flexible on the outside. One product underneath.

No custom code per school—so every school gets every improvement, and nothing a setting does can weaken the platform.

  • Security, privacy and audit controls
  • One product, updated for every school at once
  • Your licensed features—no setting can unlock more
  • Historical records can't be rewritten by a setting

Start with your school

See School Niva in your school's colours.

Send us your logo and how your school is organised. We'll show you the platform set up as your own.

  • Your brand and domain
  • Your terms and workflows
  • No obligation