How do I sign up, choose my School Code, and take my school live?
Updated 23 Aug 2026
In short
Onboarding establishes the School Code, selected starting defaults, a setup checklist and Quiet Mode. Defaults are starting points—not proof that every module, integration or AI workflow is live. Plan scope, permissions, provider setup and representative tests still determine go-live readiness.
School onboarding creates a workspace, establishes its School Code, and keeps non-essential communication quiet while authorised staff review imported records and configuration. Feature availability still depends on the selected plan, permissions, deployment configuration, and any required provider setup.
Signing up
The registration flow collects the required school and owner details and may use a six-digit email verification code. Optional profile fields include the board, academic year, UDISE+ code, address, principal, and trust or society details. A selected board can seed supported defaults, but the school must review grading and report-card rules before publishing results.
Choosing a School Code
The School Code is the web-friendly identifier used in supported public and join links. It accepts 3 to 30 lowercase letters, numbers, and hyphens, subject to availability and reserved-name checks. If the School Code changes later, previously shared links or QR codes may stop working and must be reviewed and reissued.
What setup defaults mean
Supported setup paths can seed items such as a starting chart of accounts, board or grading configuration, leave or document types, and a paused starter-automation library. A seeded default is a starting point—not evidence that every module, integration, AI workflow, or statutory configuration is ready for live use.
The Getting Started checklist
Use Getting Started to review school profile, students, staff, fee setup, invoices, exams, messaging, branding, automation, and the final go-live decision. Each applicable item should be verified against a representative record before the school enables broad access or communication.
Quiet Mode and go-live review
New workspaces use Quiet Mode to suppress supported non-essential family messages while data and communication settings are checked. Essential identity or access messages may follow a separate path. Quiet Mode is a product safeguard, not proof that every external provider or custom integration is disabled; perform a controlled communication test and review configured automations before go-live.
When the authorised team is ready, use the go-live control and confirm any fee-recovery start date. Review imports, recipients, consent, templates, provider configuration, fees, roles, and data exports first.
Frequently asked questions
Can I change my School Code?
Use the supported School Profile control where available, confirm the warning, and reissue affected links or QR codes.
Does setup make every capability ready?
No. It supplies selected defaults and a checklist. Plan entitlement, permissions, provider configuration, school policy, and representative workflow tests still determine readiness.
Will every message be held during setup?
Quiet Mode suppresses supported non-essential family communication. Review essential access messages, provider-specific traffic, and custom integrations separately.
Didn't find what you needed?
Ready to try Vidyapeeth360?
Start a 90-day free trial — no card.