LyntonWeb’s Standard Dynamics integration with HubSpot requires an integration user in CRM that has read/write capabilities and has Organizational or Business Unit level access. We require read/write capabilities to create and update records within CRM and we require the Organizational or Business Unit level access so our integration has visibility to all data that it does not own. If setting up the integration user with the default System Administrator security role is not possible, another role which gives the integration user the following capabilities is acceptable.


Read/Write capabilities to the following Entities

Account(if applicable)

Contact

Lead

Opportunities(if applicable)

If LyntonWeb is using custom entities in CRM for your integration, the same read/write access will apply.*


The integration user also utilizes the following relationships. These are used to help query related data and typically only requires read access:


Lead:

Lead_owning_user


Contact:

Contact_customer_accounts

Contact_owner_user


Opportunities:

Opportunity_parent_account

Opportunity_parent_contact


Account:

Account_primary_contact

Contact_customer_accounts


Level Access (ability to view all records, not just records owned by the integration user)

  • Organizational Access - This gives the user access to all records in the Organization. Helpful if working with records across multiple Business Units.
  • Business Unit Access - This gives the user access to all records for the Business Unit that the user belongs to. Acceptable if we do not require Org wide record access.

Notes

*Due to the nature of a bi-directional synchronization type of integration, records are being read and updated. We will always verify read/write access to entities not listed as part of our standard integration.