Managing Approved Email Content

Once Approved Email content is written and uploaded to Vault, content admins in both Vault and CRM can perform the following tasks to manage content:

Testing Staged Approved Email Content – Content admins can test content with a status of Staged by sending the email to any email address
Previewing Rendered Approved Email Content – Users in Lightning Ready orgs can preview rendered Approved Documents or sent emails directly within CRM

Matching Products for Approved Email Content – Content must be associated to a product in Vault, and a corresponding product must exist in CRM
Using Detail Groups in PromoMats / MedComms – When using Detail Groups in a CRM org, they must also be enabled in Vault
Aligning Approved Email Content to Users – Content admins can implement layers of control to refine the content available to end users
Defining the Language of Approved Email Content – The language attributes on the Approved_Document_vod and Account_vod objects can be used to filter recipients for selected content, as well as filter which content is available for selection
Customizing Email Header Behavior – Each email template can be configured to have a unique from, reply-to, and sending domain header

Filtering Approved Email Fragments – Content admins can enable additional filters when selecting a fragment to add to an Approved Email, enabling end users to more easily find and select content
Setting Consent at the Email Template Level – Content admins can control whether consent needs to be checked when using specific templates
Restricted Words in Approved Email – Content admins can specify a list of words that, if entered, prevent end users from sending the email
Restricting Email Fragments – This link leads to the Vault Online Help. Content admins in Vault can restrict fragments added to a template based on the template's stated product or by a defined relationship between the template and the fragment.