Formal intake: CSV / API
After formal service is ready, how to import teachers and students at scale with CSV or API; small trial data still uses directory or import entry.
adminintegrationcsvapi
Audience: Organization admins / academic ops / IT · Applies to: SaaS / private
Goal: After formal service is ready (or sustainable use is confirmed), pick the right scale-intake method and jump to the matching how-to.
Timing: Finish Trial expiration and formal service first (at least confirm practice will not stop due to expiry) before large CSV / API.
Few people in trial: keep using Create / Copy in Classes and teachers, or a small sample via Import users (entry).
How to choose (one line)
| Scenario | Where |
|---|---|
| Still deciding | Which intake method |
| One-time spreadsheet at term start | Import users (entry) → shortest CSV path |
| Ongoing sync with academic / SIS | API: when to use → Prepare before integration |
| Only need grade snapshot export | CSV: what it can do (export) |
Suggested order
- Confirm org status is usable (overview / Plan & usage).
- Validate fields and class codes with a small class (UI or small CSV).
- Then full CSV, or bring API live against the checklist.
- After the roster is stable, do Branding and domains.