To configure this feature, ensure Configuring Approved Email is complete.

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.

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