Loading

Account Engagement - Sync Error: "Insufficient access: insufficient access rights on object id:[0031a...]"

Veröffentlichungsdatum: Sep 30, 2025
Beschreibung
This is a common Salesforce connector sync error that can show in Account Engagement. This error means that the connector user does not have enough access to the object. Most likely the connector user will have "View All Records" for Contacts / Leads but not "Modify All Records". When Salesforce syncs to a contact that isn't owned by or isn't shared with the connector user and tries to edit the contact, this error will appear.
Lösung
To fix this issue:

1. Ask a Salesforce Administrator for help:

A) The sync error will reference an object ID. First, see Standard Field Record ID Prefix Decoder to see what the corresponding object is.
We recommend checking the contact / lead permissions for the connector user's Salesforce user profile and allow "Modify All Records", or share the contact / lead (s) in question with Read/Write access.

B) The sync error might not reference an ID at all: "Sync Error: "Insufficient access: insufficient access rights on object id:[]". In this case, please review your Salesforce Org's Organization Wide Defaults to confirm if they are set to "private" for accounts, leads, opportunities, campaigns , or contacts. Even if you put sharing rules and set read/write, this doesn't also include delete/modify all.

For example, if 'Accounts and Contract' Organization Wide Default is set to private and you are using the standard Account Engagement Integration User for the Salesforce Connector, try following these steps:

1. Create a Public Group and add the B2BMA Integration User/Custom connector user to the group.
2. Create a Sharing Rule on the Object with the required criteria.
3. Share with Public Groups > select Group just created.
4. Default Account and Contract Access = Read/Write.

2. In Account Engagement, follow these instructions to clear the sync error on the prospects..

Nummer des Knowledge-Artikels

000383442

 
Laden
Salesforce Help | Article