# Part 1 · Signing in

## 1.1 Signing in with two-factor

**Who** · Anyone who has set up two-factor (1.3).

**Where** · **Sign in**.

**Before you start** · Your phone with the authenticator app.

**The steps**
1. Sign in with your phone, e-mail or username (Part 0).
2. **Enter your code**: type the six digits the app shows, and press **Continue**.

**What the record shows** · The sign-in log: `login` (with two-factor), or `two_factor_failed` for a wrong code.

**Who is told** · Nobody.

**What can go wrong**
- *"That code isn't right."* Codes change every 30 seconds; check the phone's clock. A code works once.
- *Wrong codes in a row lock the account* (1.6), as wrong passwords do.

## 1.2 Using a recovery code

**Who** · Anyone with two-factor who can't reach their app.

**Where** · **Enter your code** › **Use a recovery code instead**.

**Before you start** · One of the eight codes you saved when you set it up.

**The steps**
1. Type one code and press **Continue**.
2. Once in, make new codes when you can: **Your security** › **Make new codes**.

**What the record shows** · The sign-in log: `recovery_code_used`. The code is spent: it never works again.

**Who is told** · You, by e-mail (`recovery_code.used`), with how many codes are left.

**What can go wrong**
- *A code is refused.* It was used already, or the codes were made again since.

## 1.3 Setting up two-factor

**Who** · Anyone; whoever holds a role that requires it is sent here before anything else. As shipped that includes
the account holder (the Owner), from the first sign-in: the platform requires it (**Two-factor for the account
holder**).

**Where** · The menu under your name › **Your security** › **Set it up**.

**Before you start** · An authenticator app (Google Authenticator, Microsoft Authenticator, 1Password).

**The steps**
1. Scan the code with the app, or type the key shown.
2. Type the code the app shows, and press **Turn on**. Only a right code turns it on: until then nothing changes.
3. Your eight recovery codes show once: copy or download them, then press **I've saved them**.

**What the record shows** · The sign-in log: `two_factor_enabled`.

**Who is told** · You, by e-mail (`two_factor.enabled`), with where and when.

**What can go wrong**
- *"That code isn't right."* Type the code showing now; check the phone's clock.
- *No "Turn it off".* Your role requires two-factor.
- *The Owner's role page has no two-factor switch, only "Two-factor: required by the platform".* While the platform
  requires it of the account holder, no workspace can turn it off; the Service can, under Platform settings ›
  Security.

## 1.4 Confirming it's you (step-up)

**Who** · Anyone making a sensitive change: roles, a lens, the platform's settings, turning two-factor off, new
recovery codes, signing out everywhere else. And, unless you signed in within the last 15 minutes, anyone changing what
hands someone a way in at id (plan SEC, 8 November 2026): adding or removing a web address, starting a product, and
adding, removing, deactivating or inviting people, one at a time or by import.

**Where** · Over the page, the moment you press the button. A page opened by its address asks on a page of its own,
then opens.

**Before you start** · Your password, or, if your account has none, your phone or an e-mail address on your account.

**The steps**
1. **Confirm it's you**: type your password and press **Confirm**.
   - *No password?* Choose where the code goes (your numbers and addresses, part hidden), press **Send the code**, type
     the six digits and press **Confirm**.
2. The change you pressed goes ahead as you had it. Nothing sensitive asks again for 15 minutes (**Password re-check
   window**).

**What the record shows** · The sign-in log: `password_confirmed`, or `confirmed_by_code`.

**Who is told** · Nobody.

**What can go wrong**
- *"That password isn't right."* Five tries a minute, then a pause.
- *"That code isn't right. 4 tries left."* Five tries, as at sign-in; then **Send a new code** (after its wait).
- *"Too many codes for … until …"* The number or address is paused as it would be at sign-in: use another of yours.
- *"This account has no verified number or address."* Add one under **How you sign in**, then come back.
- *A product asked for your password and your account has none.* Only a password answers a product's request; add one
  first.
- *Cancel* leaves the page as it is: nothing was changed.

## 1.5 Signed out while away

**Who** · Anyone, unless their browser is kept signed in (1.8).

**Where** · Any page.

**Before you start** · Nothing.

**The steps**
1. Two minutes before the idle timeout, **Still there?** counts down: press **Stay signed in**, or **Sign out now**.
2. If time runs out, or a form is sent after the session ended, **Welcome back** asks for your password (and your code)
   over the page.
3. Signed in again, you are where you were, with what you had typed: send it.

**What the record shows** · Nothing for the timeout itself; the sign-in log records the new sign-in.

**Who is told** · Nobody.

**What can go wrong**
- *The page was reloaded or closed.* The sign-in page says you were signed out after time without use; what was typed
  on that page is gone.
- *"Not you? Sign out"* leaves the page for the sign-in page.

## 1.6 If you're locked out, or told to wait

**Who** · Anyone; `Owner` `Admin` to unlock someone.

**Where** · **Sign in**; a person's page › **Signing in**.

