Differences

This shows you the differences between two versions of the page.

--- software:membership_validation [2024/06/13 00:21] – [Income based rate field not set for AMP membership] smartin015
+++ software:membership_validation [2024/06/13 00:49] (current) – [Membership Validation] smartin015
@@ Line 6: / Line 6: @@
 See [[https://github.com/protohaven/protohaven_api/blob/main/protohaven_api/commands/finances.py|protohaven_api/commands/finances.py]] in the [[https://github.com/protohaven/protohaven_api|protohaven_api GitHub repository]] for more details on the validation process.
+Validation also runs when users sign in via email at the front desk; feedback is also sent to #membership-automation in Discord.
 The following sections describe each validation error in detail, along with steps to remedy the problem.
+===== Sign in ... returned multiple accounts in Neon with same email =====
+When a member signs in at the front desk, the sign-in webapp checks Neon CRM to understand the state of their membership. We use the email address of members as a unique identifier for their sign-in and in various supporting systems.
+However, Neon really enjoys creating accounts - signing up for classes and events can often create duplicate Neon accounts with the same identifying features (first/last name, email address, phone number etc.) These duplicate accounts are *usually* deduplicated automatically, but sometimes they can linger and cause ambiguity in understanding the state of someone's membership or clearances.
+This validation error occurs when multiple accounts in Neon share the same email address, and requires the following steps to fix:
+  - Log in to Neon CRM, and use the top bar to search for the duplicate accounts with the same email address.
+  - Observe which accounts share the email address.
+If the accounts belong to multiple individuals (e.g. a company email shared across employees), we will need more information to deduplicate them:
+  - Reach out to them to explain the situation and ask for unique emails for their accounts.
+  - Once the emails are known, navigate to each account in turn, click Edit on the top right, overwrite their "Email Address 1" field, and click Save on the top right.
+  - Follow up with the members, letting them know to use the updated email addresses to sign in at the front desk.
+If the accounts all belong to the same individual, we can deduplicate them easily:
+  - Click through to any of the accounts in Neon
+  - Click the ellipses "..." on the top right, then Find Duplicate
+  - If no duplicates are found, click "Change Match Criteria" on the top right and tweak it until it finds the duplicate account.
+  - Click "Compare Accounts", then select the destination account to merge into. If you're not sure, pick the account with a lesser ID number
+  - Continue through the guided merge flow until the accounts have been merged.
+===== ...signed in at the front desk but has a non-Active membership status in Neon =====
+When entering Protohaven, all members must sign in via the kiosk at the front desk. When they do so, their Neon account is checked for an active membership. This error indicates that their membership is not currently active.
+  - The membership could have recently expired, either by choice or due to failure to charge the card on file
+  - The member might have entered the wrong email for the Neon account they're attempting to use
+  - Their membership may have been revoked (either due to exiting a program where membership is provided, or due to suspension from too many policy violations)
+In any case, we need to understand what the situation is:
+  - Browse to the account in Neon CRM and click on the Memberships button on the left.
+  - Check their membership history to see whether their membership was recently ended.
+  - Email the member and share context on the state of their membership - remind them that they must have an active membership to operate tools and equipment in the workshop, and ask whether they'd like to make changes to their membership or leave it as inactive.
+  - Assist the member in updating their membership, or make a note if they no longer wish to be a member (see the "Notes" button on the top right of the About page for the account in Neon).
 ===== Abnormal zero-cost membership =====
@@ Line 87: / Line 128: @@
   - When this information is received, open the user's account in Neon CRM and upload it under "Proof of Income" (look for the MEMBERSHIP QUALIFIERS section of the account details).
   - Then click the Edit button on the top right, select the relevant Income Based Rate value (e.g. "Low Income - 20%"), and click the Save button at the top right of the page.
-  - Ensure the active membership matches the Income Based Rate value, or else you'll soon see a validation issue
+  - Ensure the active membership matches the Income Based Rate value, or else you'll soon see the "mismatched income based rate" validation error (as below).
 ===== Mismatch between income based rate (X) and membership type Y =====
+Members that qualify for AMP have their Income Based Rate field set to a specific category, e.g. "Low Income - 20%" (indicating a 20% discount on membership). This value is independent of their active membership, which could potentially even be a General membership.
+This validation error indicates that the AMP member is not receiving the correct membership for their category. To resolve:
+  - Navigate to the account in Neon CRM and observe the set Income Based Rate value.
+  - Click the Memberships button (on the left), then click on the active membership (title in blue)
+  - Click the Edit button next to Membership Info
+  - Under Membership Term, select the blank entry at the top. Then click it again and select the closest match to the member's current membership (e.g. Weekend Membership - LI if they are listed as Low Income and currently have a Weekend membership of a different type)
+  - Click on Save Changes at the bottom.
+  - Reach out to the member (via email) and let them know that their membership has been adjusted to match the AMP information that we have on file.