OXC OneXCube Story-led learning

OneXCube field notes

Requirements

The practical inputs needed to run OneXCube cleanly for a home, academy cohort, or school tenant.

Manual status

A working product manual, not a developer-docs theater. Use it to decide who does what first.

Before launch

School inputs

A clean OneXCube rollout starts with the roster shape: branches, classrooms, student age bands, teacher owners, and parent contact rules. The first pilot can stay small as long as those boundaries are clear.

Branch list
Classroom list
Student age bands
Teacher owners
Parent contact policy
Preferred payment flow

Baseline

Technical baseline

  • Tenant domain: choose a school slug or custom domain path.
  • Payments: Stripe and Paystack can support the marketing flows.
  • Storage: student audio and worksheet images stay behind private access rules.
  • Integrations: bring roster imports first; SSO can follow after pilot proof.