Newsletter

Purpose

Sends email newsletters to your member and prospect lists. Newsletter Settings holds the configuration (sender, branding, lists). The Newsletter dashboard (under Website) holds the campaign editor itself.

When to use this

First-time setup of sender identity and template colours.
Adjusting audience lists (members, prospects, society organisers).
Reviewing send history.

Key fields (Newsletter Settings)

Enabled — master switch.
Sender name — appears in the "From" field (e.g. "Cathkin Braes Golf Club").
Sender email — must be on a verified domain (see AWS SES Settings or Email Hosting).
Reply-to email — where replies land.
Template — MJML template controlling header, footer, and brand styling.
Audience segmentation rules — define which member attributes go to which list.
Automation rules — e.g. "send the latest blog post on Friday at 09:00 to All Members".
Unsubscribe URL — auto-generated; do not change.

Common tasks

First-time setup

Verify your sending domain in AWS Settings or Email Hosting.
Settings > Newsletter Settings > Sender name, Sender email, Reply-to.
Save.

Build a campaign

Website > Newsletter, New Campaign.
Pick the audience list.
Compose in the editor (MJML-based, drag-and-drop).
Preview sends a test to your own email.
Schedule picks a send time, or Send now.

Add subscribers

Website > Newsletter > Subscribers, Import CSV or add manually.
Each subscriber has an email, name, and optional segmentation tags.

Gotchas

Sender domain must be verified before you can send anything. Unverified domains return SES errors silently in the background.
MJML is opinionated — custom HTML pasted in may render inconsistently across Outlook/Gmail. Stick to the provided blocks.
Unsubscribes are honoured globally — once a subscriber unsubscribes, they're suppressed across all lists for this tenant.
Scheduled sends are queued — once scheduled, edits to the campaign aren't picked up. Cancel and re-schedule if you need to change content.
Don't import a marketing list you didn't earn consent for. SES will throttle and eventually block the sender domain.