Source: https://vaultcrmhelp.veeva.com/doc/Content/CRM_topics/Multichannel/ApprovedEmail/ConsentAE/ClassicConsentComponents.htm

## Classic Consent in Approved Email

Classic consent in Approved Email ensures that end users are compliant with local regulations requiring certain levels of consent be obtained before emails are sent to an account.

Each account has some control over what emails are sent to them. Vault CRM's flexible consent model supports a variety of opt types and ensures that opt preferences of an account are respected when sending emails, including designating an account as never being allowed to receive emails.

Classic consent in Approved Email consists of three primary components:

* Consent Type
* Consent Records
* Consent Validation

**Who can use this feature?**

* Approved Email Admin Users
* [Defining Consent Types](#Defining)
* [Using Consent Records](#Using)
* End Users — iPad
* [Validating Consent](#Validati)
* Users require an Approved Email license

### Defining Consent Types as

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

There are three types of consent in Approved Email:

* Opt-in Required – An opt-in record is required to send email
* Opt-in Not Required – An opt-in record is not required to send email
* Never Email – Emails cannot be sent to the account and opt-in cannot be recorded (this option is only available when set on an existing account)

Every account can have a unique consent type, allowing a single Vault to apply different consent types to different accounts.

#### Consent Type Levels

Consent types can be defined at two levels to grant varying levels of control over an individual account's consent type:

* The Approved Email Opt-in Required Approved Email setting – This checkbox setting enables admins to set a default consent type value for all accounts

  + When this checkbox is selected, the consent type is Opt-in Required

    ![](../../../../Resources/Images/Multichannel/ApprovedEmail/AEOptinRequired.png)
  + When this checkbox is not selected, the consent type is Opt-in Not Required

  This value can be overridden on an individual account using the approved\_email\_opt\_type\_\_v picklist on the account\_v object
* The approved\_email\_opt\_type\_\_v field on the account\_v object – When this picklist is NULL, the account inherits the consent type from the Approved Email Opt-In Required Approved Email setting. When populated with one of the following values, this picklist overrides the setting, enabling more granular control over an account's consent type:
* explicit\_opt\_in\_\_v – Sets the Consent Type to Opt-in Required
* implicit\_opt\_in\_\_v – Sets the Consent Type to Opt-in Not Required
* never\_\_v – Sets the Consent Type to Never Email

For example, the Multichannel Explicit Opt In Approved Email setting is selected. An HCP account has approved\_email\_opt\_type\_\_v=NULL, so his inherited consent type is Opt-in Required. Another HCP account has approved\_email\_opt\_type\_\_v=implicit\_opt\_in\_\_v. This picklist overrides the setting, so his consent type is Opt-in Not Required.

### Using Consent Records as

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

Consent records are stored as approved\_email\_\_v object type multichannel\_consent\_\_v records and represent a specific opt choice made by an account. Consent records are used during the [validation phase](#Validati) to check if the proper consent exists. Consent records contain the following information:

* account\_\_v – References the account associated with this consent record
* capture\_datetime\_\_v – The capture datetime
* channel\_value\_\_v – In approved\_email\_\_v type records, this field references the associated email address
* opt\_type\_\_v – Represents the captured opt preference and can be one of the following values:
  + opt\_in\_\_v – Emails for all products can be sent to this account and email address pair. Created opt-in records never expire and immediately expire all opt-out multichannel\_consent\_\_v records referencing the same account and email address.

    If an account has more than one email address, one opt-in record per email address is required prior to sending email for each address.
  + opt\_out\_\_v – Opt-out type consent records also reference a specific product. Emails cannot be sent to this account, email address, and product triplet.
* product\_\_v – Only populates when opt\_type\_\_v=opt\_out\_\_v. References the product associated with the opt-out consent record.
* detail\_group\_\_v – Only populates when opt\_type\_\_v=opt\_out\_\_v and when using Detail Groups with Products
* optout\_event\_type\_\_v – This picklist only populates if opt\_type\_\_v=opt\_out\_\_v and indicates the opt-out event that caused the consent record to be created:
* unsubscribed\_\_v – The recipient selected an Unsubscribe link within the email
* consent\_capture\_\_v – The recipient opted out of emails via Consent Capture

Pre-existing content preferences can be loaded from external systems into multichannel\_consent\_\_v records.

#### Data Loading Consent Records

The multichannel\_consent\_\_v object can be populated using a data loader or other integrations. Each multichannel\_consent\_\_v record requires the following values:

* object\_type\_\_v – Must be approved\_email\_\_v
* account\_\_v
* capture\_datetime\_\_v
* channel\_value\_\_v – In approved\_email\_\_v type records, this field references the associated email address
* opt\_type\_\_v – Can be either opt\_in\_\_v or opt\_out\_\_v
* optout\_event\_type\_\_v – Only required when opt\_type\_\_v is opt\_out\_\_v

When data loading consent records with Vault Loader, do not select No Triggers. Triggers are essential for the proper functioning of multichannel consent. They expire related existing records, ensuring only the new record is valid.

#### Examples of Consent Records

For example, an HCP opts in to receiving emails sent to exampleaddress@gmail.com. A multichannel\_consent\_\_v record with an object type of approved\_email\_\_v is created with the following fields:

* account\_\_v – References the HCP's account
* capture\_datetime\_\_v – The datetime when the HCP consented to receive emails
* channel\_value\_\_v – exampleaddress@gmail.com
* opt\_type\_\_v – opt\_in\_\_v
* optout\_event\_type\_\_v – The HCP did not opt out of emails, so this picklist is blank

Emails for all products can now be sent to the HCP at exampleaddress@gmail.com.

In another example, an HCP selects the Unsubscribe link in an email associated with Cholecap sent to his email address exampleaddress@gmail.com. A multichannel\_consent\_\_v record with an object type of approved\_email\_\_v is created with the following fields:

* account\_\_v – References the HCP's account
* capture\_datetime\_\_v – The datetime when the HCP submitted the unsubscribe request
* channel\_value\_\_v – exampleaddress@gmail.com
* opt\_type\_\_v – opt\_out\_\_v
* optout\_event\_type\_\_v – unsubscribed\_\_v
* product\_\_v – Cholecap

Validation prevents all Cholecap emails sent to the HCP using exampleaddress@gmail.com from sending until an end user captures opt-in consent from the HCP. Emails about other products can still be sent to exampleaddress@gmail.com.

### Validating Consent as

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

Consent is validated whenever an end user tries to send an Approved Email. Validation looks at both the consent type of the recipients as well as any consent records associated with the account. Validation occurs in the following steps:

1. Check the consent type of the account. This is determined by the approved\_email\_opt\_type\_\_v picklist on the account. If the picklist is NULL, the consent type is determined by the Multichannel Explicit Opt In Approved Email setting:

   * Consent type is Opt-in Required – Validation looks for any active opt-in multichannel\_consent\_\_v record associated with both the account and the email address
   * If no opt-in record exists, end users are prevented from sending the email and are prompted to [capture opt-in consent](CapturingOptIn.htm)
   * If a valid opt-in record exists, validation proceeds to Step 2
   * Consent type is Opt-in Not Required – Validation proceeds to Step 2
   * Consent type is Never Email – End users are prevented from sending the email
2. Check for any active opt-out multichannel\_consent\_\_v records associated with the account, email address, and product.

   * If an active opt-out record exists, end users are prevented from sending the email and are prompted to [capture opt-in consent](CapturingOptIn.htm)

If these two steps are completed without error, the end user is able to send the email.

### Related Topics

[Capturing Consent for Approved Email](../../ConsentCapture/IntegrateFunct/AEConsent.htm)

[Managing In-Person Consent Confirmation Methods](../../ConsentCapture/CreateManageConsent/InPersonConfirmation.htm)