Reference
Email and Communications Settings Reference
Email in Forge is controlled in three places. Admin > Email sets the organization's sender, domain, suppression, and logging. The event's Communications tab (Notifications, Compose, Scheduled, History) sets which emails each event sends and from which address. Each email template can carry its own subject, preheader, From, and Reply-to. This page explains what each setting does and what to choose. For the account-level screens in full detail, see Admin > Email Settings.
Which setting wins
| Layer | Where | What it controls | Recommendation |
|---|---|---|---|
| Organization | Admin > Email | Default From name and address, sending domain, additional senders, suppression, preference categories, pause switches, Salesforce logging, CC master switch. | Finish this first. Nothing sends reliably until a sender exists and the sending domain is verified. |
| Event | Event > Communications > Notifications | Which automatic emails are on for this event, which template each uses, the event's sender, and the event's CC setting. | Set per event. Use it to change the sender or templates for one event without touching the others. |
| Template | Communications > Templates | Subject, preheader, From (Default or Custom address), Reply-to, and folder for one template. | Leave From on Default (tenant settings) unless a specific template must come from a different address. |
| One send | Compose > Audience / Review & Send | The From address for that single send, plus audience and timing. | Pick the sender you want on step 1; confirm it on Review & Send. |
Fast setup for a new event: confirm Admin > Email says You're ready to send, open the event's Communications > Notifications, pick a sender (a SendGrid sender you added but have not confirmed shows as Awaiting confirmation until you click the link in SendGrid's email), turn on Registration confirmation with a template, and send a test from the template.
Organization settings in short
| Setting | Where | What it controls | Recommendation |
|---|---|---|---|
| From Email and From Name | Admin > Email | The default sender shown on every email unless a template, event, or send overrides it. | Use a monitored address on your own domain and a name people recognize. |
| Sending domain and tracking domain | Admin > Email | Domain verification so inbox providers trust your mail, and branded links for open and click tracking. | Verify a dedicated subdomain before your first event. Until it is verified, bulk sends are blocked and test sends use a fallback sender. |
| Additional senders | Admin > Email | Extra From addresses your team can pick when sending, each Verified, Pending, or Revoked. | Add one per team that sends, for example Sponsors or Attendee Support. |
| Suppression list and preference categories | Admin > Email | Addresses that never receive email and the categories recipients can opt in or out of. | Keep transactional mail such as confirmations out of optional categories. |
| Pause all sending | Admin > Email > Advanced | Emergency stop. While it is on, sends are skipped, not held, and they are not sent when you resume. | Use only when something is wrong, such as the wrong template going out. |
| Salesforce activity logging | Admin > Email > Advanced | Whether each email is also recorded in Salesforce as a Task, an Email Message, or both. | Leave Tasks on; add Email Messages only if your team needs the full message in Salesforce. |
| CC additional emails (master) | Admin > CC Email Settings | Copies extra Salesforce email fields (for example an assistant's address) on attendee emails. | Turn on only when second recipients are required, then decide per event. |
| Daily sending limit | Built in | Each organization can send up to 100,000 emails per day. A send that would exceed the remaining allowance is refused. | Schedule very large campaigns across days. |
Event Communications tabs
| Tab | What it is for |
|---|---|
| Notifications | Automatic emails triggered by registration activity, the event sender, and the CC setting. Changes here save automatically; there is no Save button, and a status line shows Saving, Saved at a time, or an error. |
| Compose | Write and send an email to an audience now or on a schedule (see Sending Emails). |
| Scheduled | Sends that are queued, running, or paused, with Pause and Resume. |
| History | Past sends with delivery status, run history, and a per-recipient delivery log. |
Report, Inbox (two-way SMS), and Automations tabs are not shown by default. Email results for an event are under Manage > Reports > Email.
Notifications tab settings
| Setting | What it does | Values | Recommendation |
|---|---|---|---|
| Sender defaults (Sender) | The From address used for the triggers on this tab, chosen from your verified Forge senders. If you have none, a link to Admin > Email explains how to add one. | A verified sender. | Choose a verified sender. A trigger cannot be switched on until a From address exists, either here or as the organization default. |
| CC additional attendee emails for this event | Whether the extra email fields chosen in Admin > CC Email Settings are copied on this event's attendee emails. | Inherit tenant setting, On, Off. | Leave on Inherit unless this event differs. Choose On only if the organization master switch is also on and the extra fields are filled in. |
| Trigger toggle | Turns one automatic email on or off. It stays disabled until a template is chosen. | Enabled, Disabled. | Choose the template first, then switch it on. Switching off is always allowed. |
| Template picker | Search and choose the template the trigger sends. Edit template and New template open the template editor. Remove deletes the trigger setup. | A template from your library. | Use one template per trigger. For registration confirmation only templates that contain the Attendee Link merge field are listed; a note shows how many were hidden. |
Triggers
Seven triggers are available. The first four are shown as featured cards at the top of the tab; all seven appear in the full list below.
| Trigger | Fires when | Template needs | Recommendation |
|---|---|---|---|
| Registration confirmation | Right away when someone registers and their registration becomes Registered from a non-waitlist status. | The Attendee Link merge field ({{AttendeeLink}} or {{conference360__AttendeeLink__c}}). Saving fails without it. | Turn this on for every event. If no registration confirmation is enabled the tab warns that nothing is sent when someone registers. |
| Waitlist Confirmation (Waitlisted) | When someone is placed on the waitlist (Registered to Waitlisted). | None. | Use for waitlist events so people know they are on the list. |
| Spot Available Notification (Waitlist released) | When a waitlisted attendee gets a spot and is registered (Waitlist to Registered). | None. | Tell them what to do next and how long they have, if you set a time limit. |
| Day-Of Welcome Message | On the morning of the event with agenda and links. | None. | Use for in-person logistics or the join link. |
| Cancellation | When a registration is canceled, declined, or rejected. | None. | Send one clear notice with refund information. |
| Attendance update | When the attendance status changes to any non-blank value, such as checked in. | None. | Use for a thank-you on check-in; avoid noisy status changes. |
| Receipt | Once per invoice when the Bill To email is filled in and the related transaction is completed. | None. | Use for payment receipts. |
Registration-triggered emails start from Salesforce: a platform event on Attendee and Session Attendee status changes calls Forge, carrying record IDs only. Until an admin chooses Enable Salesforce Sync (on Home or Org Settings), registration confirmations do not send and the tab says so. Confirm with a real test registration.
Enabling a trigger also creates a stub record of the template in Salesforce so the event can reference it; the template content stays in Forge.
Waitlist pickers in Event Configuration
Event Configuration > Most used has two more waitlist email pickers (Email when status is Waitlist-Pending, Email when status is Pending). They use Salesforce email templates and are part of the Salesforce-side waitlist automation, separate from the Forge triggers above. They send automatically only while Automated waitlist emails is On. Use the Forge triggers for new events unless your team relies on Salesforce templates.
Delivery readiness
The Communications page checks that mail can actually be delivered. Warnings you may see:
- Email settings have not been configured: complete Admin > Email.
- No verified sender: finish Single Sender verification or domain authentication in Admin > Email before sending.
- Sending domain is not verified: bulk sends are blocked until DNS records pass verification; test sends use a fallback sender in the meantime.
- Email service is not configured: ask your administrator to add the email API key in the server environment.
- No From address selected for this event: choose one when you set up the email or under Sender defaults.
Compliance and unsubscribe
- Forge adds an Unsubscribe link to the bottom of every email sent from Communications that does not already have one, and sets the one-click unsubscribe header. To control where the link appears, add the Unsubscribe and Manage Preferences links yourself: both are merge tokens ({{UNSUBSCRIBE_LINK}}, {{MANAGE_PREFERENCES_LINK}}) and special links in the email builder.
- Suppressed, bounced, and unsubscribed addresses are excluded when a send runs. The send confirmation shows how many were excluded, and warns when more than one in four addresses is inactive.
- Recipients you de-select in the audience step are excluded from that send.
- Keep promotional content out of confirmations and other transactional emails, and keep those emails out of optional preference categories.