What this guide covers
- the two export paths available in Superadjust
- what teachers and coordinators can export
- what is included in a generated export
- what happens to the export after it is created
Quick answer
Superadjust supports two export layers: direct per-student PDF exports for quick single-student downloads, and stored export packs with history and re-download support for broader exports. The backend creates a server-side file, stores export metadata, and keeps history available even after the original download window passes.
Step 1: Choose the export path
Superadjust supports two export layers: direct per-student PDF exports and stored export packs with history and re-download support.
Direct student exports use shortcut endpoints for a single student. The teacher evidence PDF includes only the requesting teacher's evidence. The coordinator NCCD pack returns the full student pack for the school context.
The main pack builder creates a broader export through the standard export flow and stores file metadata in the export history tables for later access.
| Export Path | Best For | What It Returns |
|---|---|---|
| Direct student PDF | One student | A teacher evidence PDF or coordinator NCCD pack for a single student |
| Stored export pack | Multiple students or a wider export | A generated export with saved metadata, history, and download controls |
Export Flow
Select Export
Choose students and options
Build File
Generate server-side snapshot
Save Metadata
Store export history
Download
Now or re-download later
Step 2: Understand what gets exported
The export controller gathers student records, evidence rows, related resources or attachments, readiness cache rows from student pillar scores, and school or teacher metadata.
Snapshot, not live query: The final file is a backend snapshot of the selected data, not a live query that changes after download.
For the main pack builder, the generated ZIP can include a summary report PDF, one PDF per student, optional attachments, a manifest file, and an audit hash file.
What the Export ZIP Contains
Summary Report PDF
Overview of all included students
Student PDFs
One PDF per student with evidence
Attachments
Optional linked files and resources
Manifest File
List of all files in the export
Audit Hash
SHA-256 integrity verification
Step 3: Know who can export what
Teachers can export their own students and any linked students where the row-level access checks pass.
Coordinators can export school-wide data when the export permissions and same-school checks allow it.
Route-level vs row-level: Route-level permission is broad, but the controller still narrows the actual student set by ownership and school membership before it returns anything.
Why this matters
Exporting your data is more than a download button. The backend creates a server-side file, stores export metadata, and keeps history available even after the original instant download window passes.
- Teachers and coordinators have a clear record of what was exported.
- The system tracks when the export was built.
- History preserves which data set was included at that moment.
- Re-downloads remain available through export history.
Common mistake
Export is not a live view: The most common mistake is assuming the export is just a live view turned into a file. It is not. The system creates a generated snapshot and stores history and retention metadata separately from the active UI.
What to do next
If you need a full pack, use the standard evidence export flow. If you only need one student, use the direct student PDF path that matches your role. Then review export history if you need to re-download the file later.
For detailed step-by-step instructions on exporting evidence packs, see the How to export an evidence pack guide in the Exporting & Reporting section.