This is the first article in a series guiding you through everything you need to know to set up, support, and succeed with the Tackle for Salesforce integration.
Preparing to install (You are here)
Before you connect Tackle to your Salesforce account, you’ll need to make sure both your Tackle and Salesforce environments are prepared with the right permissions and settings. Here are four prerequisite steps you’ll need to complete before installing your Tackle for Salesforce package.
Create a Tackle user account for your Salesforce admin
Account privileges required: Tackle administrator
Follow our guide Add or edit users in Tackle to create a new user account, and enter the email address of your Salesforce admin.
Assign your Salesforce admin to a Tackle role with access to your Integrations page, both on your test and production accounts.
Note: The Tackle default role Administrator includes these permissions. However, we recommend using custom roles for most users in your Tackle organization for better control over your account access.
Create or refresh a developer sandbox in Salesforce for the installation
Account privileges required: Salesforce Developer, Developer Pro, or Administrator
You’ll initially install your Tackle for Salesforce integration into a sandbox, which is a safe environment used for testing before making live changes in your production org. To create a clean developer sandbox for the Tackle package installation, follow this guide from Salesforce to create a new sandbox or refresh an existing one🔗.
Connect your Tackle account to the ACE API (AWS Co-sell only)
Account permissions required: AWS administrator
If you plan to use Salesforce to co-sell through the Amazon Partner Network Customer Engagements Program (ACE), you’ll need to connect your Tackle account to the ACE API first. Follow all 8 steps of our guide Connect to AWS Partner Central to complete your AWS co-sell setup in Tackle.
Important:
If you’ve previously connected your Tackle account to the ACE API, we’ve added an additional step, titled Enable Role permissions, with an additional CloudFormation Template (CFT) that you must install for this integration. If you aren’t sure whether you’ve completed this step, open Connect to AWS Partner Central and complete the step titled "Enable Role permissions".