Members List
What the Screen Is For
Staff can explore a member list using questions, filters and saved views. The built screen reads generated records from the console’s server-side prototype store. It provides no live Membership read or write and does not enforce Membership permission keys.
What It Shows and Lets People Do
Results show identity, contact details, chapter, region, standing, tier, dates and balance, with configurable columns, sorting and paging. Ask converts text into filters through the built-in parser without a model call. Saved views support update, deletion and shared links. Selection supports prototype status changes, reminders and CSV export; changing status or sending reminders asks for confirmation only above one hundred selected records, while export requires no confirmation. The Add member button has no handler.
A connected implementation needs scoped membership reads and roster export operations. Prototype balance and direct bulk status changes have no equivalent Membership data contract. The validation references identify future integration obligations rather than checks enforced by this prototype.
States and Errors
LoadingLine indicates result refresh. Failed queries show an error and retry action, and empty results offer filter clearing. Action progress prevents repeated button activation and reports failures through notifications. No permission-driven read-only or inactive state is built into this page.
Patterns It Must Respect
The contract describes the existing PageHeader, RecordSearch, view and column menus, MembersTable, BulkActionBar and MembersPagination. Integration should preserve those built interactions while replacing prototype data and unsupported actions according to reviewed product decisions.