**Before you start** · Nothing.

**The steps**
1. *"Too many tries. You can try again in … seconds."* The button counts down; try again after it.
2. *"This account is locked after 5 wrong tries in a row."* Wait until the time it gives, or reset your password
   (**Forgot your password?**): a completed reset unlocks it.
3. Whoever may change you can press **Unlock** on your page.

**What the record shows** · The sign-in log: `lockout`, then `unlocked` (by a person, or `password_reset`).

**Who is told** · You, by e-mail when it locks (`account.locked`), with the time it opens.

**What can go wrong**
- *Locked though you didn't try.* Someone else did: reset your password.

## 1.7 Signing out everywhere else

**Who** · Anyone.

**Where** · **Your security** › **Sessions** › **Sign out everywhere else**.

**Before you start** · Your password (step-up).

**The steps**
1. Press the button and confirm. Every other browser signed in as you is signed out, and "Keep me signed in" is
   forgotten. A new password does the same by itself (1.9).

**What the record shows** · The sign-in log: `signed_out_everywhere`, with how many sessions ended.

**Who is told** · Nobody.

**What can go wrong** · Nothing.

## 1.8 Keeping a browser signed in

**Who** · Anyone, on a browser only they use; not someone who must use two-factor, unless the platform allows it
(**Kept signed in with two-factor**, off as shipped).

**Where** · **Sign in** › **Signing in as …** › **Keep me signed in on this device for 14 days**: the password step,
for an e-mail or a username. Signing in by a code doesn't offer it.

**Before you start** · Nothing.

**The steps**
1. Tick the box, type your password (and your code), and press **Sign in**.
2. For the days the box names, this browser signs you in by itself, and the idle timeout (1.5) doesn't end it.
3. When the days are up, the sign-in page asks again.

**What the record shows** · The sign-in log: `login`, each time the browser signs you in by itself too.

**Who is told** · Nobody.

**What can go wrong**
- *No box on the sign-in page.* The platform set **Keep me signed in** to 0 days: it isn't offered.
- *Ticked, but asked again after 30 minutes away.* Your role requires two-factor: a kept browser would skip the code,
  so the box is ignored for you. The same happens to a browser already kept once a role starts requiring it.
- *Asked again sooner than the box said.* The platform shortened the days, your password changed (1.9), or you signed
  out everywhere else (1.7).

## 1.9 After a new password

**Who** · Anyone whose password changes: by **Forgot your password?**, or the Service's by `service:reset`.

**Where** · **Choose a new password** (the reset link), or the server's command line.

**Before you start** · The reset link from your e-mail.

**The steps**
1. Choose the new password and press **Save the password**.
2. Every browser signed in as you is signed out, and every browser kept signed in (1.8) is forgotten. Sign in with the
   new password.

**What the record shows** · The sign-in log: `password_reset_completed`, then `password_changed` with how many sessions
ended.

**Who is told** · You, by e-mail, however it changed, so a change you didn't make doesn't go unnoticed.

**What can go wrong**
- *Another device is asked to sign in again.* That is the point: whoever had your old password, or a browser you left
  signed in, is out.

---

## 1.10 Your name and your password

**Who** · `Everyone`.

**Where** · The user menu › **Your account**.

**Before you start** · You're signed in. Inside a lens this page is closed.

**The steps**
1. **Your name:** change it and **Save your name**. This is the name on your account. Each workspace keeps its own
   record of you, and its people can change that one.
2. **Password:** type the new one twice and **Change your password**, then your current password when it asks.

**What the record shows** · The sign-in log has "password changed", with how many other browsers were signed out.

**Who is told** · You, by e-mail, when your password changes.

**What can go wrong**
- *"That is your password now."* Choose a different one.
- *You're the Service and there's no password here.* It's changed on the server: `php artisan service:reset`.

---

## 1.11 Changing the address you sign in with

**Who** · `Everyone` but the Service.

**Where** · The user menu › **Your account** › **Sign-in e-mail**.

**Before you start** · You can read mail at the new address.

**The steps**
1. Type the new address and **Send the link**, then your password when it asks.
2. Open the link in the e-mail at the new address, and press **Yes, use this address**. You don't need to be signed in.

**What the record shows** · The sign-in log has the request and the change. Each workspace that held your old address has
the new one, and its audit log says so. A workspace holding a different address for you keeps it.

**Who is told** · Your current address as soon as you ask, in case it wasn't you. Both addresses when it's done, each
separately.

**What can go wrong**
- *"This address can't be used yet."* Someone in one of your workspaces already has it on their record. Nothing changed.
  Ask that workspace's people to correct it, then ask for a new link.
- *"This link no longer works."* It was used, it ran out, or a newer request replaced it. Ask for another.
- *No link arrives.* Check the address. If it already belongs to an account, no link is sent, and the page doesn't say
  so: that keeps this form from showing which addresses have accounts.
- *You didn't ask for this.* Change your password at once: that cancels the request.
