Renewal settings reference
This page describes every setting on the Auto-renewal & reminder settings page in MapleGather, found at Memberships > Settings > Auto-renewal.
Signup auto-renewal
Section titled “Signup auto-renewal”These settings control auto-renewal for people applying to join.
| Setting | What it does | Notes |
|---|---|---|
| Offer auto-renewal on new levels by default | Sets whether new levels start with Offer auto-renewal at signup turned on. | Doesn’t change existing levels and doesn’t turn auto-renewal on for anyone — applicants always choose. Each level can be changed on its own settings. |
| Require a second confirmation before auto-renewal starts | Applicants who choose auto-renewal see how much they’ll be charged, how often, and on which payment method, together with your disclosure terms, and must confirm again. | Turn this on where your jurisdiction requires it. Requires Disclosure terms. |
| Disclosure terms | The published membership-terms version whose text applicants see on the confirmation step. | Shown while the second confirmation is on. Only current, published, organization-wide membership terms can be chosen — publish them under Settings > Policies first. Saving without one shows an error. Publishing a new version asks applicants who haven’t been accepted yet to confirm again. |
Dunning & retry posture
Section titled “Dunning & retry posture”These settings control how a failed auto-renewal charge will be retried.
Not available yet: automatic retries. MapleGather saves these retry settings, but it doesn’t yet run any automatic retries of a failed renewal charge — the renewal-charge and retry engine isn’t built at this release (see How auto-renewal and the renewal lifecycle work). The values you save here take effect once retries ship. Until then, members renew from their My membership page when reminded.
| Setting | What it does | Notes |
|---|---|---|
| Retry failed renewal charges automatically | Turns automatic retries of a failed auto-renewal charge on or off. | Saved now; retries aren’t run yet (see the note above). |
| Maximum retry attempts | How many times a failed renewal charge will be retried. | 1 to 8. |
| Retry window | The number of days the retries will be spread over. | 1 to 60 days. You can’t set the day of each individual retry. |
Org-default reminder cadence
Section titled “Org-default reminder cadence”This section configures when renewal reminder emails go out to members. A level uses this cadence until its own reminders are saved on the level’s Renewal reminders page; from then on it uses its own schedule.
| Setting | What it does | Notes |
|---|---|---|
| Reminder offsets | A list of how many days before each member’s renewal date a reminder goes out (for example, 30, 7, 1). Zero means on the renewal date. | MapleGather sends reminders in its daily membership run: each member gets at most one per run (the closest one that’s due) and never the same offset twice for the same renewal date. An offset of 0 goes out in the last daily run before the renewal date — the same send point as 1 day before, so having both sends one reminder in the final day. Each offset is 0 to 365 days before — reminders after the renewal date can’t be set. There’s no separate template per offset here, and no screen chooses a reminder template — reminders use built-in wording. (A level can name a template for each reminder only through the API; it’s used only when active and transactional.) |
| Use recommended defaults | Appears when the offset list is empty. Pre-fills three offsets: 30 days before, 7 days before, and 1 day before the renewal date. |
Duplicate offset: adding the same offset twice is blocked with an error. Each offset must be unique.
More than 6 offsets: a non-blocking advisory message warns that members may unsubscribe from too-frequent reminders.
More than 12 offsets: refused — a cadence holds at most 12 distinct offsets.
Unsubscribed members: a member who unsubscribed from renewal reminders doesn’t get them while the level respects member preferences (the default). Every reminder ends with a line saying renewal reminders are part of the membership and are sent while it’s active, with a link to the member’s email preferences for their other email.
Lifetime levels: renewal reminders never fire for Lifetime-level members, regardless of this setting.
Catch-up past-due reminders
Section titled “Catch-up past-due reminders”This one-time action sends a reminder to members who are past their renewal date (for example, after a launch or data migration). Members who got a catch-up reminder in the last 30 days are skipped.
| Setting | What it does | Notes |
|---|---|---|
| Preview catch-up list | Shows a sample of up to 5 members who will receive the catch-up reminder (email and days past due), plus how many more. | The section shows how many past-due members will get the reminder and how many will be skipped before you send. |
| Send catch-up reminders | Sends the catch-up template to all eligible past-due members. Opens a confirmation dialog before sending. | Members who opted out of email (or of marketing email), unsubscribed from renewal reminders, have no email address, or got a catch-up reminder in the last 30 days are automatically skipped. Sending is queued; a message confirms how many members the reminders are on their way to. Catch-up reminders count against your organization’s email sending capacity like other email: if a send would go over it, the batch finishes as Partial and only part of it goes out — see Email reached sending capacity. Catch-up reminders are marketing email, so they can’t be sent until your organization’s postal address is saved (Add your organization’s postal address). |