Help
Frequently asked questions
Business and technical answers for SIGHTLEARN operators.
Business
What is SIGHTLEARN?
SIGHTLEARN is a multi-tenant K-12 SaaS platform covering SIS, learning, finance onboarding, identity, and institution CMS websites — branded for sightlearn.com.
Who can sign up?
Institution Owners self-signup at /signup, then verify with a 6-digit email code and enrol Google or Microsoft Authenticator. Platform Owner accounts are created manually by an authorized Platform admin (no public signup, no invite email). Staff (Admin/Teacher) may still receive an Institution Owner invite.
How does multi-tenancy work for schools?
Each institution is an isolated tenant with its own users, SIS data, CMS site, and configuration. Cross-tenant data access is forbidden by design.
What CMS templates are included?
Four full institution website templates: Classic Academic, Modern Minimal, Community Vibrant, and International Boarding — each with Home, About, Admissions, News, and Contact.
Is finance fully live in the foundation release?
Finance onboarding (entity setup, fee catalogs, contacts) ships in the foundation. Discretionary payouts and full ledger automation remain on the roadmap.
Technical
Which authentication model does SIGHTLEARN use?
Local Database is the elected default for both platform and tenant surfaces (TEP §6.1): Institution Owner signup → email OTP → Argon2id password → Google or Microsoft Authenticator. Later logins are password then TOTP, with an opt-in email OTP fallback if the app is unavailable. Microsoft Entra ID is an optional Integration Module (70) provider and is never the elected default. Local Database is never removable.
What databases are supported?
Prisma with SQLite for local development and a Postgres/SQL connection string for production (Azure SQL / Postgres).
Where is the OpenAPI contract?
See API/openapi.yaml (OpenAPI 3.1) covering auth, users/roles, tenants, cms, blog, and health modules.
How do I run the stack locally?
Install with pnpm in Frontend and Backend, run Backend migrations + seed, then `pnpm dev` in each package. Frontend :3000, API :4000.
Are test routes included in production images?
No. Test-only routes are stripped from the production API, and unit tests are excluded from Docker context via .dockerignore.