/admin/import brings delegates in from a spreadsheet, usually a cross-delegation list
from another institution.
It appears under Delegates only when the event takes cross delegations: switch Cross delegations on in Setup for a conference. An Intra MUN never shows it, because its delegates come from the Google Form and must be DTU students.
The four steps
-
Upload. A CSV or XLSX file. It is parsed and you see what was found.
-
Map. Match the spreadsheet's columns to platform fields. Full name and email are required; the rest are optional. An AI suggestion pre-fills the mapping, which you then check.
-
Preview. See exactly what will be created, row by row, before anything is written. Mapping mistakes are visible here, which is the entire point of the step.
-
Import. Everyone imported is accepted, with nothing to pay. Anyone whose first free choice is open gets it as a draft seat and is not emailed; the rest show as Accepted, needs a seat. The result ends with what to do next: review the rows that need fixing, view the imported delegates, or assign the remaining seats on Allotment.
If an imported delegate's details are wrong (a mistyped email that bounced, say), click their name on Allotment or Delegates and use the pencil to fix it, then email again.
Do not do this
A successful upload is not a successful import. The preview and the quarantine queue are part of the workflow, not optional extras. Skipping straight from upload to import is how a hundred delegates get created with their phone numbers in the institution field.
Presets
Save a mapping and reuse it. Partner institutions send the same spreadsheet shape every year, so mapping it once is worth it.
The AI helpers
Two of them: one suggests which spreadsheet column is which field, and one cleans messy rows, for example normalising inconsistent institution names. What it changed is written under the name in the preview.
A committee answer that names none of ours is never settled by the AI. The preview shows the original answer in amber with "Did they mean …? Use it", and the row stays out of the import until someone picks a committee or clears the answer.
Quarantine
No row is ever silently dropped. A row that fails validation goes to the quarantine panel rather than disappearing, with the reason.
From there you can fix the source and retry the row, or dismiss it if it was never meant to be imported. Work the queue to empty after every import; a row sitting in quarantine is a delegate who thinks they are registered and is not.
Duplicates
The email address is the identity. A row whose email already exists is rejected rather than creating a second record for the same person.
Partner sheets
A delegation that keeps its own Google Sheet can be connected under Partner sheets instead of sending files. It is read every night: rows it can read are accepted, and anything unclear (a broken row, a committee nobody can match) waits under Rows that need fixing. Review now puts the sheet through the same review as an uploaded file. The card shows when it was last read and what came of it.
After importing
Check /admin/registrations filtered by source. Imported delegates are attributed
distinctly from ones who used the public form, so you can confirm the count landed and
spot anything odd.