CSV: templates and fields
Template download, encoding rules, and common field meanings.
integrationcsv
Audience: Academic ops / Organization admin · Applies to: SaaS / private deployment
Goal: Fill the official template correctly and cut validation failures.
Before you fill
- In Organization Data integration, download the official template for the type (teachers / students / classes / class members, etc.).
- Save as UTF-8; after Excel edits, confirm it did not become ANSI.
- Do not rename header columns; remove empty rows and merged cells.
- One file = one import type.
Field conventions (general)
| Kind | Notes |
|---|---|
| Required | Columns marked required cannot be empty |
| Prefer lowercase; avoid duplicates inside one org | |
| Display name | Name shown in the App |
| Class code | Must match a class already in the system or in the same batch |
| Role | Only template-allowed values (e.g. teacher / student) |
| Initial password | If provided, meet length/policy; or reset after import |
| Student/staff ID | If the template has the column, align with the academic unique key for reconciliation |
Exact column names and enums follow the template file; versions may add/remove columns.
Notes by type
| Type | Watch |
|---|---|
| Classes | Keep codes unique; names may include grade/term |
| Teachers / students | Email is a login key; do not reuse one email across roles unless the product explicitly allows it |
| Class members | Depends on existing class codes and accounts—import classes and people first, then membership |
After filling
Go to First import. Errors: Common import errors.