The Salesforce integration is available for customers on the Enterprise plan and is a great way for your Sales team to stay up to date and never leave the platform they're used to. The integration allows you to:

View SafeBase prospect and customer activity directly in Salesforce without having to log into SafeBase
Allow for existing customers in Accounts to be automatically approved in SafeBase without manual approval

If you are looking to install our Salesforce Managed App, please find instructions here: https://help.safebase.io/en/articles/6830596-salesforce-managed-app-setup-guide

Please message our live chat or email support@safebase.io if you would like to enable Salesforce for your organization. Note that this is currently only available as a part of our Enterprise plan.

The videos below discuss the content outlined in this article. You will see what the activity sync and auto approval processes look like in a Salesforce demo environment.

OAuth Connection Setup

Configuring the Salesforce integration requires the Admin role in SafeBase. Click on the Settings tab in the SafeBase app and scroll to the Integrations section. Click Configure next to Salesforce.
Connect SafeBase to Salesforce: A Salesforce user with permissions to connect to external applications is required for the initial connection. After clicking on the Configure button there should be a modal with an option to enable the integration. We currently support integrations with both production and sandbox Salesforce accounts: select your desired Account.

Permissions

Many customers choose to create dedicated service accounts for the SafeBase integration. The account will need the following permissions:

Leads
- Read and write access if you would like for Leads to be created through this integration if neither the Contact or Account exist in Salesforce. If you would like to use the custom Lead Source option, ensure that this is a field that can be written to.
- Fields
  - Email
  - Id
  - AccountId
  - OwnerId
Accounts
- Read and write access
  - We use read access to see if Accounts already exist. For write access, we do not create new Accounts, but do write to the Activity Timeline and can potentially associate Contacts with Accounts.
- Fields for Accounts
  - Id
  - OwnerId
  - Name
  - Website for tiebreaking
  - LastModifiedDate for tiebreaking
  - Any existing NDA field that will be used for NDA override
  - A custom NDA field if you would like for SafeBase to write to this field once an NDA is created through SafeBase
  - A custom field if you would like for SafeBase to indicate how many contacts were invited to SafeBase
- Fields for Tasks
  - Assigned To
  - Status
  - Subject
  - Name
  - Due Date
  - Related To
  - Priority
  - Created By
  - Last Modified By
  - Comments (may also appear as Description in your SDFC instance)
  - Record Type (if required by your SFDC instance)
Contacts
- Read access for auto approve
- Write access if you would like for the integration to be able to create Contacts if it does not already exist in Salesforce.
- Fields
  - Email
  - isDeleted
  - LastModifiedDate
  - Name
  - Id
  - AccountId
  - Record Type (if required by your SFDC instance)
Users
- Read access to User.Id and User.isActive so that we can properly assign Task Owners.
Organization
- Read access to Organization.TimeZoneSidKey if you would like for Tasks to use your Organization's time zone. Otherwise we will default to the time zone of the integration user.
Opportunity (only if custom rules are used. Please contact your CSM for more information about custom rules)
- Id
- Name
- AccountId
- StageName
- IsClosed
- IsDeleted

This user will also need Read access to any additional fields defined in custom rules. Please contact your CSM for more information.

3. Login to Salesforce and allow access to the specified items

4. If the connection was successful, you should see a greyed out "Enabled" button as shown below

5. Toggle the following activities to be synced to Salesforce as Tasks in the Activity feed:

If Leads are linked to Accounts, then the activities will also appear in the Account page.

Activities

SafeBase creates Salesforce Task records for certain activities that happen within the application. All possible Task subjects are described below. Upon initial connection, the default state for all Tasks are off.

Note: Account names need to have an exact match for automatic matching to function properly.

SafeBase - Requested Access: A visitor requested access on your public status page.
- If an individual requests access and there is no existing contact information for the individual in Salesforce, the options for handling this request are:
  - Automatically create a new Contact in Salesforce if there is an existing matching Account (Company Name) but no contact with the requester's email.
    If your SFDC instance requires a Record Type, you can provide the ID here.
  - Automatically create a new Lead if neither an existing matching Contact or Account can be found.
  - Have the Access Request activity be marked as complete automatically.
