Source: https://vaultcrmhelp.veeva.com/doc/Content/CRM_topics/Integration/LegacyIntegration.htm

## Legacy Microsoft Outlook Integrations

Starting with the 26R2.0 release, Vault CRM will transition all Microsoft Outlook integrations, including the My Schedule calendar and Service Center Shared Mailbox to use the Core System User. While Vault CRM instances created after 26R1.0 will automatically use the Core System User, customers currently using a dedicated integration user must manually switch to the Core System User before 26R2.0 to maintain functionality.

### Legacy Microsoft Outlook Integration Permissions for

[![Closed](../../../Skins/Default/Stylesheets/Images/transparent.gif)My Schedule Integration User](#)

Legacy integration users require the following configuration for the My Schedule integration with Microsoft Outlook:

1. Navigate to **Admin > Users & Groups > Permission Sets**.
2. Select the appropriate integration user permission set, or create a permission set and security profile for the integration user, if one does not already exist. The integration user requires a dedicated permission set and security profile, but the same integration user can be used for multiple integrations in Vault CRM.
3. Select the **Objects** tab.
4. Grant the following permissions:

| Object | Object Permission | Object Types | Fields | Field Permission |
| --- | --- | --- | --- | --- |
| account\_\_v | at least R | All | * formatted\_name\_\_v * name\_\_v | at least Read |
| call2\_v | R | All | Required:   * account\_\_v * call\_date\_\_v * created\_date\_\_v * ownerid\_\_v * modified\_date\_\_v * ms\_teams\_remote\_meeting\_\_v   \*Optional:   * call\_datetime\_\_v * call\_channel\_\_v * duration\_\_v * parent\_call\_\_v | Read |
| child\_account\_\_v | R | All | parent\_child\_name\_\_v | Read |
| external\_calendar\_\_v | CRED | microsoft\_outlook\_\_v | Required:   * external\_calendar\_id\_\_v * is\_default\_calendar\_\_v * name\_\_v * object\_type\_\_v * ownerid\_\_v * title\_\_v   \*Optional:   * allowed\_online\_meeting\_providers\_\_v * can\_edit\_\_v * can\_share\_\_v * can\_view\_private\_items\_\_v * change\_key\_\_v * color\_\_v * default\_online\_meeting\_provider\_\_v * hex\_color\_\_v * is\_removable\_\_v * is\_tallying\_responses\_\_v * owner\_name\_and\_address\_\_v | Edit |
| external\_calendar\_event\_\_v | CRED | microsoft\_outlook\_\_v | Required:   * end\_datetime\_\_v * end\_time\_zone\_\_v * event\_created\_datetime\_\_v * event\_last\_modified\_datetime\_\_v * external\_calendar\_\_v * external\_calendar\_event\_id\_\_v * is\_all\_day\_\_v * object\_type\_\_v * original\_end\_time\_zone\_\_v * original\_start\_time\_zone\_\_v * sensitivity\_\_v * series\_master\_id\_\_v * start\_datetime\_\_v * start\_time\_zone\_\_v   \*Optional:   * allow\_new\_time\_proposals\_\_v * attendees\_\_v * body\_content\_type\_\_v * body\_preview\_\_v * categories\_\_v * change\_key\_\_v * description\_\_v * has\_attachments\_\_v * hide\_attendees\_\_v * icaluid\_\_v * importance\_\_v * is\_cancelled\_\_v * is\_draft\_\_v * is\_organizer\_\_v * is\_ms\_teams\_meeting\_\_v * is\_reminder\_on\_\_v * locations\_\_v * ms\_teams\_join\_url\_\_v * online\_meeting\_provider\_\_v * organizer\_name\_and\_email\_address\_\_v * recurrence\_\_v * reminder\_minutes\_before\_start\_\_v * response\_requested\_\_v * show\_as\_\_v * title\_\_v * transaction\_id\_\_v * type\_\_v * web\_link\_\_v | Edit |
| language\_\_sys | R | n/a | name\_\_v | Read |
| language\_locale\_\_sys | R | n/a | name\_\_v | Read |
| locale\_\_sys | R | n/a | name\_\_v | Read |
| medical\_event\_\_v | R | All | * created\_date\_\_v * end\_date\_\_v * end\_time\_\_v * modified\_date\_\_v * ownerid\_\_v * start\_date\_\_v * start\_time\_\_v | Read |
| medx\_\_v | R | All | * agenda\_\_v * created\_by\_\_v * created\_date\_\_v * end\_datetime\_\_v * modified\_date\_\_v * ownerid\_\_v * start\_datetime\_\_v * state\_\_v * status\_v * title\_\_v | Read |
| message\_\_v | R | n/a | * category\_\_v * language\_\_v * name\_\_v * text\_\_v | Read |
| remote\_meeting\_\_v | R | base\_\_v | Required:   * meeting\_id\_\_v * ms\_teams\_meeting\_link\_\_v   \*Optional:   * meeting\_password\_\_v * scheduled\_\_v | Read |
| time\_off\_territory\_\_v | R | All | * created\_date\_\_v * date\_\_v * hours\_off\_\_v * modified\_date\_\_v * ownerid\_\_v * reason\_\_v * start\_time\_\_v * time\_\_v | Read |
| user\_\_sys | RE | n/a | * ms\_outlook\_last\_pull\_activity\_\_v * ms\_outlook\_last\_push\_activity\_\_v | Edit |
| * application\_profile\_\_v * enable\_ms\_outlook\_calendar\_\_v * id * name\_\_v * user\_identifier\_\_v * language\_\_sys * locale\_\_sys * license\_type\_\_sys * security\_profile\_\_sys * timezone\_\_sys | Read |
| veeva\_settings\_\_v | R | n/a | * application\_profile\_\_v * disable\_tot\_weekends\_\_v * enable\_schedule\_medical\_event\_\_v * enable\_child\_account\_\_v * security\_profile\_\_v | Read |

\*To control which information from a Microsoft Outlook entry is pulled in to Vault CRM, admins can remove integration users’ field permission for fields which are not required for the integration. Changes to field permissions only apply for future entries. After the integration user’s field permission is removed, the data from that field continues to display on previously synced Microsoft Outlook entries in Vault CRM, until the entries are updated and re-synced.

### Related Topics

[Integrating My Schedule and Microsoft Outlook Calendars](../CallPlanning/Scheduling/OutlookIntegration.htm)

[Using the Service Center Inbound Tab](../ServiceCenter/Inbound/SCInbound.htm)

If any of the objects in Vault CRM have Dynamic Access Control enabled, the integration user must be given View permission to the records though Matching Sharing Rules or Custom Sharing Rules if the events are to be synced with Outlook Integration.

1. Select the **Admin** tab for the permission set.
2. Grant Read, Create, and Edit permission for **Objects**, found under the Configuration section of the Admin tab.
   ![](../../Resources/Images/SchedulingPlanning/CallPlanning/ObjectsPermission.png)

1. Select the checkbox for the **Manage User Object** setting, found under the Security section of the Admin tab.
   ![](../../Resources/Images/SchedulingPlanning/CallPlanning/MangeObjectPermission.png)
2. Select the **Application** tab for the permission set.
3. Select the checkbox for the **Access API** setting, listed in the API row.
4. Navigate to **Business Admin > Objects > user\_territory\_\_v**.
5. Create a **user\_territory\_\_v** record for the integration user and assign the integration user to the root territory in the Vault.
6. Select the **Outlook Integration Administration** tab.
7. Enter the integration user's Vault CRM credentials on the **Outlook Integration Administration** page, and select Save.

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

Legacy Service Center integration users require the following permissions:

* Received Email (received\_email\_\_v) object:
* Object Permission: Create, Read, Edit
* Object Types: service\_center\_\_v,
* All Object Fields: Create, Read, Edit
* Application Permissions:
* Access API
* File Staging: Access

### Switching to the Core System User as

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

Admin users must manually switch Microsoft Outlook integrations to use the Core System User to eliminate the need to manage a dedicated integration user.

System Users are created in Vault CRM instances and managed by Veeva for integration purposes. By default, these users are assigned the appropriate permission set. Customers cannot update the permission set.

By default, only a subset of external\_calendar\_\_v and external\_calendar\_event\_\_v fields are synced from Microsoft Outlook to My Schedule. In order to sync additional data from Microsoft Outlook, admins must define additional fields before manually switching to the Core System User. See [Integrating My Schedule and Microsoft Outlook Calendars](../CallPlanning/Scheduling/OutlookIntegration.htm#CoreSOU) for more information.

To switch to the Core System User:

1. Navigate to **CRM Setup > Outlook Integration Administration**.

   ![](../../Resources/Images/Integration/Intune/SwitchOutlook.png)
2. Select **Switch to System-Owned User**.

   Switching to the Core System User is permanent. Once an admin selects this button and confirms the switch, they cannot return to using the integration user to manage permissions.

   ![](../../Resources/Images/Integration/Intune/ConfirmOutlookSwitch.png)
3. Select **Continue** to confirm the switch.