Ensuring Salesforce Emails Send from Your Domain

Before you begin

• Ensure you’re using an email from your institution’s domain (e.g., @yourschool.edu)
• Avoid default @targetx.com addresses
• We recommend using a shared, role-based email address (for example, admissions@yourschool.edu) rather than an individual staff member’s account.

Step 1: Verify Organization-wide Email Addresses

These are the approved “From” addresses Salesforce can use.

1. Navigate to Setup and search for Organization-Wide Addresses.
2. Confirm you have emails with your domain listed.
3. Add a new email address if needed:
   
   1. Click Add.
   2. Enter email address.
   3. A verification link will be sent to this email inbox from Salesforce. Verify the address using this link.
   4. Confirm status shows Verified in your Salesforce org.

Step 2: Update Process Automation Settings

Automation (such as Salesforce Flow) relies on these defaults.

1. Navigate to Setup and search for Process Automation Settings.
2. Update the following locations:
   
   1. Default Workflow User 
   2. Automated Process User Email Address 

Step 3: Check Digital Experience (Community) Emails

This controls emails sent from portals (application site, appointment scheduler site, etc.). You will need to confirm this for each site.

1. Navigate to Setup and search for All Sites.
   
2. Select your Site → Workspace → Administration → Emails
3. Confirm the following:
   
   1. Email address uses your domain
   2. Email address exists in Organization-Wide Addresses
   3. Status is Verified
   4. Click Verify if needed
      

Step 4: Update Site (Guest User) Email Address

This setting routes emails sent by Site (Guest) users through a verified address, ensuring those messages are not blocked and delivered reliably.

1. Navigate to Setup and search for Sites.
2. Select your site (e.g., Event Site).
3. Click Public Access Settings.
4. Open the Guest User.
5. Confirm the following:
   
   1. Email address uses your domain
   2. Email address exists in Organization-Wide Addresses

Step 5: Review Additional Email Settings

Check these commonly overlooked areas:

Step 6: Review Flows Sending Emails

If you use Flows with email actions:

1. Check each Flow’s From Address
2. Ensure it uses a verified Organization-Wide Email

Step 7:Identify and Restart Scheduled Apex Jobs for DKIM Compliance

Scheduled Apex jobs must be restarted under a DKIM‑covered user to ensure outbound emails are properly authenticated and successfully delivered. Apex scheduled jobs that send outbound emails must run under a user whose email domain is included in the Salesforce DKIM configuration, as Salesforce applies DKIM signing based on the running user’s email domain and the “From” address. If a job is created or scheduled by a user with a non‑DKIM‑enabled domain, the resulting emails (e.g., Schedule Job reports, failures, or reminders) may fail DKIM/DMARC checks and be rejected, quarantined, or filtered as spam by recipient mail servers.

Step 8: Configure Email Authentication (DKIM or Domains)

Confirm that Salesforce is authorized to send emails from your domain. This must be configured in production and reconfigured in the sandbox after every refresh. TargetX recommends that you satisfy this requirement via DKIM keys. You may also do so via Authorized Email Domains.

Need Help?

If emails are still not sending after these updates, contact support or submit a case with details about where the email is triggered.