Source: https://vaultcrmhelp.veeva.com/doc/Content/CRM_topics/Multichannel/ApprovedEmail/ManagingContent/AlignContent.htm

## Aligning Approved Email Content to Users

Customers may use a large variety of content when using Approved Email. Content admins can implement layers of control to refine the content that displays as available.

**Who can use this feature?**

* Content Admin Users — Browser
* [Aligning Approved Email Content to Users](#Aligning)
* End Users — Browser, iPad, iPhone
* [Using Alignment of Approved Email Content to Users](#Using)
* Users require an Approved Email license

### Configuring Customized Email Header Behavior for

[![Closed](../../../../../Skins/Default/Stylesheets/Images/transparent.gif)Content Admins](#)

To configure this feature, ensure [Configuring Approved Email](../InitialConfig/ConfiguringAE.htm) is complete.

### Aligning Approved Email Content to Users as

[![Closed](../../../../../Skins/Default/Stylesheets/Images/transparent.gif)Content Admins](#)

The following methods can be used independently and in conjunction with one another to provide a nuanced and compliant method to align and restrict Approved Email content:

* The status\_\_v field on the approved\_document\_\_v object

  This is the base layer of access; the other methods below only matter if the status field grants the user access to the document.
* End users can only access Approved Documents where status\_\_v is approved\_\_v
* Content admins can only access Approved Documents where status\_\_v is either approved\_\_v or staged\_\_v
* The my\_setup\_products\_\_v object – End users and content admins can only access content that is aligned to a Detail Product or Topic that the user can access via My Setup Products
* Sharing Rules – Custom sharing rules can be setup on the approved\_document\_\_v object. The territory\_\_v field on the approved\_document\_\_v object can be used as the basis for sharing rules in CRM by populating the corresponding field in Vault.
* VMOCs – The WHERE clause of VMOC for the approved\_document\_\_v object can be customized to filter which approved\_document\_\_v records sync down to mobile devices

#### Example: Status and Product Groups

For example, the following templates exist in a Vault:

* Template A
* Status: Approved
* Detail Product: Cholecap
* Template B
* Status: Staged
* Detail Product: Cholecap
* Template C
* Status: Approved
* Detail Product: Labrinone

If an Approved Email end user with access to Cholecap in My Setup sends an Approved Email to an HCP, only Template A displays as available for selection since Template B has a status of Staged and Template C is for Labrinone, which the user does not have access to.

### Using Alignment of Approved Email Content to Users as

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

Email templates in the Send Email screen are limited to those the end user has access to, based on alignment by content admins.

### Related Topics

[Personalizing User Profiles](../CreatingContent/PersonalizingUserProfile.htm)

[Creating Approved Email Templates](../CreatingContent/CreatingAETemplates.htm)