Zendesk for Salesforce integration - Required profile permissions

Return to top
Have more questions? Submit a request

5 Comments

  • Dwight Bussman
    Zendesk team member

    Hi Nevena Imetska

    I suspect that the reason the Domain Mapping field no longer appears is that this was likely a field created by our Legacy Salesforce integration which is currently being deprecated. 

    It should still be possible to map other fields to the Domains organization field

    Hopefully that helps to explain why that field would be absent. If not, I recommend reaching out to our Support team as described in this article to discuss this further in a ticket/on a call/zoom meeting.

    1
  • Dwight Bussman
    Zendesk team member

    PJ Parbhoo

    Thanks for the heads-up. I'm going to reach out to our Developers to see what they intended with these lines in that documentation and get it updated accordingly.

    0
  • PJ Parbhoo

    This does not answer the question. In the article:

    https://support.zendesk.com/hc/en-us/articles/360034751534#topic_mpl_nw4_rjb

     

    the instructions state "Select the Standard User profile". For this profile, object settings cannot be set without "Permission Sets". I think the article needs to be updated with Permission Sets instructions. 

    0
  • Nevena Imetska

    Thank you Dwight Bussman that explains it and I have created a custom field for mapping the domain names from salesforce to Zendesk.

    0
  • Nevena Imetska

    Dwight Bussman

    We were using the data sync with Salesforce successfully and had it setup as per the documentation but after a few tickets had failed to sync we noticed that the configuration for the data sync for accounts, contacts and tickets had been disabled due to an error. 

    We did the configuration again for Contacts and Tickets sync, but we can't do the Accounts sync config because now we don't see the Domain Mapping anymore. We can't see it in the dropdown for mapping the fields in the sync config screen, and we also don't have permissions for it in Salesforce. 

    Any idea what might be the reason since we have not changed any permission settings?

    Thanks, 

    Nevena Imetska

    0

Please sign in to leave a comment.

Powered by Zendesk