Accounts 1.0.0 frontend and @crosscode/ui
Sign-in steps (password, sign-up, email code, two-step sign-in and its setup with recovery codes, privacy notice, news question), forgot and reset password, the account page, admin (people, deletions, church profile, linked products, settings, notice, licence, audit) and setup. Strict CSP with a nonce per page; church colours from the profile. @crosscode/ui gets its first components (shell, card, fields, buttons). Plan: roles stay in each product (asked 2026-11-18). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -109,6 +109,17 @@ What Accounts holds (ROADMAP §3 "What lives where"):
|
||||
- The `crosscode.identity/1` method name is `totp`; Events 2.3 calls it `authenticator`. The 3.0
|
||||
migration maps it.
|
||||
|
||||
**Roles stay in each product** (ROADMAP §3; asked by Joshua 2026-11-18). Accounts knows who someone
|
||||
is, never what they may do in a product: its own `member` / `admin` are only about Accounts (who
|
||||
manages sign-in settings, people and the church profile). Cross Events keeps its `User` table with
|
||||
its four roles (`admin`, `supervisor`, `staff`, `user`), campus scopes and all its data; in 3.0 only
|
||||
the user's id becomes the account's `sub`. When someone signs in to Events through Accounts, Events
|
||||
finds its own user by `sub` and applies that role, as today; someone new to Events arrives as
|
||||
`user` and an Events admin promotes them there. The ID token carries no roles, so no product can
|
||||
give anyone a role in another. An Events admin isn't an Accounts admin (or the other way round)
|
||||
unless someone makes them one; the 3.0 migration asks which Events admins should also manage
|
||||
Accounts. Events still requires 2FA for its staff roles by sending `acr_values=mfa`.
|
||||
|
||||
## 3. OpenID Connect
|
||||
|
||||
- **`oidc-provider`** (panva, 9.x) on the backend, **`openid-client`** (6.x) in each product
|
||||
|
||||
Reference in New Issue
Block a user