Question

Difficulty: HardSalesforce Outlook and Gmail Integration with Email Templates

A Salesforce administrator is configuring email integration features and template access controls across various department units. Match each business requirement scenario with its appropriate Salesforce administrative setup or feature capability.

  • Restrict access to a specific folder of sales email templates so that only members of a designated Public Group can view and use them in Outlook or Gmail integrations.Enable Folders and Enhanced Sharing for Email Templates in Setup, and share the target email template folder with the Public Group.
  • Enable sales representatives to insert Lightning Email Templates in the integration panel that automatically populate merge data from related custom object fields.Configure Handlebars Merge Language (HML) fields within Lightning Email Templates accessible via the Integration Pane.
  • Allow service agents using Gmail Integration to send template-based emails that include persistent file attachments without re-uploading documents manually.Attach Salesforce Files directly to the Lightning Email Template record in the Files related list.
  • Grant power users the ability to build visually rich email templates using drag-and-drop component layouts without granting them full system administrator privileges.Assign a permission set containing the 'Access Email Template Builder' system permission.

Answer

Each scenario maps directly to its specific administrative feature: restricting template folder visibility to a Public Group requires enabling Folders and Enhanced Sharing for Email Templates; populating cross-object fields dynamically relies on Handlebars Merge Language (HML); incorporating automatic attachments requires attaching Salesforce Files directly to the template record; and delegating template design capability without administrative rights requires the Access Email Template Builder permission set.
The pairings correctly match each operational requirement with its Salesforce administrator feature: folder-level group restriction requires enhanced folder sharing; dynamic cross-object field insertion requires Handlebars Merge Language (HML); reusable email attachments require Salesforce Files attached to the template record; and visual template creation rights require the Access Email Template Builder permission.

Step-by-Step Solution

1
Analyze the folder access requirement for Public Groups.
Determined that standard email sharing lacks Public Group folder controls until Folders and Enhanced Sharing for Email Templates is enabled.
Enhanced sharing extends folder-level permissions (View/Edit) to Public Groups and Roles.
2
Analyze the requirement for dynamic field merge across standard and custom objects in integration panes.
Identified Handlebars Merge Language (HML) in Lightning Email Templates.
HML supports rich field substitution across parent and related records in modern Salesforce email templates.
3
Analyze the requirement for pre-attached files when inserting templates from Gmail/Outlook panes.
Identified attaching Salesforce Files directly to the Lightning Email Template record.
Lightning Email Templates automatically link attached Salesforce Files when the template is selected in an integration.
4
Analyze permission requirements for drag-and-drop template builder tool access.
Identified the 'Access Email Template Builder' permission set assignment.
This permission explicitly grants access to the visual builder interface without requiring system administration rights such as 'Customize Application'.

Key Concept

Salesforce Integration Pane & Lightning Email Template Administration
Rate this question