# Part 1 · People

## 1.1 Signing in

**Who** · `Member` · anyone with an account.

**Where** · The sign-in page, where every address leads until you are signed in.

**Before you start** · An account. A workspace invites you by e-mail (the Mail manual, 1.3); the operator can also make one (1.8).

**The steps**
1. Type your e-mail and your password.
2. Tick *Keep me signed in on this device for 14 days* only on a device that is yours (the Sign-in manual, 1.8).
3. Press **Sign in**. You arrive in the workspace you were last in.

**What the record shows** · Each sign-in, each failed try (with the e-mail typed) and each sign-out is in the sign-in
log, with the address and browser it came from.

**Who is told** · Nobody.

**What can go wrong**
- *"That e-mail and password don't match an account."* One of the two is wrong; for your safety it doesn't say which.
- *"Too many tries."* After a few wrong tries in a minute, wait the seconds it says.
- *"You're not in a workspace yet."* Your account works, but nobody has added you to a workspace.
- *"Your access is turned off."* Someone turned your access off in your workspace (1.6). Ask them.
- *"… is paused."* The workspace is suspended. Your other workspaces are listed on that page.

## 1.2 Moving to another workspace

**Who** · `Member` · someone in more than one workspace.

**Where** · The workspace chip at the top of every page: its initials and name, with a small arrow when you have others.

**Before you start** · Active access to the other workspace.

**The steps**
1. Press the chip. Your other workspaces are listed.
2. Choose one. The page opens in it, and says *You're now in …*.

**What the record shows** · Your account remembers the workspace, so your next sign-in opens there.

**Who is told** · Nobody.

**What can go wrong**
- *The chip has no arrow.* You're in one workspace only.
- *A workspace I belong to isn't listed.* It is paused, or your access to it is turned off, or the e-mail it holds
  for you isn't the one you sign in with. A workspace lets your account in only through the address it has for you:
  ask someone there to set it to your sign-in address.

## 1.3 Finding a person

**Who** · `Admin` · someone who may see the people.

**Where** · **People** in the menu.

**Before you start** · Nothing.

**The steps**
1. Type a name, an e-mail, a mobile number or an ID number in the search box. An ID number is found however it was
   typed: spaces, dashes and capitals don't matter. Only what this workspace recorded is searched.
2. Choose *Active*, *Deactivated* or *All* above the list; each shows how many.
3. Press a name to open the person. The Lists manual shows the rest: filters, columns, saved views and export.

**What the record shows** · Nothing: looking is not recorded.

**Who is told** · Nobody.

**What can go wrong**
- *There's no People in my menu.* Your role doesn't include seeing people.
- *Someone I added in another workspace isn't here.* Each workspace lists only its own people.

## 1.4 Adding a person

**Who** · `Admin` · someone who may add people.

**Where** · **People** › **Add a person**.

**Before you start** · Their first and family name. An e-mail, a mobile and a date of birth help find them if they
are already known.

**The steps**
1. Type who they are. The first and family names are required (the red asterisk).
2. Press **Add a person**.
3. If someone in this workspace has the same name and date of birth, the page asks whether it's the same person.
   Choose *Yes, the same person* to open that record, or *No, someone else* and press **Add a person** again.
4. Their page opens, and says they are added.

**What the record shows** · The new person and their membership are in the audit log. They get the workspace's default
role. They have no account yet, so they can't sign in.

**Who is told** · Nobody yet: they can then be invited from their page, by e-mail if the workspace holds one (the Mail
manual, 1.3), otherwise by text to their mobile. A text invitation names the organisation, never who added them; they
prove the number with a code and are in, with an account of their own and no password (plan CL, CL4). Someone whose
mobile or e-mail already signs in to an account needs no invitation: that account is let in already.

**What can go wrong**
- *"Someone in this workspace already uses this e-mail."* Use another, or open their record.
- *"This person is already in this workspace."* The e-mail they sign in with matched someone already here.
- *The person is known in another workspace too.* An ID number, the e-mail they sign in with, or a mobile they confirmed, names one
  person on the whole platform, so they are linked rather than made twice. Nothing tells you so: you see only what you
  typed, and the other workspace sees only what it recorded. Each keeps its own name, e-mail, mobile and date of birth
  for them.

## 1.5 Changing a person's details

**Who** · `Admin` · someone who may change people's details, for anyone but themselves.

