To enable users to send emails on behalf of a team or department, instead of using
their individual email addresses, set up an organization-wide email address. Specify which user
profiles or permission sets can use each address, and select one organization-wide address as
your no-reply email address. With the required permissions, both users and system-generated
emails can use an organization-wide address to send email from Salesforce.
Required Editions
When sending email from Salesforce, users with these profiles can select their own email
address or the organization-wide email address for the email From field.
Replies are delivered to the selected address.
You can also set up a special purpose organization-wide email address for Salesforce to use
when no reply is expected. Users can’t select this No-Reply email address.
Other features use organization-wide email addresses to send system-generated email or, in
the case of unverified email domains, to send email on behalf of the user.
Available in: Lightning Experience and Salesforce Classic
Available in: All Editions
Example
Your org has several users assigned to a Support Profile. This profile
is associated with an email address called support@acme.com and a
Display Name of Acme Support. When these users
send an outbound email through Salesforce, they can choose to have their
From email address appear as support@acme.com
instead of their own Salesforce email address.
The highlighted sections in the following image
represents the changes to the From address and Display
Name that the recipient of an email might see.
Set Up Organization-Wide Email Addresses You can define and manage organization-wide email addresses for each permission set or user profile. When sending email from Salesforce, users with these permission sets or profiles can select their own address or the organization-wide address for the email From address. Replies are delivered to the selected address.
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.