Sending Approved Emails to BCC Recipients
BCC recipients of emails do not display to other recipients. End users can use the BCC field on an Approved Email to add any recipients who should receive the email without displaying to standard recipients. Any valid email address can be a BCC recipient and does not need to correspond to an account in Vault CRM. This enables end users to send Approved Emails to BCC recipients not in Vault CRM and have those emails display to BCC recipients exactly as they would display to standard recipients. Approved Email end users may wish to receive the email exactly as it is sent to the primary recipients and so include themselves as a BCC recipient. Other customers may require end users include a dedicated compliance team as a BCC recipient for auditing purposes.
BCC recipients receive the same content as standard recipients, including:
- Links to Vault documents
- Links containing merge tokens
Who can use this feature?
- Browser, iPad, iPhone Users
- Users require an Approved Email license
- Integration Users, Content Admin Users, End Users
Configuring BCC Recipients for

To configure this feature:
- Grant Edit field permission to the bcc__v field on the approved_document__v object.
- Add the bcc__v field on the page layouts for corresponding object types of the Sent_Email__v object.
- Grant access to the bcc__v field on the Email Template Document Type in PromoMats/MedComms.
- Refresh the Vault - Vault CRM Mapping on the Approved Email Administration page.

To configure BCC recipients, grant Edit field permission to the bcc__v field on the approved_document__v object.

To allow end users to add BCC recipients to an email, perform the following optional configurations. Without these configurations, any default BCC recipients configured by content admins are added to the message, but users cannot specify additional BCC recipients.
- Grant Edit field permission to the bcc__v field on the approved_document__v object.
- Grant Edit field permission to the bcc__von the sent_email__v object.
- Add the bcc__v field to the layout for corresponding record types of the sent_email__v object.
Using BCC Recipients as

When composing an Approved Email, end users can select the BCC field and manually enter any valid email address as a BCC recipient. Since BCC recipients do not need to be associated with an account, end users cannot search for accounts using the BCC field like they can on the standard recipients field.
If an email address is added to both the From and BCC fields, for example, if the user tries to BCC themselves, the BCC recipient may not receive the email. This is because some email systems automatically filter out messages were the sender and recipient addresses match.
When end users enter a BCC email address with valid syntax, the address becomes a pill. If the syntax is invalid, an error message displays.
When the email is sent, all BCC recipients display in the bcc__v and email_config_values__v fields on the corresponding sent_email__v record.
Opened, Clicked, Bounced, and Dropped activities by BCC recipients are not tracked. Vault activities by BCC recipients, for example Viewed and Downloaded, are tracked under the Sent Email as if they were a standard recipient.
Approved Email does not check for consent or perform any other validations for BCC recipients.
Setting Default BCCs as

Content admins can define default BCCs to associate with an Approved Email template, simplifying the composition process if there are known BCCs that should always be included when sending that template.
To define default BCCs for a template:
- Navigate to the template in PromoMats/MedComms.
- Edit the template.
-
Enter a comma-separated list of email addresses in the bcc_v field. Entered BCC recipients can be plain-text, configuration tokens, or a combination of both.
For example: compliance@verteobiopharma.com, {{userEmailAddress}}, legal@verteobiopharma.com, {{User.Email}}
When a template with default BCCs is sent, the content admin-defined BCCs display in the email_config_values__v field on the corresponding sent_email__v record.
Entered BCC recipients do not display to end users in the Approved Email UI.
Considerations
This feature is not supported in Approved Emails sent through Events Management.