Security pack
Identity and access
Your people signing in
- Usernames are work email addresses at a domain your company has approved and verified. A person belongs to one company.
- People are invited by your company admins (an emailed link, single-use, good for 7 days), or register with an address at your domain and are approved by your admins.
- Authenticator first. For an account with an authenticator app (TOTP, RFC 6238), its code is asked for before the password, so a password leaked elsewhere cannot even be tried. Your company can require an authenticator for everyone. Ten single-use recovery codes are given once, and only their hashes kept.
- Passwords are at least 12 characters, with no composition rules or forced expiry (as NIST SP 800-63B advises), checked against known breached passwords without sending the password anywhere (k-anonymity), and stored with Argon2id.
- Lockouts: 5 wrong codes lock the account for 15 minutes, 10 wrong passwords for an hour, and the person is emailed. Sign-in attempts are also limited per address, and Cloudflare's bot check runs on the sign-in steps.
- Resets are by single-use emailed links (good for 1 hour), never by temporary passwords, and end every other session. A reset does not get round the authenticator.
- Single sign-on (Microsoft Entra ID and others) is planned, not yet available.
Sessions
- Sessions are kept on the server: a 256-bit random id, of which only a hash is stored, in a
__Host-cookie that is HttpOnly, Secure and SameSite=Strict. - They end after 12 hours without use, and after 7 days in any case; when the password, the person's roles or their authenticator change; and when they or an admin signs them out.
- People can see where they are signed in and sign out there. Company admins can sign anyone at the company out.
Roles
| Role | Can |
|---|---|
| Company admin | Everything at every site; people, roles, approved domains, the Claude connection, the subscription |
| Site admin | Everything at their site, including its people and settings |
| Engineer | Write and change the documents, registers and plugin records at their site |
| Viewer | Read their site's documents and registers |
Every request is checked for the person's company, site and role before anything is read, in one place for the whole application, denying by default. A site's id in a request must belong to the person's company and memberships.
The audit log
Your company admins see an audit log of sign-ins and failed attempts, authenticator changes, password resets, people and role changes, invitations, settings and Claude connection changes, plugin installs, exports and approvals. Each entry is chained to the one before by a hash, so an entry changed afterwards shows. It can be exported at any time.
Break-glass
So your company can always get back in, it has a break-glass account: its password is given to you once, sealed, for your safe; it needs an authenticator; and every use emails all your company admins and is flagged for review.
Our own administrators
- Platform administrators are separate accounts, not people of any company, and reach no company's content (see Your data).
- They sign in with an authenticator. From the internet they can sign in only through Cloudflare Access, as themselves (a request that came through Cloudflare otherwise cannot sign in as an administrator, or use an administrator's session).
- The server is administered over a private network (Tailscale), with SSH keys only: no passwords, no direct root sign-in. Today that is the owner alone.
- If we sign your people out during an incident, your company admins see it in your audit log.