EDITIONS Available in: • Enterprise • Performance • Unlimited • Developer USER PERMISSIONS To create, customize, or activate a community:
• “Create and Set Up Communities” AND Is a member of the community whose Community Management page they’re trying to access. You can customize email sender information, Chatter email branding, and templates in your
community emails. You can perform customizations in either the user interface or the Network object in Salesforce APIs.
1. Access Community Management in either of the following ways:
• From the community, click in the global header.
• From Setup, click Customize > Communities > All Communities, then click Manage next to the community name.
2. Click Administration > Emails.
3. Enter custom values for the email sender’s name and address to replace the default values.
Note: 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 for verification.
If you enter a custom value for the sender’s address and you have enabled mail relay, your Chatter emails will use the relay.
4. Customize what displays in the footer of Chatter emails.
Important: Both a logo and email footer text are required. Keep in mind that:
• All Chatter emails display the Chatter logo and Salesforce information by default unless you replace them with your organization’s own 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.
a. Choose a logo to replace the default Chatter logo.
The logo must be an existing document in the Documents tab and must be marked Externally Available Image. Images with a maximum size of 150 x 50 pixels on a transparent background work best.
b. Enter custom text to replace the default footer text, up to a maximum of 1,000 characters.
The default text includes Salesforce’s name and physical address. We strongly recommend including your organization’s physical address to comply with applicable anti-spam laws.
5. Select Send welcome email to send email to users when they’re added to the community.
Important: Welcome emails contain login information for external members. If you don’t select this option, you’ll have to manually send external members their usernames and passwords.
The link provided in the welcome email is valid for 6 months. Welcome emails are sent when:
Customizing Communities Email Set Up Your First Community
• A community changes from Preview status to Active status. Emails are not sent when a community is in Preview or Inactive status.
• An administrator adds a new profile or permission set to a Activecommunity.
• A user is assigned a profile or permission set that is part of a Activecommunity.
Note: If a profile or permission set is part of multiple communities, users with that profile or permission set receive a welcome email from each community. The first email contains login credentials, but emails from subsequent communities simply contain a link to the community.
6. Use the default email templates or use the lookups to select different templates for welcome emails to new community members, forgotten password emails, and notification emails about reset passwords. If your organization uses email templates to submit case comments, you can select a template (none is provided by default).
You can customize any default template.
Note: If you customize the contents of an email template, we recommend that you use the {!Community_Url} merge field. This custom merge field populates the unique URL for a community, ensuring that emails to users contain URLs with the correct parameters and direct users to the appropriate community to log in or change a password.
7. Click Save.
Another way to customize community 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 a user that their password has been reset.
• EmailFooterLogoId—ID of the Document object that displays as an image in the footer of community Chatter emails.
• EmailFooterText—Text that displays in the footer of community Chatter emails.
• EmailSenderAddress—Read only. Email address from which community emails are sent.
• EmailSenderName—Name from which community emails are sent.
• ForgotPasswordEmailTemplateId—ID of the email template used when a user forgets their password.
• NewSenderAddress—Email address that has been entered as the new value for EmailSenderAddress but has not 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 becomes the email address from which community emails are sent.
– If verification is pending for a new email address and you set NewSenderAddress to null, this cancels the verification request.
– 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 community.
• WelcomeEmailTemplateId—ID of the email template used when sending welcome emails to new community members.
Customizing Communities Email Set Up Your First Community