Notifications

What is configured where?

Email delivery, recipient selection, message content and scheduling are separate settings.

Changing a template does not enable a notification, add recipients or send an email. Likewise, creating a reminder definition does not activate reminders for every existing event.

Templates

Templates cover registration confirmations, waiting lists, attendance responses, invitations, cancellations, reminders, and notifications about new or edited events and venues.

Filter the list by language, workflow and recipient, then open the required variant. Each template has a required subject, a required plain-text body and an optional HTML body. The editor provides available variables and a preview with example data.

For example, Hello {user_name}, your booking for {event_title} is confirmed. becomes a personalised message using the actual booking and event information.

Customisations are saved separately by language and preserved during updates. Restore Default removes the customisation for the selected template and language. The original translated text is then used again.

Read the Notification Templates manual for the complete editing process, variable reference and practical examples.

Footer

Use the Footer tab for common information such as the organisation's name, contact email or site address. Select the language and choose whether the footer is included in user messages, administrator messages or both.

This avoids copying the same signature into every template. When enabled, the shared footer is added after the individual message body.

Thank you,
The {site_name} team
{site_url}
Contact: {contact_email}

Use the variables offered by the shared-content editor. Footer customisations are independent of individual templates and other languages.

Data Protection

The Data Protection tab contains the optional shared privacy notice. Configure the text, the privacy-policy URL and the recipient classes that should receive it.

The privacy notice follows the footer when both sections are enabled. For example:

This message relates to your activity on {site_name}.
Read our privacy policy: {privacy_url}

Adapt this text to the information your organisation needs to provide. Enabling the notice does not change booking permissions, consent settings or the notification retention period.

Reminders

Reminder definitions specify how long before an event a reminder should be sent. They can use minutes, hours, days or weeks.

1. Enable event reminders in JEM Settings → Notifications.
2. In Notifications → Reminders, create and publish a definition, such as 24 hours before.
3. Open an event and select the required reminder definitions in its Notifications section.
4. Check that the JEM Notifications Task is enabled and that Joomla Scheduled Tasks runs regularly.

Definitions marked as default are preselected for new events while reminders are enabled. They do not automatically change the reminder choices of existing events.

For example, a reminder set to 24 hours before an event on Saturday at 18:00 becomes due on Friday at 18:00, using the event's applicable time zone. The task must run for it to be processed.

Reminders depend on reservation and event eligibility. Open-date events cannot have a timed reminder, and a waiting-list place is not treated as a confirmed reservation. JEM checks whether a pending reminder is still relevant before delivery.

Read how the JEM Notifications Task processes reminders and retries.

History

The History tab records supported reservation notifications, their recipient, language, saved message and delivery attempts. Use it to investigate a missing confirmation or a failed delivery.

Retry or resend?

• Retry attempts delivery of the same saved message. It keeps the saved recipient and content.
• Resend creates a new linked notification using current reservation data and templates, when the workflow and permissions allow it.

Example: if the mail server was temporarily unavailable, fix the connection and retry the failed message. If the original message was sent but an authorised new copy needs current information, use the available resend action.

Editing a template does not rewrite stored messages. Automatic retries also retain their original content.

Viewing history and performing retry/resend actions have separate permissions. The available actions also depend on the message state and configured limits.

Recommended first setup

1. Confirm that Joomla can send a test email.
2. Enable the JEM Mailer plugin and select the required notifications and recipient groups.
3. Check the default templates before customising them.
4. Set up a shared footer and, if needed, a Data Protection notice.
5. Configure reminders and the scheduled task if your events need them.
6. On a test site, make a registration and create or edit a test event or venue. Check the resulting messages in the languages you use.

If Notifications is missing, check the JEM operating profile and user permissions. If messages are missing, check the Mailer recipient settings and Joomla mail configuration first. For queued messages and reminders, also check the scheduled task and notification history.

For notification settings and limits, see JEM Settings. For recipient selection and delivery format, see the JEM Mailer Plugin.