Salesforce integration requirements

Overview

This article describes what your Salesforce org needs to connect to Opensense. The permissions and configuration depend on which features of the integration you use. Your Opensense implementation team handles the configuration after your requirements are confirmed.

Available on select plans

Salesforce integration is available on select Opensense plans. Contact your account manager to confirm that your plan includes CRM connectivity.

Before you start

You need:

• A Salesforce admin account
• Your Salesforce Instance URL (for example, https://yourcompany.my.salesforce.com)
• The admin email address for your Salesforce account
• API access turned on for your Salesforce org

Use the salesforce.com URL

To find your Instance URL in Lightning Experience, select your avatar, then View Profile. You can also find it in Setup: search for My Domain, and use the Current My Domain URL. Use the *.salesforce.com version of the URL, not *.lightning.force.com.

What you can use this integration for

The Opensense Salesforce integration supports three independent use cases. You can use one, two, or all three, depending on your organization’s needs.

Recipient-based banner targeting

Opensense queries your Salesforce CRM data to decide which banner campaign content to serve on outbound emails. Banners can target the recipient's contact, account, lead, or opportunity attributes. This is the most common use of the Salesforce integration.

Salesforce email signatures

For teams that send email directly from Salesforce, Opensense applies centrally managed signatures to those emails. Opensense pushes a Plain Text Block (PTP) to each user's native Salesforce email signature field. It then processes outbound emails through its relay, to add the full signature before delivery.

User directory sync

Opensense pulls your Salesforce user records as the source of truth for sender signature fields: name, title, phone, department, and similar data. This is useful for organizations that manage employee data mainly in Salesforce, rather than in a directory like Microsoft 365 or Google Workspace.

Required for everyone: the AppExchange package

Whichever features you use, install the Opensense managed package in your Salesforce org from the AppExchange. Your implementation team gives you the listing link. After installation, configure the connected app so that all user profiles have access.

The integration is installed in your production Salesforce org.

Need a sandbox?

If you need a sandbox configuration, give Opensense that information during implementation.

To complete the configuration, your Salesforce admin needs access to Manage Connected Apps (in Setup, under Apps > Connected Apps), to authorize the Opensense app and assign profiles.

Permissions by use case

The object and field permissions depend on which features of the integration your organization uses. Find your use cases in the columns, then review their sections below.

Object or setting	Banner targeting	Salesforce signatures	Directory sync
Contact, Lead, Account, Opportunity	Read	—Not needed	—Not needed
User	—Not needed	Read and edit	Read
User: Email Signature field	—Not needed	Write	—Not needed
User: sender data fields	—Not needed	—Not needed	Read
Email Delivery Settings and Deliverability (Setup)	—Not needed	Admin access	—Not needed

Field-level security applies to every object

If the admin account used for the integration can’t see a field, Opensense returns a blank value for that field, even when it has object-level read access.

Banner targeting permissions

Opensense needs read access on the Salesforce objects it queries for targeting. At minimum, it needs read access on the objects that your banner campaigns target:

Contact

Contact-level recipient targeting

Lead

Lead-level recipient targeting

Account

Account-level ABM targeting

Opportunity

Deal stage targeting

Read-only access

This access is read-only. Opensense doesn’t create, update, or delete CRM records.

To find the Salesforce field API names to use for targeting, see Finding Salesforce field API names to query in Opensense.

Salesforce signature permissions

To apply Opensense signatures to emails sent from Salesforce, your Salesforce admin needs two more areas of Salesforce Setup:

Email Delivery Settings

To route email through Opensense, on the Email Relays page. Salesforce also needs an email domain filter (Email Domain Filters) for a relay to work.

Deliverability

To update the email delivery configuration to allow relay processing.

Opensense also needs read and edit access on the User object, specifically write permission on the native Email Signature field. This is how Opensense pushes the Plain Text Block to each user’s Salesforce signature, so that only the Opensense-managed signature is in use.

The only write access

Write access on the User Email Signature field is the only place in the Opensense integration where data is written to your Salesforce org. All other access is read-only.

Directory sync permissions

To sync sender data, Opensense needs read access on the User object, and field-level read access on these fields:

• First Name, Last Name, Email
• Title, Department, Company Name
• Phone, Mobile Phone

Active users only, by default

This access is read-only. By default, Opensense syncs active users only. Your Opensense admin can turn on inactive user sync in domain settings, if needed.

What’s next

• Finding Salesforce field API names to query in Opensense
• Assigning Opensense tags with Salesforce Flow Builder
• Setting up your email signature in Salesforce

For further help, contact Opensense Support at help@opensense.com.