Platform & trust · White-label & configuration

Your school's brand and rules, without custom code.

Your name, logo, colours, domain and terminology, plus your own academic structure, forms and workflows—changed safely with preview, approval and rollback.

  • Your brand and domain
  • Your terminology
  • Forms and workflows
  • Preview and rollback
Configuration StudioAster Grove

Aster Grove School · Example

School identity · Draft v4

School brandLogo, photo and colours
Draft
Academic structureTerms and year groups
Validated
PublicationAuthorised approver
Awaiting review
Make the platform feel like your school

Identity and terminology can change while permissions and record boundaries remain in place.

Setup administratorDraft, validate, approve and publish, with version history.

Who White-label & configuration is for

  • School owners

    A platform families know as yours.

  • Setup administrators

    Configure without developers, with version history.

  • School groups

    Shared standards with each school's own identity.

What it fixes

What White-label & configuration fixes

Where schools usually struggle, and what changes.

  • Problem: Software that looks like someone else's

    With School Niva: Your brand on the web, app, emails and documents.

  • Problem: Changes that need a developer

    With School Niva: Configure structure, forms and rules yourself.

  • Problem: One mistake breaks everything

    With School Niva: Preview, approve and roll back any change.

What's included

Everything in White-label & configuration

Use what you need now; switch more on as your school grows.

Brand

  • Logo, colours and imagery
  • Your own domain
  • Branded emails, documents and certificates
  • Your brand in the mobile experience

Structure

  • Academic structure and terms
  • Your own terminology
  • Grading and report templates
  • Languages and regional settings

Workflows

  • Form builder
  • Approval rules
  • Notification templates
  • Role setup

Safe change

  • Draft and preview
  • Automatic validation
  • Approval before publishing
  • Version history and rollback

Want the full picture? White-label and configuration in depth

Connected

How White-label & configuration connects

It shares data with the rest of the platform, so nothing is typed twice.

Draws on

  • EntitlementsThe modules your school uses
  • DomainsYour own web address

Feeds into

How it works

Every change previewed, approved and reversible

Every step has an owner. Key decisions stay with people.

  1. Draft

    A change is prepared without touching the live school.

    Setup admin
  2. Preview

    See it as each role will see it.

    Setup admin
  3. Validate

    Checks catch conflicts and missing pieces.

    Platform
  4. Approve

    An authorised person signs it off.

    ApproverApproval
  5. Publish

    It goes live with a version you can roll back.

    Platform

Safeguards

Safeguards built into White-label & configuration

Configuration is stored per school, separate from student records.

It always

  • Keeps security and privacy controls the same for every school
  • Records who changed what and when
  • Lets you roll back any published change

It never

  • Lets configuration switch off audit or privacy protections
  • Needs custom code for your school

Where AI helps

Configuration help suggests settings. An administrator approves every change.

See it working

See your school's brand on the platform.

Set up around your school, with your own terminology.