Pitchly respects the permissions of the connected Salesforce user. Any object, field, or record visibility configured in Salesforce will apply to data accessed by the Pitchly integration.
However, some organizations may want additional control over which Salesforce records are synchronized to Pitchly. This article outlines recommended approaches for limiting synced data beyond standard Salesforce permissions.
How Salesforce Permissions Work with Pitchly
When Pitchly connects to Salesforce, all API requests run using the connected Salesforce user’s permissions.
This means:
If the user cannot access an object, Pitchly cannot access it
If the user cannot view a field, Pitchly cannot retrieve it
If the user cannot see certain records, those records will not sync
Pitchly automatically respects:
Object permissions
Field-level security
Record visibility and sharing rules
Why Additional Filtering May Be Needed
Some Salesforce objects are commonly configured with broad visibility across an organization.
For example:
Accounts
Contacts
Opportunities
In these cases, the integration user may technically have access to more records than should be synchronized to Pitchly.
Organizations often want to:
limit synced records to a specific business unit
sync only records tied to active engagements
restrict records to a particular workflow
exclude internal or sensitive records
To support these use cases, customers may optionally apply additional synchronization filters.
Recommended Approaches
Option 1 (Recommended): Create a “Send to Pitchly” Field
The simplest and most flexible approach is to create a custom Salesforce checkbox field such as:
Send_to_Pitchly__c
Records marked as TRUE can then be included in Pitchly synchronization filters.
Example:
SELECT Id, Name
FROM Account
WHERE Send_to_Pitchly__c = TRUE
Benefits
Easy for administrators to manage
Transparent and auditable
Consistent across Salesforce objects
Simple to troubleshoot
Does not require complex Salesforce sharing configuration
Best Practices
Add the field to all objects synchronized with Pitchly
Use Salesforce Flows or automation to populate the field when possible
Clearly document ownership and maintenance rules internally
Option 2: Relationship-Based Filtering
Some organizations prefer to sync records only when they are related to another approved object.
Example:
SELECT Id, Name
FROM Account
WHERE Id IN (
SELECT Position_Company__c
FROM Engagement__c
WHERE Position_Company__c != null
)
This approach is commonly used when:
Accounts should only sync if tied to an Engagement
Parent objects should inherit filtering from child objects
Synchronization should follow existing business relationships
Considerations
More complex to maintain
May require custom SOQL queries
Can behave differently across Salesforce objects
Additional Filtering Examples
Organizations may also choose to limit synchronization using additional query filters such as:
Record Type
Region
Business Unit
Status
Ownership
Custom fields
Examples:
WHERE Region__c = 'North America'
WHERE RecordType.Name = 'Client'
WHERE Status__c = 'Active'
These filters are optional and are applied in addition to Salesforce permissions.
Important Notes
Additional Filters Do Not Replace Salesforce Security
Pitchly can only access records visible to the connected Salesforce user.
Additional filters further narrow the records synchronized to Pitchly.
Effective synchronization logic becomes:
Records visible to the integration user
AND
Additional Pitchly sync filters
Record Visibility May Vary Between Objects
Different Salesforce objects may use different sharing models and visibility rules.
For example:
Engagement records may already be restricted by Salesforce sharing
Account records may be broadly visible across the organization
As a result, some objects may require additional filtering while others may not.
Recommended Integration Strategy
For most organizations, Pitchly recommends:
Creating a dedicated Salesforce integration user
Applying least-privilege Salesforce permissions
Using explicit synchronization filters such as:
Send_to_Pitchly__crelationship-based filters
additional query filters when needed
This approach provides the most predictable and supportable synchronization behavior.
Need Help?
We’d love to hear from you. If you have any feedback on product enhancements or additional questions, email the team at PitchlySupport@pitchly.com.