# Part 1 · Imports

## 1.1 Importing people from a spreadsheet

**Who** · Admin: anyone whose role holds *Import people from a spreadsheet*.

**Where** · **People** › **Import people** (`/import/person`).

**Before you start** · A CSV or Excel (.xlsx) file whose first row names its columns. **Download the template** if you
want the columns the import knows, with an example row and a sheet of notes (what each column takes, the ID kinds and
how each is written). If you have an import that isn't finished, the page offers to **carry on with it** instead.

**The steps**
1. **The file.** Drop it on the page, or choose it, then **Next: the columns**. The file is scanned for malware; its
   rows are read as soon as it's clean (a moment, usually; the page waits by itself).
2. **The columns.** Each column of your file is shown with its first values, and what it **becomes**: a first name, a
   family name, an e-mail, a mobile, a date of birth, an ID, roles, *your number for them*, or **Ignore this column**.
   Each is guessed from its heading: **matched** (the heading is one we know, or what you chose last time), **a guess:
   check it**, or **ignored**. Change any. First name and family name are required (\*); a column fills one field.
3. **How to read it.** Say how dates are written (day/month/year, month/day/year, year-month-day). If a column holds
   IDs, say which kind (from Input Fields › ID kinds). If a column holds roles, each of its values is listed: choose
   the role it becomes, among the roles you may give, or *no role from this* (they get the default role).
4. Leave **Remember these columns for next time** on, and the next file with the same headings is matched for you.
5. **Next: check every row.** Every row is checked in the background, with a count; then you see the check (1.2).
6. **Import N people.** It runs in the background; you can leave the page (1.3).

**What the record shows** · Until you choose **Import**: only the import itself (its file, its rows, what the check
made of each). Nobody is added, no ID or role is given, nothing reaches the audit log but *Import started*. Once you
import, each person added or linked is in the audit log, each change carrying the import's tag, under one *Import
finished* entry; their place here remembers the import and your number for them.

**Who is told** · You, when it's done: on the bell, and by e-mail if you keep *Your work* by e-mail (What reaches you).
The people imported are told nothing until you invite them (1.3).

**What can go wrong**
- *"Choose a CSV or Excel (.xlsx) file".* An old .xls workbook, a PDF, or a file with another ending. Save it as .xlsx or
  CSV first.
- *"The file was refused: …".* The scan found malware, or the file vanished before it could be scanned. Nothing was read.
- *"It has more than 5,000 rows".* Split the file into two.
- *"It has no rows under its headings".* The first row is the headings; there must be rows under it. A workbook whose
  first sheet is notes is read from its first sheet with rows; choose another **Sheet** above the columns.
- *"… must come from a column".* First name or family name has no column. Choose one.
- *"Finish or discard your import that isn't finished first".* You have one open: carry on with it, or discard it (1.5).

## 1.2 Fixing the rows the check found

**Who** · The person who ran the import.

**Where** · The import's page, at **The check**.

**Before you start** · The check has run. It is a dry run: **nothing is saved yet**.

**The steps**
1. Four tiles say what would happen: **new people**; **already here** (never added twice);
   **need a fix**; **twice in the file** (the first is kept).
2. **Every row** lists them by outcome: **To fix**, **Twice in the file**, **Linked**, **Already here**, **New**, **All**.
   Each row says why, in the words of its column: *"Email address: The e-mail field must be a valid email address."*, *"“31/02/1988” isn't
   a date written day/month/year"*, *"“Head of Ops” matches no role you may give"*, *"someone here has the same name
   and date of birth (Kojo Badu): if it's someone else, add them with Add a person, which asks"*.
3. **The rows left out, as a CSV** downloads those rows as your file had them, with a last column saying why. Fix them
   there.
