/tenants/modules/emails) and requires ADMIN_TENANT; communication managers
(COMMUNICATION_TENANT) can also open the Emails page and change wording. The
delivery log and the lists sit in the Administration area instead.
The three surfaces
Campaigns you write and send yourself are a separate feature: see
Newsletter.
Who the email comes from
Three things decide what a recipient sees in their inbox. From name is always your organisation’s name as it appears in Organisation info. From address is your organisation’s contact email, but only once that address has been verified for sending. Until then Orgo sends fromno-reply@orgo.space.
Verification is done by Orgo rather than in the settings screen, because it
requires DNS records on your domain: ask support to verify the address you want to
send from.
Reply-To is always your contact email, verified or not. So even on a brand new
organisation, a member who hits reply reaches you rather than a dead no-reply
mailbox.
Change the contact email at Settings → Organisation → Contact email.
Changing it to an unverified address moves the From address back to
no-reply@orgo.space until the new one is verified.What language an email is written in
Automatic emails are written in your organisation’s default interface language, not the recipient’s. Email is available in English, Romanian, German, Bulgarian, Lithuanian, Spanish, French, Italian, Dutch, Ukrainian and Portuguese: if your default language is anything else, emails fall back to English. Wording you change yourself is saved for the language you wrote it in, and every recipient gets that version. If you change the organisation’s default language later, the built-in wording in the new language applies until you edit the email again. The invoice email and the PDF attached to it are the exception: they follow your organisation’s default language across all 14 interface languages, and fall back to English only when the default is not one of them. See Email templates for what you can rewrite, and Languages for the interface language setting itself.How a message actually gets sent
1
Something happens
A member registers, a fee approaches its renewal date, a ticket is paid for.
Each of these has one email type attached to it.
2
The switch is checked
If that email is switched off on the Emails page, nothing is sent and
nothing is logged as sent. Sign-in and security emails, the newsletter signup
confirmation and workflow emails ignore this check and always send.
3
The wording is resolved
The built-in email in your organisation’s language, with any texts and subject
you changed in place of the defaults.
4
Placeholders are filled in
Names, dates, amounts, links. See the
placeholder reference.
5
It is queued or sent immediately
Login codes, verification codes, password emails, registration confirmations
and admin-created account emails are sent on the spot so a failure surfaces
right away. Everything else is queued and sent by a background worker.
6
It is written to the log
With the rendered body, so you can see exactly what the recipient got. Codes
are the exception: login and multi-factor codes are not logged at all, and the
other one-time codes are logged with the code removed and no body stored.
Deliverability
A few things Orgo does for you, and one it cannot:- Emails sent through the template system carry a plain text version alongside the HTML, which mailbox providers (Microsoft in particular) treat as a quality signal.
- Notification and campaign email carries a
List-Unsubscribeheader, so the unsubscribe button in Gmail and Apple Mail works without the recipient opening the message. Campaign email additionally supports RFC 8058 one-click unsubscribe. - Addresses that were minted during a data import for people who had no email of their own are recognised and skipped rather than bounced. A member with one of these will simply never receive email until you give them a real address.
- If you run a custom domain, the setup asks you to
publish DKIM keys plus an MX and a TXT record on
bounce.<your domain>. Those last two put the envelope sender on your own domain, so SPF passes and aligns with the address recipients see instead of resolving to Amazon. Mail sends either way, but a domain missing them authenticates on DKIM alone. - Orgo cannot fix your domain’s reputation. The DMARC policy on your domain, and the SPF record on your apex covering everything else you send from it, are still yours to maintain.
Troubleshooting
A member says they never got an email
A member says they never got an email
Start at Email logs and search for them. The log
answers whether Orgo sent it, to which address, and what it said. If there is
no row at all, check first whether that email is one Orgo logs: waitlist
messages and family invitations are never written to the log. Otherwise the
email was either switched off on the Emails page or the triggering action
did not happen.
Emails arrive from no-reply@orgo.space instead of us
Emails arrive from no-reply@orgo.space instead of us
Your contact email has not been verified for sending yet. Replies still reach
your contact address. Ask support to verify the address.
An email is in the wrong language
An email is in the wrong language
Automatic email follows the organisation’s default language, falling back to
English for a language email does not cover. A member’s own interface language
does not change it. Invoice emails are the exception and cover all 14
languages.
We want to stop one specific reminder without stopping the rest
We want to stop one specific reminder without stopping the rest
Find it on the Emails page and turn off the switch on its row. Every email
has its own switch; Turn all off on a section is only a shortcut.
Related
- System emails - the catalogue of automatic emails, what triggers each, and which can be switched off
- Email templates - previewing an email, changing its wording, and the placeholder list
- Email logs - what was sent, to whom, and what it said
- Newsletter - campaigns you compose and send yourself
- Notifications - in-app and push delivery, and per-member preferences