Source: https://vaultcrmhelp.veeva.com/doc/Content/CRM_topics/Multichannel/ApprovedEmailDocModel/ConfiguringAE/AEConfig.htm

## Configuring Approved Email as Document Model

### Configuring Approved Email for

[![Closed](../../../../../Skins/Default/Stylesheets/Images/transparent.gif)Admins, Content Admins, and Integration Users](#)

To configure Approved Email for admins, content admin users, and integration users:

1. Ensure [Multi-Language Support](https://platform.veevavault.help/en/gr/13309/#enable-multi-language) is enabled in the Vault CRM instance.
2. Navigate to **Admin > Users & Groups > Permission Sets**.
3. Select the permission set for the appropriate user profile.
4. Navigate to **Objects**.
5. Grant the following permissions:

   | Object | Object Permission | Object Types | Fields | Field Permission |
   | --- | --- | --- | --- | --- |
   | account\_\_v | R | All applicable object types | * approved\_email\_opt\_type\_\_v * language\_\_v * restricted\_products\_\_v | Read |
   | approved\_email\_settings\_\_v | R | n/a | All Fields | Read |
   | channel\_metrics\_\_v | R | email\_\_v | * account\_\_v * channel\_value\_\_v * channel\_source\_\_v * external\_id\_\_v * last\_email\_error\_date\_\_v * email\_delivery\_error\_\_v * email\_activity\_\_v | Read |
   | email\_activity\_\_v | CRE | email\_activity\_\_v | * activity\_datetime\_\_v * approved\_document\_\_v * bot\_\_v * city\_\_v * click\_url\_\_v * client\_name\_\_v * client\_os\_\_v * client\_type\_\_v * country\_\_v * device\_type\_\_v * event\_msg\_\_v * event\_type\_\_vip\_address\_\_v * link\_name\_\_v * name\_\_v * object\_type\_\_v * region\_\_v * sent\_email\_\_v * user\_agent\_\_v | Edit |
   | * created\_by\_\_v * created\_date\_\_v * modified\_by\_\_v * modified\_date\_\_v | Read |
   | multichannel\_consent\_\_v | CRED | * approved\_email\_\_v * clm\_\_v * engage\_\_v * sample\_consent\_\_v | * account\_\_v * capture\_datetime\_\_v * channel\_source\_\_v * channel\_value\_\_v * detail\_group\_\_v * last\_device\_\_v * mobile\_id\_\_v * opt\_expiration\_date\_\_v * opt\_type\_\_v * optout\_event\_type\_\_v * product\_\_v * signature\_datetime\_\_v * signature\_id\_\_v * signature\_\_v | Edit |
   | * created\_by\_\_v * created\_date\_\_v * modified\_by\_\_v * modified\_date\_\_v | Read |
   | product\_\_v | CRED | n/a | vexternal\_id\_\_v | Edit |
   | sent\_email\_\_v | CRE | * call\_\_v * clm\_\_v * email\_receipt\_\_v * events\_management\_\_v * medical\_event\_\_v * medical\_inquiry\_\_v | * call2\_\_v * email\_config\_values\_\_v * email\_config\_values\_file\_\_v * email\_content\_file\_\_v * email\_sent\_date\_\_v * failure\_msg\_\_v * last\_activity\_date\_\_v * list\_unsubscribe\_header\_v * related\_transaction\_id\_\_v * receipt\_record\_id\_v * sent\_email\_status\_\_v * territory\_\_v | Edit |
   | * account\_email\_\_v * account\_\_v * approved\_email\_template\_\_v * capture\_datetime\_\_v * created\_by\_\_v * created\_date\_\_v * detail\_group\_\_v * email\_fragments\_\_v * email\_group\_id\_\_v * email\_source\_\_v * mc\_capture\_datetime\_\_v * mobile\_id\_\_v * modified\_by\_\_v * modified\_date\_\_v * object\_type\_\_v * ownerid\_\_v * product\_\_v * scheduled\_send\_datetime\_\_v * sender\_email\_\_v * subject\_\_v * valid\_consent\_exists\_\_v | Read |
   | sent\_fragment\_\_v | R | All applicable object types | * created\_by\_\_v * created\_date\_\_v * modified\_by\_\_v * modified\_date\_\_v | Read |
   | tsf\_\_v | R | n/a | * account\_\_v * allowed\_products\_\_v | Read |
   | user\_\_sys | R | n/a | approved\_email\_admin\_\_v | Read |
   | user\_detail\_\_v | CRED | user\_detail\_\_v | user\_\_v | Read |
   | veeva\_settings\_\_v | R | n/a | legacy\_org\_id\_\_v | Read |

   If [Dynamic Access Control](https://platform.veevavault.help/en/gr/33946/) is enabled for any of the objects leveraged by Approved Email, for example Sent Email, Email Activity, or Multichannel Consent, the Approved Email integration user should have All Object Record Read and All Object Record Edit permissions enabled.
6. Navigate to **Application** in the permission set.
7. Grant the administrator and the integration user access to **File Staging** in the Enable Access column.

   ![](../../../../Resources/Images/Multichannel/ApprovedEmail/Config/ae-config-file-staging.png)
8. Grant the administrator and the integration user **Access API** permission for the API action.
9. Navigate to the **Pages** tab in the permission set.
10. Grant the administrator and the integration user access to the following pages:

    * Approved Email Administration
    * CRM PL1 Generic Page
    * CRM PL3 Generic Page

      PL1 and PL3 are generic layouts used to render various pages across modules in Vault CRM.
11. Navigate to the **Tabs** tab in the permission set.
12. Grant the administrator and the integration user access to the **CRM Setup** Tab Collection.
13. Grant the administrator and the integration user access to the **Approved Email** tab.
14. Navigate to **Admin > Configuration > Objects > sent\_email\_\_v > Object Types > Account**.
15. Select the **last\_device\_\_v** field.
16. Ensure all appropriate picklist values are available, including the **iPad** and **Online** values.
17. Navigate to **Business Admin > Objects > user\_territory\_\_v**.
18. Create a user\_territory\_\_v record for the integration user and assign the integration user to the root territory in the vault. For more information, see [Viewing Territories in the Hierarchy](../../../TerritoryManagement/AssignAccts/CreateTerr.htm#Viewing).
19. Update the WHERE clause and verify users have read access to the modified\_date\_\_v field if the following VMOCs are enabled:
    * sent\_email\_\_v - WHERE account\_\_v IN (SELECT id FROM account\_\_vr) AND created\_date\_\_v >= LAST\_DAYS:90
    * sent\_fragment\_\_v - WHERE account\_\_v IN (SELECT id FROM account\_\_vr) AND created\_date\_\_v >= LAST\_DAYS:90
20. Ensure users have read access to the **modified\_date\_\_v** field on the channel\_metrics\_\_v object.
21. Grant Execute access to the **Send Email** action on the appropriate account\_\_v object types for testing purposes.

    The Send Email action does not control the ability to send emails on mobile devices. The action is displayed based on the user's permissions to the Sent Email and Multichannel Consent objects.

#### Designating Content Admin Users

An additional process is required to designate users as content admin users:

1. Place the **approved\_email\_admin\_\_v** field on the appropriate user\_\_sys layouts.
2. Navigate to the appropriate user.
3. Select the Approved Email Admin checkbox.
4. Select **Save**.
5. Log in as the vault owner.
6. Navigate to **Admin > Users & Groups**.
7. Select the appropriate user.
8. Verify the user is granted **Full User** license to the Approved Email application in Vault CRM.
9. Ensure Content Admin Users are assigned to the Content Administrator role for Approved Email Document Types via Dynamic Access Control. See [About Dynamic Access Control for Documents](https://platform.veevavault.help/en/gr/31824/) for more information.

[![Closed](../../../../../Skins/Default/Stylesheets/Images/transparent.gif)End Users](#)

To configure Approved Email for end users:

1. Navigate to **Admin > Users & Groups > Permission Sets**.
2. Select the permission set for the appropriate user profile.
3. Navigate to **Objects**.
4. Grant the following permissions:

   | Object | Object Permission | Object Types | Fields | Field Permission |
   | --- | --- | --- | --- | --- |
   | account\_\_v | R | All applicable object types | * approved\_email\_opt\_type\_\_v * language\_\_v * restricted\_products\_\_v | Read |
   | approved\_email\_settings\_\_v | R | n/a | All Fields | Read |
   | channel\_metrics\_\_v | R | n/a | * name * account\_\_v * channel\_value\_\_v * channel\_source\_\_v * external\_id\_\_v * last\_email\_error\_date\_\_v * email\_delivery\_error\_\_v * email\_activity\_\_v | Read |
   | email\_activity\_\_v | R | email\_activity\_\_v | * event\_type\_\_v * activity\_datetime\_\_v * bot\_\_v * event\_msg\_\_v * approved\_document\_\_v * city\_\_v * click\_url\_\_v * client\_name\_\_v * client\_os\_\_v * client\_type\_\_v * country\_\_v * created\_by\_\_v * created\_date\_\_v * device\_type\_\_v * ip\_address\_\_v * link\_name\_\_v * modified\_by\_\_v * modified\_date\_\_v * region\_\_v * sent\_email\_\_v * user\_agent\_\_v | Read |
   | multichannel\_consent\_\_v | CRE | approved\_email\_\_v | * account\_\_v * capture\_datetime\_\_v * channel\_source\_\_v * channel\_value\_\_v * detail\_group\_\_v * last\_device\_\_v * mobile\_id\_\_v * opt\_expiration\_date\_\_v * opt\_type\_\_v * product\_\_v * signature\_datetime\_\_v * signature\_id\_\_v * signature\_\_v | Edit |
   | * optout\_event\_type\_\_v * created\_by\_\_v * created\_date\_\_v * modified\_by\_\_v * modified\_date\_\_v | Read |
   | sent\_email\_\_v | CRE | * account\_\_v * call\_\_v * clm\_\_v * email\_receipt\_\_v * events\_management\_\_v * medical\_event\_\_v * medical\_inquiry\_\_v | * account\_email\_\_v * account\_\_v * approved\_email\_template\_\_v * call2\_\_v * capture\_datetime\_\_v * detail\_group\_\_v * email\_config\_values\_\_v * email\_config\_values\_file\_\_v * email\_fragments\_\_v * email\_group\_id\_\_v * email\_sent\_date\_\_v * email\_source\_\_v * last\_device\_\_v * list\_unsubscribe\_header\_v * mc\_capture\_datetime\_\_v * mobile\_id\_\_v * object\_type\_\_v * ownerid\_\_v * product\_\_v * related\_transaction\_id\_\_v * receipt\_record\_id\_v * sender\_email\_\_v * sent\_email\_status\_\_v * status\_\_v * subject\_\_v * territory\_\_v * user\_input\_text\_\_v * valid\_consent\_exists\_\_v | Edit |
   | * approved\_document\_views\_\_v * click\_count\_\_v * clicked\_\_v * created\_by\_\_v * created\_date\_\_v * email\_content\_file\_\_v * failure\_msg\_\_v * last\_activity\_date\_\_v * last\_click\_date\_\_v * last\_open\_date\_\_v * modified\_by\_\_v * modified\_date\_\_v * open\_count\_\_v * product\_display\_\_v | Read |
   | tsf\_\_v | R | n/a | * account\_\_v * allowed\_products\_\_v * territory\_name\_\_v | Read |
   | user\_\_sys | R | n/a | * approved\_email\_admin\_\_v * email\_\_sys | Read |
   | user\_detail\_\_v | CRE | All | user\_\_v | Edit |
   | * created\_by\_\_v * created\_date\_\_v * modified\_by\_\_v * modified\_date\_\_v | Read |
5. Grant end users Execute permission to the **Send Email** object action permission on the Account object.
6. Navigate to **Application > File Staging** in the permission set.
7. Grant end users access to **File Staging** in the Enable Access column.
8. Navigate to **Admin > Configuration > Objects > Account > Object Types**.
9. Select the **Actions** link.
10. Select **Edit Object Type Actions** from the Actions menu.
11. Enable the **Send Email** action for the appropriate account object types.
12. Select **Save**.
13. Navigate to **Business Admin > Objects > Approved Email Settings**.
14. Edit the appropriate record.

    While [profile specific](../../../Getting_Started/SettingUp/VeevaCustomSettings.htm#Configur) Approved Email Settings records are supported, a Global record must exist with both Application Profile and Security Profile empty.
15. Populate the following fields:

    * enable\_approved\_email\_documents\_\_v – Select True
    * approved\_email\_filter\_fields\_\_v – Populate with the list of Document field API names to enable filtering from

#### Enabling Approved Email Documents for Mobile Devices

To sync Approved Email documents to mobile devices:

1. Navigate to **Business Admin > Objects > Veeva Settings**.
2. Edit the appropriate record.
3. Populate the **Sync Configuration Mode** field with 1.
4. Navigate to **Business Admin > Objects >VMobile Object Configurations**.
5. Ensure the following VMOCs exist. If a VMOC does not exist, create it. All VMOCs must be **Active** with the appropriate device selected. See [Using VMobile Object Configurations](../../../Getting_Started/MobileDeviceSetup/Sync/VMOCs.htm) for more information.

   | Object | VMOC Configuration |
   | --- | --- |
   | approved\_email\_settings\_\_v | * Type – Full Sync * Where Clause – WHERE application\_profile\_\_v = @@USER\_APP\_PROFILE\_ID@@ OR (application\_profile\_\_v = null AND security\_profile\_\_v = null) |
   | channel\_metrics\_\_v | * Type – Full Sync * Where Clause – WHERE account\_\_v IN (SELECT id FROM account\_\_vr) Ensure users have read access to the modified\_date\_\_v field on the channel\_metrics\_\_v object. |
   | multichannel\_consent\_\_v | * Type – Full Sync * Account Lookup Field – account\_\_v * Where Clause – None |
   | sent\_email\_\_v | * Type – Top Level * Where Clause – WHERE account\_\_v IN (SELECT id FROM account\_\_vr) AND created\_date\_\_v >= LAST\_DAYS:90 |
   | user\_detail\_\_v | * Type – Full Sync * Where Clause – WHERE user\_\_v = @@USER\_ID@@ |
   | documents | * type\_\_v: Full * object\_name\_\_v: "documents" * where\_clause\_\_v: "WHERE TONAME(type\_\_v) CONTAINS ('email\_template\_\_v', 'email\_fragment\_\_v', 'template\_fragment\_\_v') AND TONAME(lifecycle\_\_v) = 'crm\_content\_lifecycle\_\_v' AND TONAME(status\_\_v) = 'approved\_\_v'" * enhanced\_sync\_\_v: True * document\_query\_modifier\_\_v: "latest\_matching\_version\_\_v" To allow Approved Email admins to view staged content on mobile devices, manually add staged\_\_v to the WHERE clause of the documents VMOC:  WHERE TONAME(type\_\_v) CONTAINS ('email\_template\_\_v', 'email\_fragment\_\_v', 'template\_fragment\_\_v') AND TONAME(lifecycle\_\_v) = 'crm\_content\_lifecycle\_\_v' AND TONAME(status\_\_v) CONTAINS ('approved\_\_v', 'staged\_\_v') |
   | relationships | * type\_\_v: Full * object\_name\_\_v: "relationships" * where\_clause\_\_v: "WHERE TONAME(source\_\_vr.type\_\_v) CONTAINS ('email\_template\_\_v', 'email\_fragment\_\_v') AND TONAME(source\_\_vr.lifecycle\_\_v) = 'crm\_content\_lifecycle\_\_v' AND TONAME(source\_\_vr.status\_\_v) = 'approved\_\_v' AND relationship\_type\_\_v CONTAINS ('related\_piece\_\_v', 'related\_email\_fragments\_\_v', 'related\_template\_fragments\_\_v', 'related\_pi\_\_v', 'related\_isi\_\_v', 'other\_related\_documents\_\_v', 'email\_fragment\_content\_\_v')" |

### Related Topics

[Approved Email Overview](../AEMainOverview.htm)

[Integrating Vault CRM and PromoMats / MedComms for Approved Email](AECRMVaultIntegration.htm)

[Creating a Sending Domain](CreateSendingDomain.htm)
