Customers that do not want to authenticate their Bedrock Data Microsoft Dynamics 2016 integration using a System Administrator can follow the screenshots below to create a new role with the minimum permissions needed for the Bedrock sync to function.
Disclaimer: Note that if you use a Custom User role instead of a System Administrator, you are responsible for ensuring the role's permissions remain up to date with any new features that Bedrock's product team releases for the Microsoft Dynamics Connector. Often new features require access to new API endpoints and if the role that is authenticating the integration does not have these permissions, it can lead to your integration breaking.
You need to make sure that the role's permissions are identical to what you see in the screenshots below.
Dynamics 9.0 Additional Permissions in addition to the below:
- Currency (READ)
- Team (READ)
- Campaign (READ)