This reference covers the email and communications settings available at both the account level (Global Options) and the event level (Event Info > Communications). These settings control how Forge sends transactional and marketing emails on behalf of your organization.
From Address and Sender Identity
| Setting | Where it lives | What it controls | Notes |
|---|---|---|---|
| From Name | Global Options > Email | The display name that appears in the email client as the sender | Example: 'Planner Conference Team' — keep it recognizable to avoid spam filters |
| From Email Address | Global Options > Email | The email address used in the From: header of all outgoing emails | Must be a verified domain in your email provider; unverified addresses will cause deliverability issues |
| Reply-To Address | Global Options > Email | Where replies are directed when a recipient clicks Reply in their email client | Can differ from the From address — useful for routing replies to a support inbox |
| Event From Name Override | Event Info > Communications | Overrides the account-level From Name for this specific event | Leave blank to use the account-level default |
| Event From Email Override | Event Info > Communications | Overrides the account-level From Email for this specific event | The override address must also be verified with your email provider |
Transactional Email Settings
| Setting | Where it lives | What it controls |
|---|---|---|
| Send Confirmation Email | Event Info > Communications | Master toggle — when off, no confirmation email is sent on registration |
| Confirmation Email Template | Event Info > Communications | The template used for the post-registration confirmation email for this event |
| Send Waitlist Email | Event Info > Communications | Sends a notification email when a registrant is added to the waitlist |
| Waitlist Email Template | Event Info > Communications | Template used for waitlist placement notifications |
| Send Cancellation Email | Event Info > Communications | Sends a notification when an attendee's registration is cancelled |
| Cancellation Email Template | Event Info > Communications | Template used for cancellation notifications |
| Send Reminder Email | Event Info > Communications | Enables scheduled reminder emails before the event |
| Reminder Days Before | Event Info > Communications | How many days before the event start the reminder is sent (e.g. 7, 3, 1) |
Before your event goes live, disable the Send Confirmation Email toggle to prevent test registrations from emailing real contacts. Re-enable it when you are ready to start accepting real registrations.
Email Provider Configuration
Forge's built-in email sending runs on SendGrid — there is no provider-choice setting; every tenant gets its own SendGrid subuser under Forge's parent account. Salesforce Marketing Cloud is not an alternative provider for this native sending path — it is a separate, opt-in routing bypass covered in Salesforce Triggered Sends below. Provider configuration, under Global Options > Email, covers:
- Sending domain and tracking domain, plus SPF/DKIM/DMARC verification status
- From name and From email address
- Dedicated IP pool assignment
- Suppression group used for unsubscribe/bounce handling
Emails sent from an unverified domain are far more likely to land in spam or be rejected by recipient mail servers. Set up SPF, DKIM, and DMARC DNS records for your sending domain before your first event. Your email provider's dashboard provides the exact records to add.
Salesforce Triggered Sends
Registration-triggered sends are fired from the Salesforce side rather than by Forge polling for changes. A Salesforce platform event (emitted on Attendee / Session Attendee status transitions) calls back to Forge's own registration-triggered-send endpoint, which then sends using Forge's native templates from its Postgres library — this is not an integration with Salesforce Marketing Cloud, and there is no separate SFMC template library or data extension involved.
| Setting | What it controls |
|---|---|
| Enable Salesforce Sync | Provisions the Salesforce-side metadata (endpoint URL, tenant ID, worker token) so Salesforce can call Forge when a registration changes |
| Registration-Triggered Sends (per event) | Enabled per event under Communications; determines which templates fire on which Attendee status transitions |
:::(Note) (Salesforce-side prerequisite)
Registration-triggered sends require the Salesforce-side platform event subscriber to be deployed and enabled in your org (deployable via the one-click "Enable Salesforce Sync" provisioning flow). Until enabled, registration changes in Salesforce do not fire Forge emails.
:::
Unsubscribe and Compliance
Forge automatically appends an unsubscribe link to all marketing emails. Transactional emails (confirmations, reminders) are exempt from unsubscribe requirements under CAN-SPAM and GDPR Article 6 lawful-basis processing, but Forge still provides an opt-out path for best practice.
| Setting | What it controls |
|---|---|
| Unsubscribe Page URL | The URL shown in the footer of every marketing email — defaults to Forge's built-in unsubscribe page |
| Suppression Group | The SendGrid suppression group (ASM group) that records unsubscribes and bounces for this tenant |
| Footer Content | Optional custom footer text appended to all outgoing emails — include your physical mailing address to comply with CAN-SPAM |