Skip to main content

Membership Status and Portal Login Experience

This article explains how the system evaluates membership status and routes members accordingly when logging into the member portal.

Updated this week

When a member attempts to log in, the system evaluates all memberships associated with their account in a specific priority order to determine access and login experience.

First Check: Failed Memberships

If any membership has a Failed status, the member will be routed to the Failed Dues Paywall.

This screen informs members that their membership dues payment has failed. There is no grace period - members will see this paywall immediately upon login if any membership is in Failed status. This includes any add-on or secondary memberships associated with their CRM profile.

Payment Options on Failed Paywall

You have the option of whether members can pay their failed dues directly from this screen or not.

  • If enabled: Eligible members will see a "Pay Now" option to resolve their failed payment

  • If disabled: Members can view their failed status but cannot make a payment from this screen.

Please reach out to your Peoplevine point-of-contact to enable/disable this option.

Here is what the login screen looks like when the failed paywall is enabled (option to pay now):

Here is what the login screen looks like when the failed paywall is disabled (informational only):

Please note the failed paywall will populate with the email address listed under your Company Profile, under 'Contact & Social Information'.

Sub-members:

Payment must be handled by the primary account holder. Sub-members (non-primary account holders) will never see a payment option on the Failed paywall as they do not hold the subscription. Sub-members can view the failed status but cannot resolve payment from their account.

Global Network Members:

If failed payments in the portal is enabled, global members will only see the payment option for failed dues on their home house portal (property that holds the subscription). If a non-home house membership shows a Failed status, they'll see the failed paywall as informational only, without the ability to pay.

In the case where the Member App login page is tied to a specific property that is not their home house, the failed member must login into their Home House via Web to pay for the dues.

Second Check: Active Memberships

If the member has no Failed memberships and has at least one Active membership:

  • Login is allowed

  • The member is routed into the portal with full member access

  • For global members, the home house (property that holds the subscription) and membership configuration determine their default view and network access.

Third Check: Other Membership Statuses

If the member has no Failed memberships and no Active memberships, the member will be routed to a status-specific paywall. The system evaluates statuses in this order and displays the first match:

  1. Pending - Membership is awaiting approval

  2. Suspended - Membership has been temporarily suspended

  3. Canceled - Membership has been canceled

  4. Expired - Membership term has ended

Example: If a member has one Pending membership and one Expired membership, they will see the Pending paywall since it's evaluated first.

These paywalls are informational only and explain what the member needs to do next, such as waiting for approval, contacting your organization, or renewing their membership.

Key Takeaways

  • Failed status takes priority: Any failed membership will trigger the Failed Dues Paywall, regardless of other active memberships.

  • Active memberships grant access: At least one active membership must be present to allow portal access.

  • Status hierarchy matters: When multiple inactive statuses exist, the system follows a specific evaluation order. See order above, under Third Check.

Questions?

If you have questions about how this affects your specific membership configuration or need to adjust your Allow Failed Member Dues setting, please contact your Peoplevine Account Manager or the Support Team.

Did this answer your question?