SafeBase - Account Created: A SafeBase account was created for this Salesforce Account record.
SafeBase - Account Member Added: A new person was given access to this account.
SafeBase - NDA Signed: The NDA process for an account has been completed (either clickwrap or DocuSign). You can optionally choose to write to a Salesforce field called Is_SB_NDA_Done__c if an NDA has been executed through SafeBase. In a future release, we will allow for the ability to sync this NDA status to a custom field.
SafeBase - Status Page View: A visitor viewed a shared status page.
SafeBase - Comment on Status Page: A visitor commented on an item in a shared status page.
SafeBase - File Downloaded: A visitor downloaded a file from a shared status page.
SafeBase - Questionnaire Uploaded: A visitor uploaded a questionnaire on a shared status page.

Note: If your SFDC instance requires a Record Type value, you can enter the ID at the top of the configuration modal. All Tasks created will use this Record Type.

Disabling the Salesforce Integration

If you would like to disable the integration, click on Uninstall at the bottom of the Salesforce configuration modal.

NDA Bypass

After configuring Salesforce, you will also the option to skip the NDA requirement in SafeBase using a custom field. This can be used if NDA status is already tracked in Salesforce. Using this option, you can specify a custom field and value that allows for certain users to skip the NDA process. Users who do not have this value for the custom field can still be approved, but they will be required to complete an NDA if Clickwrap or DocuSign are set as the default option.

Here is a quick video demonstrating the NDA Bypass in action.

This applies to both auto approved requests, and non auto approved requests that we are able to link to a Salesforce account.

Note: You will need to specify the Salesforce API Field Name and not the Field Name you see in Salesforce. Your Salesforce Admin/Architect will be able to retrieve this for you. These values typically end in __c.

If you need additional conditions for NDA Bypass, we can create custom rules for your organization to mix and match AND/OR conditions, along with any standard or custom fields in the Account object. Please contact us for more information.

For example, we can choose to have requests bypass the NDA if a the field NDA Status is not blank. Accounts that have a blank value for NDA Status would still be required to sign your organization's NDA.
- Please see this article for additional details on what is possible with our Rules Engine.

Salesforce Auto Approval

After enabling the Salesforce integration, in the Settings page, you will find new options under Automatically approve access requests.

The Salesforce integration currently has two options for automatic approval:

Contact exists in Salesforce - If this option is turned on, requests will be automatically approved if SafeBase is able to find a Contact that has the same email as the user submitting the request.
1. Please see this video for a quick explanation as to how this option works.
Contact domain exists in Salesforce - If this option is turned on, requests will be automatically approved if SafeBase is able to find a Contact that has the same email address domain as the user submitting the request.
1. Please see this video for a quick explanation as to how this option works, and how it differs from the above.

Note: These options operate using OR logic, meaning if both of them are enabled, only one of the conditions needs to match for the approval to be automatic.

If you need additional conditions for auto approval, we can create custom rules for your organization to mix and match AND/OR conditions, along with any standard or custom fields in the Account object. Please contact us for more information.

For example, we can create a custom rule to auto approve if a Customer Status field is set to Customer. Accounts with Customer Status set to Prospects would not be auto approved and would require manual approval.
- Please see this article for additional details on what is possible with our Rules Engine.

Troubleshooting

Our Salesforce integration is designed to be self-serve for standard Salesforce configurations. Please contact us by messaging our live chat or emailing support@safebase.io to let us know if you run into issues with the integration or if there are certain workflows that you would like to be added.
Verify that Account names are spelled exactly as they are in Salesforce because automatic matching requires exact spelling matches.
- Ex: "Company Inc." will not match with "Company Incorporated"
We use a third party service called Paragon to assist with certain parts of our integration. If you run into issues, please verify that your Salesforce admin has not inadvertently blocked Paragon in your Salesforce environment.
If auto approving seems to be failing, try running some tests using email domains other than Gmail or your own company's domain. Sandbox environments with many Account records with the same domain likely will result in conflicts in which our system is unable to determine which Account to associate the request with. If needed, you may coordinate testing with us, as we have several email distinct testing domains that can be used:
- For example, you can create test Contacts using the following emails: