Users
Every account is its own operation. Today there is exactly one — yours — because login is staged, not activated.
Current user
Washington
ownerReview mode — login stagedaixentium@gmail.com
Shops in this account
4
Approvals (pending / total)
40 / 40
Activity rows
5
Account since 2026-10-24 14:01:55. These counts are rows scoped to this account only — the same numbers nobody else's login will ever see.
How isolation works
- Every account is its own operation. Your shops, approvals, money, intel, agents, commands, and settings live under your account — and only yours.
- Every row is user-scoped. Each record in the database carries its owner's ID, and every screen query filters by it. There is no unscoped read path.
- Decisions are double-guarded. Approving or killing an item checks the account twice — in the request and again in the database write — so one account can never decide another account's queue.
- New accounts start empty. A family member who signs in gets a brand-new operation: no shops, no approvals, none of your data — their own team snapshot seeds their side, the same way yours did.
Family accounts
Family accounts arrive when login is activated. The Google sign-in flow is fully built and staged off on purpose — turning it on is the owner's ~5-minute job:
- In Google Cloud Console, create an OAuth client (Web application) and register the redirect URI
https://etsy.aixentium.com/api/auth/google/callback. - Set the credentials on the server —
GOOGLE_CLIENT_ID,GOOGLE_CLIENT_SECRET,SESSION_SECRET— and flipAUTH_ENABLED=true. - Restart the app. You sign in and match your existing operation by email; each family member who signs in gets their own empty, fully separate operation.
Until then, the OS runs in supervisor review mode and this page shows the one account that exists. No placeholder family members are listed — when they arrive, they arrive by signing in, not by being typed into a table.