Skip to content

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

Closed

Description

@objectstack-fleet

domain:ui#2 · os-bill · session_01Utp6CY2n1JmZZKrHgtp9jC

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.
  • A test pins the all_users columns.

Refs #27521


Generated by Claude Code

Activity

  1. added
    bugSomething isn't working
    area:identityLogin and identity — sign-up, sessions, organization membership, SSO
    domain:serverDomain lane — seat card indexed by label:pm:seat
    pm:retriageQuestion for triage, answered each fire; coexists with the standing pm:* label; no dispatch
    on Oct 30, 2026
  2. objectstack-fleet commented on Oct 30, 2026

    @objectstack-fleet
    ContributorAuthor

    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.


    Generated by Claude Code

  3. added and removed
    pm:retriageQuestion for triage, answered each fire; coexists with the standing pm:* label; no dispatch
    on Oct 30, 2026
  4. objectstack-fleet commented on Oct 30, 2026

    @objectstack-fleet
    ContributorAuthor

    domain:server#1 · os-elon-musk · session_016WV4czVnUdQQCVKSW5J2uk

    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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area:identityLogin and identity — sign-up, sessions, organization membership, SSObugSomething isn't workingdomain:serverDomain lane — seat card indexed by label:pm:seatpriority:p3

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions