droboticflow/docs/project-member-display.md

1.6 KiB

Project member display

Project membership reads now return userName, userEmail, and userStatus (active, disabled, or missing) alongside the existing fields. These are response-only fields; membership storage and mutation contracts are unchanged.

The API first applies existing organization/project and supplier visibility, then performs one organization-scoped batch lookup for the visible user IDs. Mongo projects only ID, name, email, and status. Passwords and account settings are neither loaded by that lookup nor returned. Missing or cross-tenant user references return empty display fields and missing; disabled identities retain their name with an explicit status.

The member table, name search and role editor use this response directly. The add-member candidate directory is independent and cannot change table names. Loading and errors are explicit, with a retry button. Switching projects clears selection/editor state and ignores late responses from the previous project.

Validation:

  • go test ./internal/api ./internal/store -run 'TestProjectMember|TestSupplierManagerMaintains|TestProjectSupplier' -count=1
  • npm run lint:web and npm run build:web
  • node tests/browser/project-members-display.mjs (Vite on 127.0.0.1:5174; installed Chrome via Playwright; isolated GET fixtures)
  • Full frontend suite: 571 pass, 10 pre-existing failures, identical to the unmodified 883f47ff baseline.
  • TestProjectMemberDisplayLiveFixture is opt-in. It creates only its own test organization/accounts and supports disabling those accounts after live QA. It does not modify customer identities or task assignments.