4. Then choose: **Import the N good rows** (the rest are left out; import the fixed file afterwards), or **Fix the
   file first** (this import is discarded; upload the corrected file when it's ready). **Change the columns** goes back
   a step.

**What the record shows** · Nothing new: the check reads, it doesn't write.

**Who is told** · Nobody.

**What can go wrong**
- *A row is "To fix" that Add a person would take.* It can't be: each row goes through the same rules as the form. The
  same name and date of birth as someone here is the one difference: the form asks you; a file can't, so the row
  waits, and you add that person by hand if they are someone else.
- *Someone in the file may be known in another workspace.* The check never says so: they count as new. Their ID, or
  an e-mail or mobile they confirmed, links them rather than making them twice, and you see only what your file says
  about them (25 October 2026).

## 1.3 After the import: the report and the invitations

**Who** · Admin. Only the person who ran it sees the invitations panel if they may invite.

**Where** · The import's page, at **Importing**, then **Done**; or the bell's notice.

**Before you start** · You chose **Import**.

**The steps**
1. **Importing** counts the rows as they go in, with the rate and the time left. Leave the page if you like.
2. **Done**: added, already here, left out, and how long it took. **The report** names the file (yours to download, kept in
   the file vault), who ran it and when, until when it can be undone, and the rows left out as a CSV.
3. **Invitations**: **Invite all N now** sends each new person with an e-mail and no account an invitation to choose a
   password, over the next few minutes. **Not yet** leaves them on the records; invite them from their page later.
4. **Every row** shows what became of each: added, already here, left out.

**What the record shows** · Each person's place here, with *the import* it came from and *your number for them*. In
the audit log: *Import finished*, and every change it made under its tag; each invitation sent.

**Who is told** · You, by the bell (and e-mail, if you chose). The people invited get their invitation e-mails.

**What can go wrong**
- *"Stopped after N rows".* Something broke part way. What it made is in the report; **Undo** takes it back (1.4); then
  import the file again.
- *A row the check passed is now "To fix".* Something changed between the check and the import (someone added that
  person by hand meanwhile). The rest went in; the row says why.
- *Nobody to invite.* Everyone it added already signs in, has no e-mail, or has an invitation.

## 1.4 Undoing an import

**Who** · Admin: anyone who may import, not only the person who ran it.

**Where** · The import's page › **Undo this import**, or **Earlier imports** › the undo arrow on its row.

**Before you start** · Within 24 hours of the import finishing (the workspace's *An import can be undone for*).

**The steps**
1. **Undo this import**. The dialog says how many it would take back and how many stay, by row, because someone has
   changed them since.
2. **Undo the import**. What it made goes back:
   - someone it **added** leaves this workspace, and, with no other place and no account, the platform;
   - someone it **linked** loses the place it gave them here, and stays on the platform as they were;
   - someone it **gave their place back** is removed again, with the roles they had.
3. What someone **changed since** stays: their details edited, their roles changed, an invitation sent by hand, or
   they signed in. The report says which rows stayed and why.

**What the record shows** · *Import undone*, with how many went back and how many stayed; each removal under the
import's tag. The import's line stays, marked **Undone**.

**Who is told** · Nobody.

**What can go wrong**
- *"An import can be undone for 24 hours after it's done".* The window has passed. Remove people one at a time from
  their page.
- *More rows stay than you expected.* Someone changed them since the import, perhaps only an invitation. They are
  someone's work now; remove them by hand if you must.

## 1.5 Earlier imports, and discarding one

**Who** · Admin.

**Where** · **Import people** › **Earlier imports**.

**Before you start** · Nothing.

**The steps**
1. Each import of this workspace: its file and rows, who, when, its outcome (added, linked, left out). Search by file,
   filter by outcome or date.
2. The folder opens its report. The undo arrow appears while it can be undone, with until when.
3. An import that isn't finished can be **discarded** from its page (the bin, top right): its file and rows go;
   nothing was imported.

**What the record shows** · *Import discarded*. After 30 days, every import's file and rows go with the night's purge
(an unfinished one is discarded then); its line, its counts and the audit log stay.

**Who is told** · Nobody.

**What can go wrong**
- *An import's rows are gone.* It is older than 30 days: its line and counts stay, and the audit log says what it did.
