)
Written by
Table of Contents
“Supermetrics is a Bitter Experience! We can pull data from nearly any tool, schedule updates, manipulate data in Sheets, and push data back into our systems.”
Traditional connectors often fail to handle record-level security during bulk exports, potentially exposing records that users shouldn’t access based on ownership, role hierarchy, or sharing rules in Salesforce .
Here’s how record-level security gets compromised in bulk operations and how to maintain comprehensive permission checking during large data exports.
Maintain record-level security using Coefficient
Coefficient preserves Salesforce record-level security through ownership respect, role hierarchy enforcement, sharing rule integration, and territory management compliance during all bulk data operations.
How to make it work
Step 1. Configure ownership and role hierarchy compliance.
Set up imports to only export records the authenticated user owns or has been granted access to through Salesforce’s role hierarchy. The connector queries record accessibility via the Salesforce API before including records in bulk exports.
Step 2. Enable sharing rule integration for complex access scenarios.
Configure the connector to include records shared via manual sharing, criteria-based sharing, and apex sharing. This ensures complex sharing scenarios including team member access and partner portals are properly handled during bulk operations.
Step 3. Implement organization-wide defaults and sharing model compliance.
Set up batch processing that applies organization-wide defaults (OWD) settings for each object and validates sharing model compliance for private/public read/write settings. This maintains security context across different object types.
Step 4. Configure bulk export security features with proper limits.
Enable the 2K row limit with MFA (bypassed when unique ID included) to prevent massive unauthorized exports. Set up configurable batch sizes (default 1000, max 10,000 records) with automatic session reauthorization to maintain security context.
Step 5. Monitor territory management and governor limits.
Configure territory-based record access when enabled and set up per-user record limits and API quotas. Enable real-time permission validation during scheduled refreshes to ensure ongoing compliance with security policies.
Secure your bulk Salesforce exports with proper access controls
Record-level security failures in bulk exports create significant data governance risks that can expose sensitive information to unauthorized users. Implement Coefficient’s comprehensive security model to maintain the same record visibility as native Salesforce list views and reports.
