As a Trust Center Pro customer, you can connect Salesforce to streamline document access requests with Drata. This guide provides what is needed for Drata to search Salesforce for an NDA.
For more information about streamlining your document access request, refer to Streamline your documentation access request.
Prerequisite
To utilize Salesforce within Trust Center, you must have one of the following Salesforce packages: Pro Suite, Enterprise, Unlimited Edition, or Einstein 1 Sales.
This is due to the way Salesforce manages their Web Services API.
To determine which Salesforce package you are currently on, contact Salesforce support directly.
Ensure that you have connected Salesforce (Customer Relationship Management connection type) to Drata.
Utilize Salesforce
Navigate to Drata's Trust Center page and select the Settings button.
Scroll down to the Document access management section and select the Edit icon.
Within the Search CRM for existing NDAs section, select the desired option.
Do not search CRM for existing NDAs
Drata does not search for the presence of an NDA on an account record.
The document request workflow will default to the selection you made under the “Set up preferences for Trust Center document access” section.
Will display relevant information that has been retrieved from opportunities in the CRM that match the request.
Automatically search for NDAs but require approval for requests
Drata searches your CRM for a matching account/opportunity and an existing NDA when a document access request is made.
If a match is found, the customer/prospect is not required to sign a new NDA.
You will receive the access request and must manually approve or deny it.
If no matching account/opportunity and NDA are found, Drata defaults to the selection you made under the “Set up preferences for Trust Center document access” section
Automatically approve if NDA is found
Drata searches your CRM for a matching account/opportunity and an existing NDA when a document access request is made.
If a match is found, the customer/prospect is not required to sign a new NDA.
The request is automatically approved, and the documents are provided immediately.
If no matching account/opportunity and NDA are found, Drata defaults to the selection you made under the “Set up preferences for Trust Center document access” section
Enter the required fields:
NDA field name: Enter the field or custom field in Salesforce that Drata can use to confirm if there is an NDA in place.
To identify the correct field, you can consult your Salesforce administrator or refer to your internal documentation for a list of available field names.
NDA field value: Enter the expected or desired value that is returned when we query for the NDA field name.
For example, if the response is a Boolean, enter 'True' if the desired outcome is true and 'False' if the desired outcome is false.
If the entered NDA field name or NDA field value receives an error, it is because Drata was unable to search or validate the fields you entered. You can verify the configuration with your Salesforce administrator to ensure the correct fields and values are being used.
Example scenario: Verify if the NDA is on file
In this example, we will verify if the NDA checkbox field, 'NDA_Checkbox__c', is checked (true). If it is true, Drata can verify that an NDA is on file.
To do this, we will search for accounts where the 'NDA_Checkbox__c' field is checked. This is a custom checkbox field created in Salesforce. You can learn more about custom fields in Salesforce at Create Custom Fields and Custom Field Types.
Since the “NDA_Checkbox__c” field is a checkbox, it will either return True or False.
Therefore, we want the NDA field value to be set to True. This allows Drata to verify if an NDA is on file by checking whether the "NDA_Checkbox__c" field in Salesforce is checked.
To recap, based on the example scenario:
NDA field name: NDA_Checkbox__c
NDA field value: True
Search for Deal Value within Salesforce
You can also specify the field we use to search for the Deal Value if you have a custom field for the value of your contracts. Reach out to your Salesforce administrator to ensure the correct fields and values are being used.