No "Add Member" button. Intake is via (A) the Prospects pipeline (Add Prospect / invite / approve application) or (B) self-service /register. The seeded pending@demo.membervu.com (Miguel) is an APPLIED prospect with member status GUEST_ATTENDEE; the seeded guest@demo.membervu.com (Roberto) has role GUEST but member status ACTIVE.
Test Cases
TC-REG-01: Self-Service Registration
Step
Action
Expected Result
1
Open /register (incognito).
Core fields: First Name*, Last Name*, Email*, Phone (international, optional), Address, LinkedIn, Other socials. No password field at the form.
2
Fill the fields (use an intl phone) and click "Create account".
Success: "Check your email — verification link sent". Phone is persisted (#182). Status depends on tenant config: PENDING_APPROVAL / PENDING_PAYMENT / ACTIVE.
As ADMIN, go to Member Settings → Fields (/admin/members/settings?tab=fields). For a native field (company/profession) or a custom field, toggle "Show at registration" (and optionally "Required at registration").
Config saved. (>3 required fields shows a completion-rate warning.)
2
Reload /register.
An "Additional information" section now renders the configured field(s), in the configured order; required ones block submit until filled.
TC-REG-03: Invitation Flow
Step
Action
Expected Result
1
As ADMIN/MEMBERSHIP_MANAGER, from Prospects, invite an eligible prospect.
Invitation email sent (POST /api/membership/invitations).
2
Open the invite link (/register?token=…).
Heading becomes "Accept Your Invitation"; email is pre-filled + locked. Submitting consumes the token.