Customize Email Sent from Experience Cloud Sites for Email Verification

Important System-generated emails from an unverified email-sending domain aren’t delivered, even if the From email address is verified. See Requirements to Send Email from Salesforce.

1. From Setup, in the Quick Find box, enter All Sites, and then select All Sites. Next to your site, click Workspaces.
2. Click Administration, and then select Emails.
3. Enter custom values for the email sender’s name and address to replace the default values.

   For security reasons, the sender's email must be verified to create a new site and to send welcome emails to new site members. If you change the sender’s email address, we send a verification email to the new address. The change is pending, and we continue to use the existing address while we await verification. The requested address doesn’t take effect until you click the confirmation link in the email. If verification is already pending for a new email address and you specify a different new address, we retain the latest value and use that value for verification.

   If you enter a custom value for the sender’s address and you have enabled mail relay, your Chatter emails use the relay.

4. Customize the content that appears in the footer of Chatter emails.

   Welcome emails contain login information for external members. If you don’t select this option, you must send username and password information directly to the user who’s registering for your site. All Chatter emails display the Chatter logo and Salesforce information by default unless you replace them with your logo and information. If you previously customized the logo or footer text and want to restore the default values, use the API to set these fields to null.

   1. To replace the default Chatter logo, choose a logo. The logo must be an existing document in the Documents tab and must be marked Externally Available Image. Images of 150 x 50 pixels on a transparent background work best.
   2. To replace the default footer text, enter up to 1,000 characters. The default text includes the Salesforce name and physical address. We recommend including your physical address to comply with applicable anti-spam laws.
5. To send email to users when they’re added to the site, select Send welcome email.

   Welcome emails contain login information for external members. If you don’t select this option, you must send username and password information directly to the user who’s registering for your site.

   Salesforce sends welcome emails when:

   • A site changes from Preview status to Active status. An inactive site doesn’t receive emails unless the associated org has a default portal or if the user’s profile is part of an active portal.
   • An admin adds a profile or permission set to an active site.
   • A user of an active site is assigned a profile or permission set.

   You can set the duration that the link provided in the welcome email is valid.

   1. From Setup, in the Quick Find box, enter Digital Experiences, and then click Digital Experiences | Settings.
   2. Change the link expiration duration under New User Email Settings and save your work.

   If a profile or permission set is part of multiple sites, users with that profile or permission set receive a welcome email from each site. The first email contains login credentials, but emails from subsequent sites simply contain a link to the site.

   

   Note The BCC compliance email setting isn't available for Experience Cloud site welcome emails.
6. To send email to users when they receive a one-time password, for One-Time Password, look up and select the email template, Communities: One-Time Password Email.

   This one-time password email message isn’t enabled by default. If you don’t select this option, Salesforce sends a generic message for identity verification.

   Salesforce sends one-time password verification emails to verify a user’s identity Salesforce also sends emails with one-time passwords for device activation when users log in from an unfamiliar browser, app, or IP address. This use case isn't covered by the One-Time Password email template. To customize emails sent for device activation, use the Device Activation Verification email template.

   • An external user attempts to log in to your site with an email address.
   • An external user attempts to register a mobile or U2F device.
   • An external user changes their email address.
7. To select an email template for Forgot Password, Change Password, Case Comment, User Lockout, One-Time Password, Old Email Address Change Verification, New Email Address Change Verification, Device Activation Verification, Self-Registration Micro-Batch Error, or One-Time Password For Headless Forgot Password Flow, click . Then select an email template from the list.
   

   Note Password reset links expire after 24 hours.

   You can customize the default email templates.

   

   Note When you customize the contents of a default email template, use the {!Community_Url} merge field to populate the URL for the current site. This field ensures that emails have the correct URL to direct users to the appropriate site. The {!Community_url} merge field isn’t available for the User Lockout template.
8. Save your changes.

Emails that are sent as a result of approvals and workflows, and changes to unscoped objects, like cases, are sent based on-site membership. For example, if a workflow triggers an email, all the recipients are grouped based on-site membership and then one email is sent to each group. If the user is a member of multiple active sites, the email comes from the oldest active site.

Note Objects that you can see whether you’re in a site or your internal Salesforce org are called unscoped objects. Unscoped objects include records like opportunities, accounts, cases, and the like.

Another way to customize site emails is to use these fields on the API Network object.

• CaseCommentEmailTemplateId—ID of the email template used when submitting a comment on a case.
• ChangePasswordEmailTemplateId—ID of the email template used when notifying users that their password has been reset.
• ChgEmailVerNewEmailTemplateId—ID of the email template used when notifying users that their email address has been changed. This template is sent to the new email address.
• ChgEmailVerOldEmailTemplateId—ID of the email template used when notifying users that their email address has been changed. This template is sent to the old email address.
• DeviceActEmailTemplateId—ID of the email template used when users log in from an unrecognized browser, app, or IP address. The email contains a one-time password that users enter to verify their identity.
• EmailFooterLogoId—ID of the Document object that displays as an image in the footer of the site Chatter emails.
• EmailFooterText—Text that displays in the footer of site Chatter emails.
• EmailSenderAddress—Read only. Email address from which site emails are sent.
• EmailSenderName—Name from which site emails are sent.
• ForgotPasswordEmailTemplateId—ID of the email template used when users forget their password.
• LockoutEmailTemplateId—ID of the email template used when users try to reset their password after locking themselves out of their site from too many login attempts.
• NewSenderAddress—Email address that has been entered as the new value for EmailSenderAddress but hasn’t been verified yet. After a user has requested to change the sender email address and has successfully responded to the verification email, the NewSenderAddress value overwrites the value in EmailSenderAddress. This value becomes the email address from which site emails are sent.
  • If verification is pending for a new email address, and you set NewSenderAddress to null, the verification request is canceled.
  • NewSenderAddress is automatically set to null after EmailSenderAddress has been set to the new verified address.
  • If verification is pending for a new email address, and you specify a different new address for this field, only the latest value is retained and used for verification.
• OptionsSendWelcomeEmail—Determines whether a welcome email is sent when a new user is added to the site.
• VerificationEmailTemplateId—ID of the email template used when users must verify their identity, for example, when they log in without a password or from a new device.
• WelcomeEmailTemplateId—ID of the email template used when sending welcome emails to new site members.