Skip to main content
The email log answers one question well: did we send it, and what did it say. Most email the platform sends is recorded with its recipient, subject, time and, where available, the exact rendered body. Two gaps are worth knowing before you rely on the log as proof: notification email (discussions, comments, mentions, events, votes) is logged as Transactional email with the subject only and no body; and a handful of emails are produced outside the logging path and leave no row at all, among them the fee payment approval, the newsletter signup confirmation, waitlist messages, family invitations, the vote seal and the discussion digest. Built for whoever fields “I never got the renewal reminder”. Replaces taking the member’s word for it, or your own. The log is at Administration → Email logs (/email-log) and needs ADMIN_TENANT. It is also embedded in two places where you are more likely to want it: a member profile has a Logs tab with an Email Logs view, and a contact record shows an Email logs card. Email logs list with a recipient search box and a table of ID, sent date, member, subject and type

​
Reading the list

Newest first, twenty per page. Each row shows: Search by recipient at the top finds a member or contact and filters the list to them. ID, sent date and type are sortable.

​
Reading one entry

Opening an entry shows the recipient, the subject, the sent date, the type, and Email Preview: the message body exactly as it was rendered for that person, with their name, dates and links already substituted. Rows tagged Transactional email that came from a notification (a discussion, comment, mention, event or vote alert) store the subject only, so their preview is empty. Everything else stores the full body. Email log entry showing recipient, subject, sent date and type cards above a rendered preview of the email body This is the part that settles arguments. If a member says the payment link did not work, you can see the link that was in their copy.

​
Answering “the member never got it”

1

Find them in the log

Search by recipient, or open their profile and use the Logs tab. Working from the profile is usually faster and avoids picking the wrong person.
2

No row at all?

Usually Orgo did not send it: either the email is switched off (check Emails Config) or the thing that triggers it did not happen. Check first that the email is one Orgo logs. Waitlist messages, family invitations, the fee payment approval, the newsletter signup confirmation and the discussion digest are never written to the log, so their absence here is normal.
3

A row exists?

Orgo handed it to the mail service. Check the address on the row: an old address, a typo, or a placeholder address left by a data import all produce a row that was never going to arrive. If a whole day’s mail is missing for everybody rather than for one member, it is not the address: tell Orgo support, because the row records the handover and not the delivery.
4

Right address, still missing?

It is a delivery problem, not an Orgo problem. Ask them to check spam and quarantine, and check whether their employer’s mail filter is involved.
5

Subject starts with FAILED?

The message was queued but could not be delivered after repeated attempts, and the entry records why instead of the body. Usually the address is invalid.

​
What the log does not tell you

The log is a record of sending, not of delivery. It has no opened, clicked, bounced or delivered status. Those exist only for newsletter campaigns, where they are shown as campaign statistics: see Newsletter. Two more gaps worth knowing:
  • Login and multi-factor codes are not logged. Nothing at all is written for them. Other one-time codes (email verification, password reset, password change, email change, event app sign-in) do get a row, but with the code removed from the subject and no body stored, so nobody with access to the log can use it to get into a member’s account.
  • Deleting a member deletes their email history. Log entries are attached to the member or contact record and go with it. Export anything you need to keep before deleting an account.

​
Newsletters in the log

Campaign sends appear here too, one entry per recipient, tagged as Newsletter and linked to the campaign that produced them. So a member who says they received a campaign they should not have appears in the log with the campaign named.

​
Retention

Orgo does not expire log entries on a schedule: they stay until the person they belong to is deleted. On a large organisation the log grows to millions of rows, which is why it always opens filtered to a page rather than counted in full.
The log stores the full body of most emails, which means it holds personal data: names, addresses, amounts, membership dates. It is restricted to ADMIN_TENANT for that reason. Take that into account in your data retention policy.