For simplicity, we recommend that the user connecting to Salesforce be given the following permissions:
Recommended Salesforce permissions for the MadKudu User
API Enabled - Access any Salesforce.com API
Lead: Modify All - Create, edit, and delete all lead data, regardless of sharing settings.
Contact: Modify All - Create, edit, and delete all contact data, regardless of sharing settings.
Account: Modify All - Create, edit, and delete all account data, regardless of sharing settings.
Opportunity: Modify All - Create, edit, and delete all opportunity data, regardless of sharing settings. If not possible, we need at least read on all opportunity data to train the models
Opportunity History: Read all data. This is used to train the models
Opportunity Field History: Read all data. This is used to identify at risk opportunities
Campaigns: Read all data. This is used to feed into the models
CampaignMembers: Read all data. This is used to feed into the models
Task: Read all data. This is used to feed into the models
Lead and Contact History: Read all data. This is used to train the model (find which leads became an SQL before going to nurture…)
[Username/Password only] Api Only User - Access Salesforce.com only through a Salesforce.com API.
[Username/Password only] Password Never Expires - Prevent the user’s password from expiring.
If you prefer more fine-grained settings, You may restrict permissions to:
Required Salesforce permissions for the MadKudu User
API Enabled - Access any Salesforce.com API
Lead/Contact/Account/Opportunity: Read all data, modify the MadKudu fields.
Lead/Contact : Create (see: Madkudu’s contact discovery)
All other above fields: Read all data.
Namely: Opportunity History/Lead History/Contact History/Campaigns/CampaignMembers/Task
Opportunity Field History: Read all data (if you are expecting to identify at risk opportunities with Madkudu)
[Username/Password only] Api Only User - Access Salesforce.com only through a Salesforce.com API.
[Username/Password only] Password Never Expires - Prevent the user’s password from expiring.
Where do I check these permissions?
To find out whether or not your user has those permissions,
Go into the Salesforce “Setup” section.
Go to the Users section and click on the “profile” of the user you want to check permissions for.
Scroll down the the Administrative permissions section and make sure the proper settings are checked.
This user will be used for the following
read data from Salesforce (leads, contacts, accounts, opportunities, users and changes)
create data in Salesforce (leads, contacts) from MadKudu Sales Copilot (see Contact Discovery)
update information in Salesforce
FAQ
Can I restrict what fields you can access on Lead/Contact/Account?
Yes. If your Contact/Lead/Account contains HR data, or anything you would like to restrict access to, you can restrict access to only the "relevant" fields on those objects. In this scenario, please contact your Customer Success Manager to decide what fields to give access to.
Does MadKudu ever creates records in Salesforce?
Yes. MadKudu creates new leads or contacts when a Sales user clicks on "add to salesforce" button in MadKudu Sales Copilot. It can be done from the Users widget in Copilot when records are showing up from your other systems and are not yet in Salesforce or from the Contact Discovery widget in Copilot, allowing our users to find additional contacts in accounts they research. For more information, please go check our integrations with Apollo , ZoomInfo or Cognism
MadKudu needs the ability to write in the following Lead / Contact fields
LastName
Title (if available)
Phone (if available)
LeadSource = MadKudu
AccountId (for Contact object)
Company (for Lead object)
Does MadKudu ever deletes records in Salesforce?
No, MadKudu does not delete recrods from your Salesforce instance