Configuring Approved Email Admins and Integration Users

Initial configuration includes the setup of all default functionality for Approved Email. Some functionality requires additional configuration.

Configuring Admins, Content Admins, and Integration Users

To configure Approved Email for admins, content admins and integration users:

  1. Grant the following permissions:

    Object OLS Record Types Fields FLS
    Accounts R n/a
    • Approved_Email_Opt_Type_vod
    • Language_vod
    Read
    Approved_Document_vod CRUD
    • Case_Template_vod
    • CoBrowse_Invite_Template_vod
    • Email_Fragment_vod
    • Email_Receipt_vod
    • Email_Template_vod
    • Engage_vod
    • Medical_Inquiry_Template_vod
    • Allowed_Document_IDs_vod
    • Allow_Any_Product_Fragment_vod
    • Check_Consent_vod
    • Engage_Document_Id_vod
    • Language_vod
    • Vault_Document_ID_vod

      This is the Field Name, not the Field Label.

    Edit
    Contact R n/a
    • IndividualId
    Edit

    Email_Activity_vod

    CRU

    • Email_Activity_vod
    • Vault_Activity_vod
    • Approved_Document_vod
    • Sent_Email_vod
    • Link_Name_vod

    Edit

    Multichannel_Consent_vod

    CRUD

    • Approved_Email_vod
    • CLM_vod
    • Engage_vod
    • Sample_Consent_vod
    • Account_vod
    • Capture_Datetime_vod

    • Channel_Value_vod

    • Detail_Group_vod

    • Optout_Event_Type_vod

    • Opt_Expiration_Date_vod

    • Opt_Type_vod

    • Product_vod

    Edit

    Product_vod

    CRUD

    n/a

    • VExternal_Id_vod

    Edit

    Sent_Email_vod

     

    CRU

     

    • Call_vod
    • Case
    • CLM_vod
    • CoBrowse_Invite_vod
    • Email_Receipt_vod
    • Events_Management_vod
    • Medical_Event_vod
    • Medical_Inquiry_vod

     

    • Call2_vod
    • Email_Config_Values_vod
    • Email_Sent_Date_vod
    • Email_Content_vod
    • Email_Content2_vod
    • Email_Source_vod
    • Medical_Inquiry_vod
    • Parent_Email_vod
    • Related_Transaction_Id_vod
    • Scheduled_Send_Datetime_vod
    • Territory_vod
    Edit
    TSF_vod R n/a
    • Account_vod
    Edit
    • Allowed_Products_vod
    Read
    User R n/a
    • Approved_Email_Admin_vod
    Read

    User_Detail_vod

    CRUD

    User_Detail_vod

    n/a

    n/a

  2. Grant access to the following Visualforce pages:

    • Approved_Email_Admin_Page_vod
    • Approved_Email_Configuration_Checker_vod
    • Approved_Email_License_Management_vod
    • Email_Opt_in_vod
    • Send_Approved_Email_vod
    • User_Detail_Image_vod
  3. Create a custom tab for the Approved_Document_vod object.
  4. Grant the administrator and the integration user access to the following tabs:

    • The custom tab created for the Approved_Document_vod object
    • Approved_Email_Administration_vod
    • Approved_Email_Configuration_Checker_vod
    • Approved_Email_License_Management_vod
  5. Add the Send_Email_vod button to the appropriate Account page layouts. This step is only required if you want to enable sending emails on the Online platform.
  6. Add the Email_Opt_In_vod button to the appropriate Account page layouts. This step is only required if you want to enable capturing opt-in on the Online platform.

Designating Content Admins

An additional process is required to designate users as content admins:

  1. Add the Approved_Email_Admin_vod field to the appropriate User page layouts.
  2. Navigate to the appropriate user.
  3. Select the Approved Email Admin check box.

Permission Sets

Permissions can be applied to a User via profile permissions or permissions sets. Permission sets are available in Approved Email product, making it easier to get started with Approved Email. Two permission sets are included, one for the Administrator or integration user, and one for the field user:

  • AE_ADMIN_INTEGRATION_USER_VOD – For admins and integration users
  • AE_FIELD_USER_VOD – For end users

Major versions of Veeva CRM may update these permission sets to include permissions to the newest features. New feature deployment involves change management and training. For that reason, Veeva recommends cloning the Veeva-delivered permission sets and enabling the features that you want to use.

Ensure the VeevaUserPermissions Apex Class is installed before continuing with permission sets. See Security in Veeva CRM for more information.