Approved Email Entry Points
- Document Model
There are multiple ways to send an Approved Email. Having multiple Approved Email entry points enhances flexibility, efficiency, and accessibility for users across different workflows. End users can send an approved email directly from a call report, while an Engage Meeting host may find it easier to send an approved email directly from a meeting. Each type of user can select the entry point most suited to their day-to-day work.
Multiple entry points reduce navigation steps, allowing users to send emails seamlessly during customer interactions. Entry points ensure that users can send emails in the right context, leading to better engagement with HCPs.
Some of these entry points are enabled by default, some require module-specific configuration.
Who can use this feature?
- End Users — Browser, iPad, iPhone, Windows Users
- Using Default Entry Points
- Users require an Approved Email license
Configuring Approved Email Entry Points for
Configuring Additional Entry Points
The following Approved Email entry points require additional configuration and their respective modules to be enabled before they can be used by end users:
- Consent Confirmation - End users can send consent confirmation emails to HCPs when using double opt-in or when capturing consent using confirmation emails for any channel
- Engage Meeting Invitations – Hosts of Engage meetings can use Approved Emails to send invitations to recipients
- Order Management - End users can send order receipts using Approved Email
- Sample Management - End users can send Approved Email receipts for signature transactions
- Surveys – Surveys can be sent to survey participants using Approved Email
- Suggestions – Suggestions can be sent as Approved Emails when the email_template__v checkbox is selected on the suggestion__v record (iPad only)
Disabling Entry Points
Admins may want to disable certain entry points for Approved Email. To disable an entry point:
- Navigate to the Disabled Approved Email Entry Points Approved Email setting.
-
Enter the appropriate values using the format EntryPoint1;;EntryPoint2:
-
Account_vod - Disables sending an approved email from the Account Detail page
-
MyAccounts_vod - Disables sending an approved email from the account list
-
Call_vod - Disables sending an approved email from a call
For example, Account_vod;;MyAccounts_vod
These values do not follow the formatting for Vault CRM objects because they are hard-coded and not mapped to specific data model API names.
-
To disable exactly two entry points:
- Create a Veeva Message containing the two entry points. For example:
- Message Name = DISABLED_APPROVED_EMAIL_ENTRYPOINTS
- Category = ApprovedEmail
- Text = Account_vod;;MyAccounts_vod
- Navigate to the Disabled Approved Email Entry Points Approved Email setting.
- Enter the Veeva Message. For example, the following references the Veeva Message from Step 1 above: DISABLED_APPROVED_EMAIL_ENTRYPOINTS;;ApprovedEmail.
Using Default Entry Points as
The following Approved Email entry points do not require additional configuration:
- Account Detail Page – End users can select the Send Email button in the All Actions menu of an account detail page to begin composing an email with the selected account populated as the recipient
- Account List – End users can select one or more accounts using the Select button, then select the Send Email button in the All Actions menu to begin composing an email with the selected accounts populated as recipients
- Call Report – When viewing a call report, end users can select the Send Email button in the All Actions menu to begin composing an email with the attendees of the call selected as recipients.
Ensure the more_actions__v object control is added to the call2__v layout for the All Actions button to display.
- X-Pages – For X-Pages authored prior to the implementation of Approved Email for Document model that pre-select content, content creators must adhere to the following guidelines:
- Query the Email Template or Email Fragment document within Vault CRM to retrieve the id field on the Document record in Vault CRM
- Pass that Vault CRM document ID in the template and/or fragments parameters.

