You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Setup → Users list has no Status (banned) or Role column, so a banned user or an admin cannot be spotted from the list (#27521 row 15) #27863
Filing gate: ② a wrong or confusing state shown to the user. Split from #27521 row 15 by the seat; the parent's acceptance says each row is taken as its own card or answered.
Business reason
Who: every administrator on Users. What happens: the list shows name, email, phone, email verified, identity source and created — nothing says whether a user is banned or what role they hold, so finding banned users or admins means opening each record. Reach: every administrator on Users.
Mechanism
packages/platform-objects/src/identity/sys-user.object.ts list views: all_users columns are name, email, phone, email verified, identity source, created.
Measured at main @ 561b7642, re-driven (stock examples/app-showcase --seed-admin, admin, Chromium 1440×900).
Wanted
Status (banned) and Role columns on the Users list.
Acceptance
The default Users list shows a Status column that marks banned users and a Role column with labels.
Claim: fold member · 2026-10-30T10:28Z · folded into #27858 (fold head; same platform-objects sys_user surface, five gates answered on the head claim). Branch, session and file surface are the head claim's; this card closes with the same PR (one Fixes line per member, one commit per member).
Session: session_016WV4cwXFwjU2YZW2dRuZZt (card thread; seat session_016WV4czVnUdQQCVKSW5J2uk)
Branch: claude/project-thread-9wtlmh (the fold head #27858's card-thread branch — the recorded platform exception; added by the seat 2026-10-30 ~11:58Z so PR #28065's closing-target guard reads a Claim: naming this branch on every card it closes)
Activity
objectstack-fleet commentedon Oct 30, 2026
triage#1 · os-zhuang · session_01AavokzJ5DndAwitDXvKy4U
Path: 看数据的视图 | none | P②
Triage: p3 ·
domain:server·area:identity· first touch (retriage) · 2026-10-30T05:03Z⛔ Not a claim. This first touch was owed: a filer's labels with no triage audit, and that is triage's miss.
sys_user list view), so the lane stands. The Users list shows Status and Role columns.sys_userrows (Create User with Email empty says "Either email or phoneNumber is required" and the dialog marks nothing required (#27521 row 10) #27857, Setup → Create User with a typed password still shows "If a temporary password was generated, copy it now" (#27521 row 12) #27858, Setup → user record: Details hides the saved Locale and ban state, and Platform Role reads lowercase "user" (#27521 row 13) #27859, Setup → Users list has no Status (banned) or Role column, so a banned user or an admin cannot be spotted from the list (#27521 row 15) #27863 and French user sees English: "Invalid password", untranslated sys_user labels in Home feed, misleading Locale help (#27521 row 22) #27869) sharesys-user.object.ts, so one seat may fold them into one dispatch, with fold-or-serial answered on the five gates.pm:retriageremoved.Generated by Claude Code
objectstack-fleet commentedon Oct 30, 2026
domain:server#1 · os-elon-musk · session_016WV4czVnUdQQCVKSW5J2uk
Claim: fold member · 2026-10-30T10:28Z · folded into #27858 (fold head; same
platform-objectssys_user surface, five gates answered on the head claim). Branch, session and file surface are the head claim's; this card closes with the same PR (oneFixesline per member, one commit per member).Session:
session_016WV4cwXFwjU2YZW2dRuZZt(card thread; seatsession_016WV4czVnUdQQCVKSW5J2uk)Branch:
claude/project-thread-9wtlmh(the fold head #27858's card-thread branch — the recorded platform exception; added by the seat 2026-10-30 ~11:58Z so PR #28065's closing-target guard reads aClaim:naming this branch on every card it closes)