Connecting Act-On to Microsoft Dynamics requires a dedicated user account with a specific set of privileges. This article lists exactly which ones Act-On needs so you (or your Dynamics administrator) can set up that connected user correctly.
Why this matters: Grant too few privileges and the connection breaks or silently stops syncing certain records; the list below is the minimum Act-On needs to read and write the data the integration depends on.
Minimum Permissions
- prvReadOrganization
- prvReadList
- prvReadEntity
- prvReadAttribute
- prvReadAttributeMap
- prvReadEntityMap
- prvReadRelationship
- prvReadAccount
- prvWriteAccount
- prvReadOpportunity
- prvReadCampaign
- prvReadLead
- prvWriteLead
- prvCreateLead
- prvReadContact
- prvWriteContact
- prvCreateContact
- prvCreateActivity
- prvWriteActivity
- prvReadActivity
- prvAppendActivity
- prvCreateNote
- prvWriteNote
- prvReadUser
- prvReadTeam
- prvReadField
- prvReadOrder
- prvReadRecordAuditHistory (If audit history is enabled)
- prvReadAuditSummary
- prvReadBusinessUnit
Related to