Approved Email as Document Overview
Approved Email as Document Model leverages the native content capabilities of the Vault Platform for Approved Email content within Vault CRM. This feature transitions from the legacy object model to a standard Vault Document and Binder architecture. By storing Approved Email templates, fragments, and template fragments as documents, customers can leverage core Vault platform capabilities, including lifecycles and robust security controls.
Not all features are available on all platforms. For a list of available platforms for each feature, see Platform Functionality.
Users and Roles
With Approved Email, the following users are able to perform the following tasks:
Content Creators
- Using HTML, CSS, and a set of Veeva-provided tokens, create reusable, compelling, and compliant content for end users to send to recipients
Content Admin Users
- Using Vault's approval process with Vault CRM functionality, manage the readiness of Approved Email content and control which end users have access to the content
- Test staged content in Vault CRM using the same flow as an end user to ensure content functions correctly
- Track activity tied to an Approved Email, for example, opens, click-throughs, and content views, and use that information to optimize content
- The Content Admin performs the following tasks:
- Creates product records
- Uploads Email Templates, Email Fragments and Template Fragments to Vault CRM as Documents
- Starts and participates in Vault content approval process
- Tests and validates Approved Email content
- Manages end user access to content
- Creates and views Approved Email Reports and Dashboards
Integration Users
- Support the MC Services that process various Approved Email functionality
End Users
- Compose Approved Emails using pre-approved and compliant content
- Selects recipients and sends Approved Emails to HCPs
- Depending on the content and organization, may also have the ability to customize content to best suit each relationship
