Considerations for Using Organization-Wide Email Addresses

Email Verification and Domain Ownership Verification

We recommend that all organization-wide email addresses use one of your verified email-sending domains. Salesforce can send email from an organization-wide address only when the email domain is verified or a deliverability setting is enabled. If the setting is enabled, Salesforce uses a substitute email address when an outgoing email includes an unverified email domain in the From header. See Requirements to Send Email from Salesforce and Send Email for Users with Unverified Domains.

In addition to domain-level verification, each organization-wide address requires verification. An admin verifies a new organization-wide address by clicking the link in the email sent after creating the address. Only verified organization-wide addresses are available to send email from Salesforce.

Naming and Uniqueness

Consider naming each organization-wide email address based on its specific purpose. Purpose-specific naming makes it easier to assign appropriate permissions and to understand how each address interacts with other features.

For example, you enable the Use a substitute email addess for unverified domains Deliverability option in Setup, and you want to specify the organization-wide address for Salesforce to use in the From header of those emails. To reduce the risk of impersonation fraud, you create an organization-wide address that indicates that the user isn’t verified. Your domain is example.com, so you create and verify the organization-wide address, unverified.email@example.com.

Tip If you decide to use a subdomain, such as email@unverified.example.com, for an organization-wide address, remember to verify the subdomain separately via a DKIM key or authorized email domain. Salesforce can send email from an organization-wide address only when the email-sending domain is verified.

Also review your organization-wide addresses and the email addresses for service features. If an organization-wide address with Allow All Profiles to Use this From Address enabled is used for another purpose, the organization-wide address settings can override feature-specific restrictions. For example, when the Email-to-Case routing address is also an organization-wide address with Allow All Profiles to Use this From Address enabled, all users can select the address as a From Address, regardless of the restrictions set for the Email-to-Case feature.

Limitations

You can’t use organization-wide email addresses in these contexts.

• Scheduled reports
• Scheduled 1:1 emails
• Scheduling dashboards for refresh
• Sending mail merge emails, mass emails, and meeting requests to contacts and leads

You can't delete or change an organization-wide address when an email alert uses the address.

If the sender's email address is an organization-wide address that isn't set for User Selection and Default No-Reply Address, the quick actions on Email.Message records are limited. The Reply, Reply All, and Forward standard quick actions don't appear on Email.Message records. Manage this setting in Organization-Wide Addresses in Setup.

Only One No-Reply Address

To configure a default No-Reply address, create a No-Reply organization-wide address or select No-Reply as the purpose on an existing organization-wide address. You activate the new No-Reply email address when you verify the new organization-wide address.

You can’t delete the active No-Reply organization-wide address, and only one verified No-Reply organization-wide address can be active at a time. To change the No-Reply address, follow the same process. Each time a new No-Reply organization-wide address is verified, it replaces the previously verified one.

Email Client Integration

You can use organization-wide addresses with Outlook© and Gmail™ integration. If a user's connected account or sender email address matches the organization-wide address, the organization-wide address takes precedence in the From: dropdown. The connected account or sender email addresses aren't available.

The verified organization-wide address is used as the From address in emails sent from the unauthenticated guest user record, such as emails sent from some custom flows. Outgoing emails are blocked when they're sent from an unverified address in the guest user record. Outgoing emails are also blocked when the organization-wide email address uses an unverified email domain.