Detailed Security Controls

Send2CRM applies best practice security controls within Salesforce. During implementation, we strongly recommend adopting a least privilege approach to configuring permissions. This security principle ensures that both users and systems are granted only the minimum access rights necessary to perform their intended functions, significantly reducing the attack surface and minimizing the risk of unauthorized data access or modification.

Send2CRM's security framework addresses two critical categories of access control within the Salesforce ecosystem:

The first category governs what individual Salesforce users are permitted to do within the system. User permissions are structured across multiple access levels, each tailored to specific role requirements and responsibilities. This granular approach ensures that team members have appropriate access to perform their duties without exposing sensitive data or critical system functions beyond their scope of work.

The second category focuses on the permissions granted to API connections originating from your public-facing website. This is where the principle of least privilege becomes particularly crucial. The API/Integration user should be granted access permissions exclusively to those Salesforce objects that the website integration is expected to read from or update.

For example, typical lead generation implementations using Send2CRM often require access to Lead, Contact, or Opportunity objects to prevent duplicate record creation when prospects submit forms through your website. It is strongly advised against granting broad access to all Salesforce objects. Excessive API permissions can inadvertently expose your organization to risk, as sales and marketing administrators might unknowingly incorporate restricted objects when designing website experiences or automation workflows.

During implementation it’s recommended that the permissions start small and then are added to as new capabilities are used in Send2CRM, rather than starting with everything and reducing permissions later. This API/Integration user is specified as the default record owner of the public site in Salesforce and only requires access to one Apex class for API access.

When freshly installed, Send2CRM does not have access to any Salesforce objects or fields. Following installation access must be granted before it will be able to fully function.

The following table includes an overview of object and field access for each of the Permission Sets that are installed with each of the packages. The permission sets only include objects that are within the Send2CRM packages. Access to other objects like Leads or Contacts are managed separately. The permissions sets that are included will not be made active on any users in the Salesforce organization until they are assigned.

• When using Send2CRM for sales, marketing, or service it’s recommend to assign the Send2CRM User to your teams that require access to analytical data.

• The marketing or sales operations administrators and should have the Send2CRM Administrator and Send2CRM Analytics Administrator permissions sets assigned.

• For API integration the Send2CRM Administrator and Send2CRM Analytics Administrator permission set are required as it needs to be able to read the system configuration and store analytical tracking and insights data.

• For those that wish to make use of the dynamic website content capabilities of Send2CRM assign the Send2CRM Web Content permission set to applicable users including for API integration.