We believe we have most of the infrastructure in place for this project through MemberPress but the previous vendor was unable to figure out how to tie a single user ID login to multiple property IDs Lake association with a member login side for: • Invoicing members and sending reminders • Allowing members to claim their property IDs – a single login can manage multiple properties and initiate the claim process • Access to a member directory – viewable only to paid members • Updating their own information – members can edit their details and add family contacts that can be published in the directory or hidden but still used for communication via email or text • Communication with members via email or text Public side for: • Lake information (this is in place) • Advertising (this is in place) Area What we are looking for Core data model Properties exist as records whether paid or not Number of properties ~1,200 cabins in the database regardless of payment status User identity One login per person managing their details; the same user account can manage multiple property IDs Email requirement Single email per person; the same email may be used to manage multiple properties Unclaimed properties Properties can exist before being claimed Property claiming Members can claim a property via a secure verification flow Dues structure Currently $85 per property; support digital payments and manual check recording Multiple properties per owner One person can own/manage multiple properties via one login Captains / majors Assignments that can change independently via property ID Communications Email/SMS to members and any family contacts they choose to add Directory management Central directory driven by property records; directory is accessible only to paid members Admin workflow Admin can manage users and properties separately, and grant captains/majors access to relevant lists MemberPress role Handle auth, membership, and billing (payments per property) while property data is stored separately Claim verification Verification method (e.g., last name + parcel ID or other secure token) will be required for property claims Payment methods Support Stripe, PayPal, Apple/Google Pay; record manual check payments with admin approval Roles and permissions Define roles: Admin, Treasurer, Membership Chair, Beach Captain/Major, Member; ensure role assignments don’t affect property ownership Additional context: We believe most of the infrastructure needed for this project is already in place through MemberPress. However, the previous vendor did not successfully link a single user ID to multiple property IDs or allow the same email to manage multiple properties. The solution should address this limitation.