Note: CRM integrations are available on our Grow AI and Scale AI plans. Please contact support if you want to upgrade your plan.
This article covers the permissions and visibility requirements needed for the Turtl integration with Pardot (Account Engagement) and Salesforce.
The integration does not require any Salesforce-specific page layout changes, but the connected user will need the correct permissions in both platforms, as detailed below.
What the integration does
Passes lead capture form data collected in Turtl Docs back to Pardot
Supports bulk creation of personalized Turtl Docs when sending bulk emails via Account Engagement
Surfaces Turtl engagement data within your CRM
Salesforce requirements
For a general overview of how permissions work in Salesforce, see Permissions and Access Settings in Salesforce Help.
User-level permissions
The Salesforce user connected to the integration must have:
API Enabled: Required for API access.
Customize Application or Modify All Data: Needed to automatically create and manage the custom Turtl_Personalized_Doc__c object and its fields via the Metadata API.
Object and field-level security
For more detail on how field-level security works in Salesforce, see Field Permissions in Salesforce Help.
Lead object
Read access: To retrieve lead details.
Edit access: To update the lookup to personalized Turtl Docs.
Fields requiring read access:
Id: Lead identifier.
Name: Lead name.
Email: Lead email address.
Turtl_SFID__c: Custom Turtl ID field, if it exists.
Fields requiring edit access:
Turtl_Personalized_Doc__c: Lookup field for personalized Docs.
Turtl_Personalized_Doc__c custom object
This custom object and all its fields are created automatically by the integration, so no manual setup is required. The connected user will need full CRUD permissions (Create, Read, Edit, Delete) on this object.
Fields requiring read and edit access:
Name
lead__c
doc_id__c
doc_url__c
doc_title__c
pid__c
personalized_cover_image_url__c
personalized_cover_teaser_url__c
personalized_twitter_image__c
personalized_facebook_image_url__c
personalization_tag__c
Note: While no page layout changes are required, we strongly recommend making the relevant fields on both the Lead object and the Turtl_Personalized_Doc__c object visible on the page layouts used by your team.
Pardot (Account Engagement) requirements
Pardot uses role-based access control rather than field-level security. The connected user will need:
Pardot API User: The Salesforce user must have the "Pardot API User" checkbox enabled.
Pardot role: A Marketing, Sales or Admin role, assigned based on the user's function.
Business Unit assignment: The user must be assigned to the correct Pardot Business Unit.
Once API access is granted, the integration automatically reads the following standard Prospect and Visitor fields:
id
email
first_name
last_name
crm_lead_fid
crm_contact_fid
salesforce_fid
lists