# Part 1 · First run

## 1.1 Setting up a new workspace

**Who** · Owner: whoever may hand the workspace over.

**Where** · Offered by itself, the first time you open the workspace (`/setup/workspace`).

**Before you start** · Two-factor, set up: as shipped the platform requires it of the account holder, so the first
sign-in asks for it before the wizard opens (the Sign-in manual, 1.3). Every step can be skipped; **Skip the rest**
ends it.

**The steps**
1. **Your workspace**: its name, a short name (up to three letters, for the chip), its legal name, the chip's colour, a
   logo (PNG, JPEG or WebP; it shows once the scan says it's clean).
2. **Where you are**: choose the country, which fills the time zone, currency and language; change any of them.
3. **Signing in**: who must use two-factor: *those who can change access* (recommended: the roles that can change
   access, named for you), *everyone*, or *each person chooses*. While the platform requires it of the account holder,
   your role keeps it whichever you choose, and *each person chooses* says so. Your password again. The idle timeout
   is the platform's, shown, not asked.
4. **Your team**: a row for each person (first name, family name, e-mail, role among those you may give). Each is
   added as **Add a person** adds them and gets an invitation. Or **Import a spreadsheet**.
5. **Ready**: what was set. **Go to the dashboard**.

**What the record shows** · The same as each form would: Settings › This workspace, Settings › Regional, each role's
two-factor rule, each person's place, role and invitation, each in the audit log.

**Who is told** · The people you added get their invitations.

**What can go wrong**
- *You're asked to set up two-factor mid-way.* You chose two-factor for a role you hold. Set it up (keep the recovery
  codes), then open the dashboard: the wizard carries on where you left it.
- *"Someone like this may already be here".* Add them from **People**, which asks whether it's the same person.
- *"That role isn't yours to give".* Choose one within your own reach.

## 1.2 Finishing the getting-started steps

**Who** · Anyone; each sees the steps their permissions reach.

**Where** · The dashboard's card; or **Settings** › **Getting started** (`/setting/started`).

**Before you start** · Nothing.

**The steps**
1. Each step shows ticked, with where it stands, or what's left and **Do it**.
2. A step ticks itself once the record is really there: a short name, legal name, colour or logo; a currency; a role
   that requires two-factor by this workspace's choice (the platform's rule for the account holder doesn't tick it);
   someone besides you in the workspace.
3. The eye hides the card for you. **Settings** › **Getting started** keeps the steps, shows the card again, and offers
   the wizard again to whoever may hand the workspace over.

**What the record shows** · Each step's first completion in the workspace, once (what the Service sees).

**Who is told** · Nobody.

**What can go wrong**
- *A step you did isn't ticked.* Its record isn't there yet (a logo still being scanned, an invitation not sent).

## 1.3 This workspace: its name, chip and logo

**Who** · Whoever's role holds *Change the workspace's settings* (reading: *See the settings*).

**Where** · **Settings** › **This workspace** (`/setting/workspace`).

**Before you start** · Nothing.

**The steps**
1. Change the name, short name, legal name, chip colour, or the logo (or remove it). **Save**.

**What the record shows** · The workspace's change in the audit log; the logo in the file vault.

**Who is told** · Nobody; everyone sees the new chip.

**What can go wrong**
- *"The logo must be a picture".* PNG, JPEG or WebP.

## 1.4 Seeing who stalled, and reminding them (the Service)

**Who** · The Service.

**Where** · **Workspaces**: the *Getting started* column; the bell on a workspace's row.

**Before you start** · Nothing.

**The steps**
1. Each workspace shows how many steps it has done and when the last was.
2. The bell sends a reminder to whoever may hand it over, saying how many steps are left.

**What the record shows** · *Reminded of the getting-started steps* in the audit log.

**Who is told** · The workspace's Owner, on the bell and by e-mail as they chose.

**What can go wrong**
- *No bell on a row.* That workspace has done every step.

---

## 1.5 Starting a workspace by yourself (where sign-up is on)

**Who** · Anyone, on a platform that has turned sign-up on.

**Where** · The sign-in page › **New here? Create a workspace**.

**Before you start** · You can read mail at the address you'll use. If there's no link on the sign-in page, this platform
makes workspaces itself: ask its people.

**The steps**
1. Type your organisation's name, your name, your e-mail and a password, and **Send me a code**.
2. Type the 6-digit code from the e-mail, and **Make my workspace**.
3. You're signed in as its Owner. Set up two-factor, and the first-run wizard (1.1) takes it from there.

**What the record shows** · The workspace's audit log has "Workspace made, and its Owner named".

**Who is told** · You, by e-mail. The platform's owner hears the workspace's name.

**What can go wrong**
- *No code arrives.* If the address already has an account, you'll get an e-mail saying so instead, and no code: sign in.
- *"That code no longer works."* It ran out, or there were too many wrong tries. **Send a new code**.
- *The address is refused.* Throwaway addresses aren't accepted. Use one you'll keep.