Configuring Approved Email End Users
Additional configuration is required for Approved Email end users. Approved Email is a primary channel of communication between end users and the accounts they serve. End users compose emails from approved content, select accounts as recipients, personalize the content (if enabled), and send the emails to accounts.
Configuring Approved Email for
To configure Approved Email for end users:
-
Navigate to Admin > Users & Groups > Permission Sets.
-
Select the permission set for the appropriate user profile.
-
Navigate to Objects.
-
Grant the following permissions:
Object Object Permission Object Types Fields Field Permission account__v R n/a - approved_email_opt_type__v
- language__v
- restricted_products__v
Read approved_document__v R - email_fragment__v
- email_receipt__v
- email_template__v
- engage__v
- medical_inquiry_template__v
- allow_any_product_fragment__v
- allowed_document_ids__v
- approved_document_status__v
- created_by__v
- created_date__v
- detail_group__v
- document_description__v
- document_host_url__v
- document_id__v
- document_last_mod_datetime__v
- email_allows_documents__v
- email_domain__v
- email_fragment_html_file__v
- email_from_address__v
- email_from_name__v
- email_html_file__v
- email_replyto_address__v
- email_replyto_name__v
- email_subject__v
- email_template_fragment_document_id__v
- email_template_fragment_html_file__v
- isi_document_id__v
- language__v
- modified_by__v
- modified_date__v
- other_document_id_list__v
- pi_document_id__v
- piece_document_id__v
- product__v
- status__v
- territory__v
- vault_document_id__v
- vault_instance_id__v
Read approved_email_settings__v R n/a - add_recipients__v
- approved_email_consent_text__v
- approved_email_consent_mode__v
- approved_email_domain__v
- approved_email_field_exclusions__v
- approved_email_filter_fields__v
- approved_email_disclaimer_text__v
- multichannel_explicit_opt_in__v
- approved_email_restricted_words__v
- approved_email_test_address__v
- approved_email_vault_endpoints__v
- approved_email_vault_query__v
- approved_email_count_limit__v
- approved_email_duration_limit__v
- created_by__v
- created_date__v
- disabled_approved_email_entrypoints__v
- enable_approved_email_receipts__v
- enable_drafts_folder__v
- enable_group_email__v
- global_id__sys
- id
- modified_by__v
- modified_date__v
- legacy_crm_id__v
- link__sys
- name__v
- recipient_name_in_email_header__v
- recipient_specific_fields__v
- security_profile__v
- setupownerid__v
- status__v
- timeline_view_email_link__v
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
- vault_activity__v
- event_type__v
- activity_datetime__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
- vault_doc_id__v
- vault_doc_name__v
- vault_document_number__v
- vault_document_title__v
- ip_address__v
- link_name__v
- modified_by__v
- modified_date__v
- vault_document_major_version__v
- vault_document_minor_version__v
- region__v
- sent_email__v
- user_agent__v
- vault_instance_id__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
- 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
Read user_detail__v CRE All - user__v
Edit - created_by__v
- created_date__v
- modified_by__v
- modified_date__v
Read
- Grant end users Execute permission to the Send Email object action permission on the Account object.
- Navigate to Application > File Staging in the permission set.
- Grant end users access to File Staging in the Enable Access column.
- Enable the VMOC for channel_metrics__v.
- Ensure users have read access to the modified_date__v field on the channel_metrics__v object.
- Navigate to Admin > Configuration > Objects > Account > Object Types.
- Select the Actions link.
- Select Edit Object Type Actions from the Actions menu.
- Enable the Send Email action for the appropriate account object types.
- Select Save.
- Add the language__v field to the approved_document__v layout.
Configuring Approved Email for Mobile Devices
The following process enables Approved Email for mobile devices:
- Open the VMobile Object Configurations tab.
-
Ensure the following VMOCs exist. If not, create them. For information on creating VMOCs, see Using VMobile Object Configurations. All VMOCs should be Active with the appropriate device:
Object VMOC Details approved_document__v - Type - Full Sync
- Where Clause - none
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 account__v IN (SELECT id FROM account__vr)
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@@
- Ensure users have read access to the modified_date__v field on the objects above.
Vault CRM does not support mobile device users having the File Staging API > Access Root Folder permission.
Email Templates reference images stored on public web servers. Approved Document attachments include a copy of the Email Template with embedded images. When synced, the Email Templates and images can be previewed from within Approved Email while offline ensuring that complex emails with many images render properly offline. Initial sync times may increase depending on the volume of Email Templates and embedded images.
Individual VMOC Settings contain WHERE clauses which enable users to add filters limiting the data pulled onto a mobile device during the Vault - Vault CRM integration. See VMOCs for more information.