**Where** · The person's page › the pencil, or the pencil on their row.

**Before you start** · Nothing.

**The steps**
1. Change what needs changing.
2. Press **Save changes**.

**What the record shows** · The audit log keeps what each detail was before.

**Who is told** · Nobody.

**What can go wrong**
- *The e-mail can't be changed.* It is the address they sign in with, which is how this workspace lets their account
  in; only they can change it, with a confirming link (later).
- *"Not saved: … changed meanwhile."* Someone saved this person after you opened the page. It says who and when; the
  page reloads with their change, and you make yours again.
- *Does my change show in another workspace?* No. The details are this workspace's own record of them; another
  workspace that knows the same person keeps its own, and neither sees the other's.
- *"Someone in this workspace already has that number."* An ID number belongs to one person here. Open their record:
  it may be the same person twice. (A number someone in another workspace holds is saved without a word; the operator
  is shown the pair to check.)
- *Their page says they have an account that signs in with another address.* They sign in elsewhere with an address
  this workspace doesn't hold. Ask them for it and put it on their record: their account then reaches this workspace.
  Until then the page shows nothing of how that account is used.

## 1.6 Turning someone's access off, or back on

**Who** · `Admin` · someone who may turn access off, for anyone but themselves.

**Where** · The toggle at the start of a person's row, or on their page. Green is on.

**Before you start** · Nothing.

**The steps**
1. Press the toggle.
2. Read what it will do, and confirm. Turning off is red: they can't enter the workspace until it is turned on again.
3. Turning on gives back the roles they held.

**What the record shows** · The audit log keeps each change and when.

**Who is told** · Nobody yet; notices come later.

**What can go wrong**
- *There's no toggle on my own row.* Nobody changes their own access.
- *There's no toggle on the Owner's row.* They hold more than you do (the Roles manual, 1.1).
- *They're still signed in.* Their very next page refuses them; nothing they open after that works.

## 1.7 Removing someone from the workspace

**Who** · `Admin` · someone who may remove people, for anyone but themselves.

**Where** · The bin on a person's row, or on their page.

**Before you start** · A reason: it is kept.

**The steps**
1. Press the bin.
2. Say why, and press **Remove**.

**What the record shows** · Their membership and its roles end; the reason is in the audit log. Their own account
stays, since it may belong to other workspaces, and so does everything they did.

**Who is told** · Nobody by mail. The organisation's products hear at once by webhook (`membership.ended`) and end it
there too; turning someone off (1.6) does the same.

**What can go wrong**
- *I removed the wrong person.* Add them again (1.4) with the e-mail they sign in with: they get the same membership back,
  with the default role.

## 1.8 Merging two records of the same person (operator)

**Who** · `Operator` · whoever runs the app: merging has no page yet.

**Where** · The command line on the server.

**Before you start** · The public ids of both records (on their pages' addresses), and which to keep. Two records that
both sign in can't be merged.

**The steps**
1. Run `php artisan person:merge <kept> <duplicate> --reason="Imported twice"`.
2. Read the question, and answer yes.
3. To give a person an account: `php artisan person:account <their e-mail>`, the address a workspace recorded for them.
   The password is shown once; pass it on safely. The account reaches each workspace that holds that address.
4. To find people who may be one person: `php artisan person:duplicates` lists records that share an ID number (each
   recorded by a different workspace, which is never told). Check each pair, then merge (step 1).
5. To take a workspace's record off a person it wrongly joined: `php artisan person:split <membership> --reason="…"`,
   with the public id of that workspace's membership (the address of their page there). Read the question, and answer
   yes. They become a new person in that workspace; the other workspaces keep the person as they were. Their account
   goes with the side it signs in to. This is how a workspace that linked someone by their ID number and invited an
   address of its own is undone: the person's own workspace can then invite them.

**What the record shows** · The merge log keeps a snapshot of the merged record and the reason, for good; the audit log
says who merged what.

**Who is told** · Nobody.

**What can go wrong**
- *"Both records sign in."* Two accounts are never merged.
- *"More than one person has that e-mail."* Merge them first.
- *"Their account signs in to both sides, or to neither."* Say where it goes: `--account=follow` (with the memberships
  you move) or `--account=stay`.
- *"Those are all of this person's memberships."* A split leaves at least one behind; to merge or remove instead,
  use those.
