Back to the Knowledge Base

Knowledge Base Article

How to Suspend a Membership

Suspending a membership puts it on a temporary hold without ending it, so the member is expected to return.

When to suspend

Suspension fits a temporary hold: a member's request (illness, travel, hardship), a disciplinary pause, or a payment issue to resolve before reinstatement, when the member will likely come back.

Suspend a member

  1. Open the member record and go to Member Details, then find the Suspension section near the bottom.
  2. Set Is Suspended? to Yes.
  3. Enter a Suspension Start Date (required; it defaults to today) and, if known, a Suspension End Date.
  4. Choose a Suspension Reason.
  5. Click Save All Changes & Continue or Save All Changes & Exit.

The suspension panel on Member Details with Is Suspended, Suspension Reason, Suspension Start Date, Suspension End Date, Inactive Date, and Inactive Reason

The suspension fields stay greyed out until Is Suspended is set to Yes.

The Save All Changes and Continue, Save All Changes and Exit, Delete This Record, and Cancel and Exit buttons

Nothing is recorded until you save.

Suspended vs. Inactive

These are different states. Suspended is a temporary pause with the member expected to return. Inactive means the membership has ended because they did not renew or chose to leave, which you set with the Active Status field along with an Inactive Date and reason.

The Active Status, Membership Status Code, and Ambassador Referred By fields on Member Details

Active Status is the field that makes a membership Inactive, not the suspension switch.

End a suspension

  1. Open the member record and set Is Suspended? back to No.
  2. Update the term and renewal dates if the pause affected their membership period.
  3. Save.
  4. The membership date fields including Membership Term Start Date, Membership Term End Date, and Renewal Date

    These are the dates to push out if the pause moved their membership period.

Reconnecting…

Whoops!

You've Encountered An Error

Something went wrong on our end. Don't worry, our development team has already been notified, and we'll get it fixed as soon as we can.

Please avoid repeating the same action for now. A quick reload usually gets you going again.