Configuring Engage Meeting
Initial configuration includes the setup of all default functionality for Engage meeting. Some functionality requires additional configuration.
Components of Engage Meeting
Engage consist of the following components:
Remote Meeting (remote_meeting__v)
Remote meetings represent the Engage meeting and contain information about the meeting's name, start time, end time, etc. Remote Meeting records with the call2__v object type signify Engage meetings that were created through a call. See below for more information about configuring this component.
Remote Meeting Attendee (remote_meeting_attendee__v)
Remote meeting attendees represent the users and HCPs attending an Engage meeting. Each records contains information about the attendee's name, account, type, participant ID, join and leave times, device and network, and more. See below for more information about configuring this component.
Configuring Engage Meeting
Ensure the appropriate Vault has Engage licenses provisioned.
Business Admins
To configure Engage meeting for business admins:
- Grant the following permissions:
Object Object Permission Object Types Fields Field Permissions user_detail__v RE n/a remote_meeting_name__v
Populate this field to update the default name for Engage meetings.
Edit user__sys RE n/a - engage_group_provisioning_status__v
- engage_group_request__v
- engage_group__v
- remote_meeting_host_id__v
- remote_meeting_host_token__v
Edit -
Add the following fields to the appropriate user__sys layout:
- engage_group_provisioning_status__v
- engage_group_request__v
- engage_group__v
- Grant access to the CRM Setup tab collection.
- Grant access to the following Pages:
- Engage Group Management
- CRM PL3 Generic Page
End Users
- Grant the following permissions:
Object Object Permission Object Types Fields Field Permissions call2__v
CRED
call_report__v
- call_datetime__v
- cobrowse_url_participant__v
- remote_meeting_type__v
- remote_meeting__v
- veeva_remote_meeting_id__v
Edit
remote_meeting__v CRED call__v - modified_date__v
- ownerid__v
Read
- meeting_id__v
- meeting_name__v
- meeting_password__v
- mobile_id__v
- scheduled__v
- scheduled_datetime__v
- vexternal_id__v
Edit user__sys RE n/a - remote_meeting_host_id__v
- remote_meeting_host_token__v
Read - Navigate to Admin > Configuration > Objects > Call > Layouts
- Select the Enable Engage section attribute in the General Call section on the call2__v object layout used for Engage meetings.
- Navigate to Admin > Configuration > Objects > Remote Meeting > Layouts.
- Ensure there is a layout for the call__v object type on the remote_meeting__v object.
- Place the meeting_name__v field on the remote_meeting__v layout. This step is optional and allows iPad hosts to edit the meeting name.
- Navigate to Business Admin > Objects > VMobile Object Configurations.
- Enable a Full Sync VMOC for the remote_meeting__v object for the appropriate platforms.
- Ensure the Start Meeting from CRM Online group meeting permission is selected for the Engage meeting group to which the end user is assigned. See Group Meeting Permissions for more information.
Assigning Users to Engage Groups
Users must be assigned to a group to use Engage meeting. Engage Group Assignment is controlled via the user__sys object. See Engage Group Management for more information.
Using Engage Meetings in Multi-Vault Domains
An end user in a multi-Vault domain can be assigned to an Engage Group in one or more of the Vault instances in the domain. This enables end users to schedule and host Engage meetings from different Vault instances with access to different data and content. Users must have an active Engage license for every Vault and Engage group they are assigned to.
Ensure Engage meetings are configured in each appropriate Vault CRM instance. Ensure end users are assigned to Engage Groups in the appropriate instances. See About Veeva Vault Domains & Domain Settings for more information.
To remove an end user from all Engage Groups in the domain, admins must individually remove the user from each Engage Group in each Vault instance. See Engage Group Management for more information about managing users in Engage Groups.
Meeting information is not shared between Vaults in the same domain, even if the end user is the same. When end users schedule and host Engage meetings from a specific Vault instance, they only have access to the meeting functionality enabled for that instance. Additionally, the attendance tracking information for an Engage meeting is only created in the instance from which the meeting was scheduled.
