Source: https://vaultcrmhelp.veeva.com/doc/Content/CRM_topics/Multichannel/ConsentCapture/IntegrateFunct/AEConsent.htm

## Capturing Consent for Approved Email

Customers can replace the email opt-in functionality for Approved Email with Consent Capture. Email opt-in captures global opt-in consent while Consent Capture allows users to capture both opt-in and opt-out consent from HCPs at different levels (for example, for specific products or content types) and for different channels (for example, CLM or custom channels). Email opt-in and Consent Capture cannot be used simultaneously.

**Who can use this feature?**

* Approved Email Integration Users - Browser
* [Sync content types for Approved Email](#Syncing)
* Business Admin Users - Browser
* [Set up consent for Approved Email](#Setup)
* End Users - Browser, iPad, iPhone, Windows
* [Capture consent for Approved Email](#CCforAE)
* Users require an Approved Email license

### Configuring Consent Capture for Approved Email for

[![Closed](../../../../../Skins/Default/Stylesheets/Images/transparent.gif)Approved Email Integration Users](#)

To configure this feature:

1. Ensure [Configuring Consent Capture](../CCConfiguration.htm) is complete.
2. Navigate to **Admin > Users & Groups > Permission Sets**.
3. Select the appropriate permission set.
4. Select the **Objects** tab.
5. Grant the following permissions and place the fields on the appropriate layouts for all object types:

   | Objects | Object Permission | Object Types | Fields | Field Permission |
   | --- | --- | --- | --- | --- |
   | consent\_header\_\_v | RE | n/a | approved\_email\_consent\_level\_\_v | Edit |
   | sent\_email\_\_v | RE | n/a | content\_type\_\_v | Edit |

[![Closed](../../../../../Skins/Default/Stylesheets/Images/transparent.gif)Business Admin Users](#)

To configure this feature:

1. Ensure [Configuring Consent Capture](../CCConfiguration.htm) is complete.
2. Navigate to **Admin > Users & Groups > Permission Sets**.
3. Select the appropriate permission set.
4. Select the **Objects** tab.
5. Grant the following permissions:

   | Objects | Object Permission | Object Types | Fields | Field Permission |
   | --- | --- | --- | --- | --- |
   | consent\_header\_\_v | RE | n/a | approved\_email\_consent\_level\_\_v | Edit |
   | sent\_email\_\_v | RE | n/a | content\_type\_\_v | Edit |

[![Closed](../../../../../Skins/Default/Stylesheets/Images/transparent.gif)End Users](#)

To configure this feature:

1. Ensure [Configuring Consent Capture](../CCConfiguration.htm) is complete.
2. Navigate to **Admin > Users & Groups > Permission Sets**.
3. Select the appropriate permission set.
4. Select the **Objects** tab.
5. Grant the following permissions:

   | Objects | Object Permission | Object Types | Fields | Field Permission |
   | --- | --- | --- | --- | --- |
   | consent\_header\_\_v | R | n/a | approved\_email\_consent\_level\_\_v | Read |
   | sent\_email\_\_v | R | n/a | content\_type\_\_v | Read |
6. Navigate to **Business Admin > Objects > Approved Email Settings > Global Approved Email Settings** and populate the **Approved Email Consent Mode** Approved Email setting with a value of 1 to hide the Email Opt In button on mobile devices.

### Syncing Content Types for Approved Email as

[![Closed](../../../../../Skins/Default/Stylesheets/Images/transparent.gif)Approved Email Integration Users](#)

Content types are customer-defined categories of information not related to products, for example, Medical or Promotional. Customers create Approved Email templates for content types in PromoMats/MedComms and Approved Email integration users sync the templates to Vault CRM. In order for a sync to be successful, the following conditions must be satisfied:

* Corresponding content\_type\_\_v records with the same external ID exist in both Vault CRM and PromoMats/MedComms
* The CRM-Vault Mapping from the Approved Email Administration page is updated
* Select View Map under the Vault Login Credential Management section of the Approved Email Administration page
* approved\_document\_\_v records include a content\_type\_\_v record in PromoMats/MedComms
* Only one content type can be assigned to an email template in PromoMats/MedComms
* End user visibility to email templates is still controlled by the product catalog (My Setup)
* Corresponding content\_type\_\_v records need to be managed in Vault CRM and PromoMats/MedComms. See [Content Type Object and Document Field](https://commercial.veevavault.help/en/gr/12080/#content-type-object--document-field) for more information.

Products still drive alignment of content in PromoMats/MedComms and are required for integration and sync purposes.

### Setting Up Consent for Approved Email as

[![Closed](../../../../../Skins/Default/Stylesheets/Images/transparent.gif)Business Admin Users](#)

Consent admins create consent type records using the approved\_email\_\_v object type. See [Creating Consent Types](../CreateManageConsent/CreateConsentType.htm) for more information. To define consent lines for products and content types, see [Creating Consent Lines](../CreateManageConsent/CreateConsentLine.htm).

Consent Capture for Approved Email does not support sub channels on consent line records.

To capture consent for content types:

1. Navigate to **Business Admin > Objects > VMobile Object Configurations**.
2. Ensure there is an active **Full Sync VMOC** for the content\_type\_\_v object.
3. Navigate to **Business Admin > Objects > Consent Headers**.
4. Select the appropriate consent\_header\_\_v record.
5. Set the **consent\_header\_status\_\_v** field to Inactive or Staged to allow edits to the record.
6. Select **Edit** on the consent\_header\_\_v record again.
7. Select the **content\_type\_\_v** value for the approved\_email\_consent\_level\_\_v field.
8. Set the consent\_header\_status\_\_v field to **Active** or **Staged**:

   * Active — displays consent channels and lines on the Consent Capture screen and prevents further editing
   * Staged — hides the consent records from end users while allowing consent admins to review how the Consent Capture screen displays
9. Select **Save**.

There can only be consent lines of the same object type for an Approved Email channel. For example, if there is a Cholecap consent line, the business admin cannot create a content type consent line, only other product consent lines.

### Capturing Consent for Approved Email as

[![Closed](../../../../../Skins/Default/Stylesheets/Images/transparent.gif)End Users](#)

End users cannot send Approved Emails to HCPs who do not grant consent. If a user tries to send an approved email to an HCP who has not opted into receiving approved emails, the Send button is unavailable and a link to Change Opt Preferences displays for the recipient. Select the link to navigate directly to the Consent Capture screen for the account. After capturing consent, the user automatically returns to the Send Email screen.

### Related Topics

[Capturing Approved Email Opt-In Consent](../../ApprovedEmail/ConsentAE/CapturingOptIn.htm)

[Classic Consent in Approved Email](../../ApprovedEmail/ConsentAE/ClassicConsentComponents.htm)