This page lists the emails MapleGather sends automatically when members join, pay, renew or lapse, what decides each one’s wording and timing today, and what the notes on the Lifecycle automations (at /admin/email/automation) page mean.
- Class: Transactional — always sends; members can’t opt out. The class applies to the automatic emails on this page. A broadcast, event follow-up or event cancellation notice with your own message always skips members who opted out, even when it uses a template marked Transactional. The post-migration claim-account email is the exception: it ignores opt-outs even when you write its wording (it still skips erased, archived, address-less and already-claimed members).
- Class: Marketing — only sends to members who haven’t opted out of the relevant marketing category.
- When it sends — the event that causes MapleGather to send this email.
- Wording comes from — what decides the email’s content at this release. Nothing on Lifecycle automations (at
/admin/email/automation) turns an automatic email on or off, and editing a template there changes only what that template says when something uses it.
| Automatic email |
Class |
When it sends |
Wording comes from |
| Application received |
Transactional |
Membership application submitted |
Built-in wording |
| Welcome |
Transactional |
Application accepted by an admin |
Built-in wording |
No email is sent when you decline an application.
| Automatic email |
Class |
When it sends |
Wording comes from |
| Payment or donation receipt |
Transactional |
Successful payment or donation recorded |
Your receipt template (billing), not an email template |
No failed-payment (dunning) email is sent yet.
| Automatic email |
Class |
When it sends |
Wording comes from |
| Renewal reminder |
Transactional |
Before a membership’s renewal date, on the level’s reminder schedule (your organization’s default cadence until the level’s own reminders are saved) |
Built-in wording — no screen chooses a reminder template yet. (A template a level names through the API is used while it’s active and transactional.) |
| Catch-up reminder |
Marketing |
When an admin sends catch-up reminders to members past their renewal date |
The template chosen for the catch-up send (it must be active) |
| Automatic email |
Class |
When it sends |
Wording comes from |
| Lapse notice |
Transactional |
Membership lapses |
Built-in wording |
| Cancellation notice |
Transactional |
Membership cancelled |
Built-in wording |
- Event emails follow each event’s own email rules and use built-in wording.
- Auto-renewal notices use built-in wording.
- Email-address confirmations and policy update notices use built-in wording.
Each template on Lifecycle automations (at /admin/email/automation) shows one of these notes under its name:
| Note |
Means |
| “Starter for broadcasts” |
A starting point for a broadcast you compose yourself. No automatic email uses it. |
| “Not used by any automatic email yet — a renewal reminder could use it, but no screen chooses a reminder template yet” |
An active transactional template. A renewal reminder could use it if a level named it, but no screen chooses a reminder template yet — so today no automatic email uses it. |
| “Not used by any automatic email yet” |
Any other template, such as a draft or a marketing template. Editing it doesn’t change any automatic email at this release. |
- Renewal reminder: There is no member control to turn renewal reminders off in the portal (Story 2.5.4). An unsubscribe recorded through the API or the catch-up email is honoured only while the level respects member preferences (the default). All other transactional emails send regardless of the member’s marketing preferences.
- Renewal reminder timing is set on your renewal settings and on each level’s Renewal reminders — see Configure auto-renewal, reminders, and catch-up. It isn’t set on the automation page.
- Copies of templates: a copy made with Fork this template keeps the original’s type and category and starts as a draft. A draft never sends.
- There’s no org-wide pause for automatic emails yet.
