Skip to main content
System emails are the messages Orgo sends on its own: nobody presses send. This page lists them, says what makes each one go out, and shows which you can turn off. Built for admins who need to know exactly what their members are receiving. Replaces guessing from the support inbox. The switches live at Settings → Notifications & Email Campaign → Emails Config (/tenants/modules/emails/system-emails) and need ADMIN_TENANT. Changes save as you flip them. Emails Config screen with the module menu on the left and grouped switches for User Lifecycle, Membership and Fees, and the start of Adhesion or Applications, with the remaining categories below the fold

​
How the switches work

A category switch on the Emails Config screen covers a group of related emails: turning off Membership Renewal Reminders silences all fourteen reminders, personal and company. A per-email switch sits in the header of each card in Email Templates and beats the category switch in both directions, so you can leave the reminder category on and silence only the 30-days-after one. A switched-off email is not sent and no log row is written. Nothing queues up for later.
Login codes, verification codes, multi-factor codes, password emails and email-change confirmations always send. They have no switch, by design: a member locked out of their account is not a preference.

​
Members and accounts

​
Sign-in and security

None of these can be switched off or edited. Seven of them are refused by the platform outright if anyone tries to save a template for them; the event app code has no card on the Email Templates screen and renders from the built-in template like the rest. Login and multi-factor codes are never written to the log. The other code-carrying messages (email verification, password reset, password change, email change and the event app code) do get a row, but with the code stripped from the subject and no body stored, so an admin reading the log cannot lift a live code and take over an account. The two messages here that carry no code, Password changed and Email change request, are logged in full like any other email.

​
Membership and fees

The renewal ladder runs once a day at 18:00 UTC and picks one message per member based on how far the renewal date is away. All fourteen (seven here, seven for companies) sit under the Membership Renewal Reminders switch. Company memberships have their own ladder at 18:30 UTC, addressed to the company’s contact email, with the primary contacts and any additional addresses in copy. When the company has no contact email, the first primary contact becomes the recipient instead. A company with neither is skipped and nothing is sent. See Renewals for what a member experiences when a fee lapses, and Invoices for invoice delivery.

​
Events

​
Applications, identity and documents

​
Subscriptions and payments

​
Community, local centres and everything else

​
Digests

Three summary emails run on a schedule instead of reacting to one event. An unread discussion notification is what triggers the digest, but the email carries the member’s ten most recent unread notifications whatever their type, so events, mentions and votes they have switched off individually still surface here. Members choose Instant, Daily or Weekly in their own notification preferences, or switch discussion email off entirely.
Discussion email follows each member’s notification preference rather than the Discussion Notifications switch on the Emails Config screen. To reduce discussion email across the organisation, change the default in Notification Preferences instead. See Notifications.