Salesforce Dictionary - Free Salesforce GlossarySalesforce Dictionary
Full Organization-Wide Address entry
How-to guide

Set up an Organization-Wide Address

Setting up an Org-Wide Address involves DNS verification, profile restriction, and downstream send-path configuration. The steps below cover the full setup.

By Dipojjal Chakrabarti · Founder & Editor, Salesforce DictionaryLast updated May 19, 2026

Setting up an Org-Wide Address involves DNS verification, profile restriction, and downstream send-path configuration. The steps below cover the full setup.

  1. Identify the address and owner

    Decide which shared address to add (billing@, support@, hello@). Confirm someone monitors the inbox to receive verification mail.

  2. Configure DNS for the domain

    Set up SPF authorizing Salesforce. Configure DKIM signing through Setup > DKIM Keys. Without proper DNS, sends are flagged.

  3. Open Organization-Wide Addresses

    Setup > Email > Organization-Wide Addresses. The page lists current addresses.

  4. Add the address

    Click Add. Enter Display Name, Email Address, optional Reply-To. Choose Allowed Profiles. Save.

  5. Verify through the link

    Salesforce sends a verification email. Someone with inbox access clicks the link. The address becomes available for use.

  6. Test from a profile-allowed user

    Log in as a user with allowed profile. Open the email composer. Confirm the address appears in the From dropdown. Send a test mail to an external address you control.

  7. Configure downstream paths

    For Email Alerts using this address, edit the alert to select Org-Wide Address as From. For Apex sends, set setOrgWideEmailAddressId on Messaging.SingleEmailMessage.

Key options
Display Nameremember

Friendly name shown to recipients. Distinct from email address.

Email Addressremember

The actual sending address. Must be verified.

Allowed Profilesremember

Profiles whose users can select this address.

Reply-Toremember

Optional different address for replies.

Special Purposeremember

Use for system-generated mail like password resets.

Gotchas
  • Verification email goes to the proposed address. Ensure inbox is monitored before adding.
  • Without SPF and DKIM, sends may be flagged as spoofed. Configure DNS before relying on the address.
  • Restricting profiles is per address. Users with disallowed profiles do not see the address in the composer.
  • Org-Wide Address sends still respect Email Delivery Settings access level. Sandbox refresh resets to System Email Only; address sends will fail until reset.
  • Reply-To redirects replies away from sender mailbox. Use deliberately; accidental Reply-To breaks customer reply flows.

See the full Organization-Wide Address entry

Organization-Wide Address includes the definition, worked example, deep dive, related terms, and a quiz.