Use this guide to understand how to install and configure the Crossbeam managed package for Salesforce, which includes "Crossbeam Copilot" (a Lightning Web Component) and "Crossbeam Ecosystem Overlap" (a custom object).
Before you begin
👋 Hello there! This guide is written for Salesforce Administrators / RevOps teams. You'll use this guide to install and configure Crossbeam's Salesforce integration.
The integration includes:
A Lightning Web Component (Crossbeam Copilot), placed on a variety of Salesforce Lightning pages to bring the partner ecosystem directly to your GTM teams.
A custom object (Crossbeam Ecosystem Overlap), which receives data from Crossbeam so your GTM teams can enrich Salesforce reports and dashboards with partner insights.
Get started by reviewing the overview and user requirements below.
What's in this guide?
Install the managed package in Salesforce: to get the Lightning Web Component and custom object into your Salesforce environment.
Then, hook it up to your Crossbeam account.
Configure the integration in Crossbeam: to choose the data that is pushed from Crossbeam to the Salesforce custom object and enable the push.
Assign permission sets in Salesforce: to control who can access the component and/or the custom object.
Place the component on Salesforce page layouts: to define where your team will go to see and interact with Crossbeam Copilot.
Crossbeam user requirements
You'll need a Crossbeam user seat with the following roles :
Full Access Role: Admin
Sales Role: Manager
Review your seat assignment by visiting the Team page in the Crossbeam web app:
Keep your Crossbeam login credentials handy, you'll need them to authenticate the connection between Salesforce and Crossbeam!
Salesforce user requirements
You'll need some Salesforce permissions to be able to complete the installation. One is a permission set that comes with our managed package (called Crossbeam Setup User), the others are standard Salesforce permissions for users configuring managed packages/integrations:
Users setting up the Lightning Web Component ("Crossbeam Copilot") need:
the
Crossbeam Setup Userpermission assigned to their user profile
Users setting up the Custom Object ("Crossbeam Ecosystem Overlap") need:
the
Crossbeam Setup Userpermission assigned to their user profileVisualforce Page Access enabled
Read access to the Account and Lead objects
For more details on managed packages, including required user permissions and installation types, review Salesforce's documentation "Install a Package."
Installing the managed package
Navigate to Crossbeam's Salesforce AppExchange listing and click the Get It Now button. If you are not already logged into the Salesforce instance you wish to install the package into, Salesforce will prompt you to log in. Once logged in:
Select Install for Admins Only: this option allows for controlling access and permissions after the package has been installed.
Then, click the Install button:
⚠️ if you select "Install for All Users," the permission sets that come with the managed package will not function properly: you won't be able to control exactly which users can see Crossbeam data and the actions they are able to take.
Approve Third-Party Access by ticking the checkbox and clicking the Continue button:
Third-Party access must be approved to continue with the installation and use the Crossbeam Integration in Salesforce. The third-party access is used for:
api.crossbeam.com - getting Crossbeam data
api.segment.io - reporting on usage
auth.crossbeam.com - authenticating your Crossbeam users
login.salesforce.com - authenticating your Salesforce access for data
sales-backend-api.crossbeam.com - getting Crossbeam for Sales data
sentry.io - reporting on errors
test.salesforce.com - sandbox testing
Connecting to your Crossbeam account
Now that the package is successfully installed, you'll need to connect it to your Crossbeam account.
Assigning the "Crossbeam Setup User" permission set
The permission set named Crossbeam Setup User gets installed as part of the managed package. Be sure to assign it to yourself in order to complete the setup steps:
Accessing the Crossbeam Setup App
Navigate to Salesforce App Launcher and search for "Crossbeam" to access the Crossbeam Setup App:
Click the Get Started button:
Completing the Setup Steps
When completing the 3 setup steps outlined below, be sure to click the "Next" button until you see and click the final "Finish" button.
Step 1: Outbound Connection
This part of the Crossbeam Setup will validate access to your Crossbeam account and allow Crossbeam data to be viewed in Crossbeam Copilot. Have your Crossbeam login credentials handy.
Click the Validate button:
A new window will pop up asking for Crossbeam login credentials:
Log in with your Crossbeam username and password (or click "Log in with Google" if you used Google as your auth method when registering your Crossbeam account).
If your Crossbeam account has SSO enforced, be sure to log in as your SSO exception user.
Click the Next button:
Step 2: Crossbeam Organization Selection
If you successfully authenticated your Crossbeam account in the previous step, this screen will display the name of your Crossbeam account. Users with access to more than one Crossbeam account will see all of their accounts displayed.
Select the Crossbeam account you are connecting to this Salesforce instance:
Click the Next button.
Step 3: Inbound Connection
This part of the Crossbeam Setup will generate a refresh token that allows Crossbeam to share information with your Salesforce organization.
Click the Authorize button:
A new Salesforce approval window may pop up. If so, click to approve/confirm.
Make sure the connection status changes from "Not Connected" to "Connected."
⚠️ If you are using an Integration User, make sure you are logged in directly. If you use Salesforce's "login as" functionality, an Insufficient Privileges error will display.
Click the Finish button:
You should see a successful System Connections screen:
Configure Trusted URLs
For advanced functionality of Crossbeam Copilot such as access to the "Plays" and "Contacts" tabs, Crossbeam must be added as a New Trusted URL in Salesforce. This will allow Copilot to load resources contained in <iframe> elements from this specific trusted URL only.
Navigate to Setup, click the Trusted URLs tab (under Security header)
Click the New Trusted URL button:
Complete the Trusted URL Information section with the following:
API Name: Crossbeam
Complete the CSP Settings section with the following:
CSP Context: Lightning Experience Pages
CSP Directives: frame-src (iframe content)
Click the Save button.
Navigate to Crossbeam Setup to verify both System Connections and Configure Trusted URLs are marked as complete:
Enable & Configure Push to Crossbeam Ecosystem Overlap Custom Object
Navigate to the Crossbeam Web App and access the Integrations page.
Find the "Salesforce Custom Object" tile and click the Install button:
In the window that pops up, click New authentication:
Click the Create button:
A Crossbeam login window will appear, log in with your Crossbeam credentials.
Click the Next button:
Click New authentication:
Click the Create button:
A Salesforce login window will appear, log in with your Salesforce credentials.
Click the Allow button.
Click the Next button:
In the previous steps in this installation guide, you installed the Salesforce package. No further action is required here. Click the Next button:
Click the Finish button:
On the following screen:
(Optional) Customize what data is pushed:
Review the "Customize Data in Push" section. By default, all your populations and all your partners' populations are selected. Remove any populations you do not want to push to Salesforce.
Don't worry: you can change your mind - if you come back to this screen and de-select a population after it has already pushed in, it will be deleted from the custom object in Salesforce on the next sync cycle.
Review the "Push opportunity data" setting. Turn this on to allow for more flexible reporting in Salesforce: when this setting is on, Crossbeam Ecosystem Overlap records will be created for every Opportunity with a partner overlap. This will allow your Salesforce users to run reports utilizing the Opportunity object and useful Opportunity fields.
Keeping this off can help reduce volume of data being pushed in.
Slide the "Enable Data Push" toggle to ON then Click the Save Changes button:
Return to the Integrations page at any time to modify these settings:
Keep in mind that when you add new partners, or when partners share new populations with you, additional records may push into the custom object.
Assigning permission sets
The Crossbeam managed package comes with a number of different permission sets so you can control exactly which users can see Crossbeam data and the actions they are able to take.
We recommend assigning "Crossbeam Account User" and "Crossbeam Report User" to your entire team. This allows them to interact with Crossbeam Copilot, and enrich Salesforce reports and dashboards using Crossbeam data.
Administrative Permissions:
Crossbeam Setup User: full access for an administratormust be assigned to the user installing or reauthorizing the integration
grants admin access to the Lightning Web Component (Crossbeam Copilot)
grants write access to the "Crossbeam Ecosystem Overlap" custom object
Lightning Web Component (Crossbeam Copilot) Permissions:
Crossbeam Account User: enables access to the Crossbeam CopilotFull Access: Users with a paid Crossbeam Core or Sales seat will have full access to the Crossbeam Copilot, including the ability to see data partners have shared.
Starter Access: Users without a paid Crossbeam Core or Sales seat will see a high level overview.
Crossbeam Widget Viewer:grants access to Crossbeam Copilot but disables any clickable buttons
users will not be able to access data shared by partners or initiate conversations
Custom Object Permissions:
Crossbeam Report User: enables access to the custom objectgrants access to the "Crossbeam Ecosystem Overlap" custom object
allows users to build Salesforce reports and dashboards with Crossbeam data
Placing the Lightning Web Component (Crossbeam Copilot)
The Crossbeam Copilot component may be placed on lightning page layouts for Account, Opportunity, Contact, and Lead records.
We recommend placing the Crossbeam Copilot on Account and Opportunity record pages, in a conspicuous location.
This example will show you how to place the Crossbeam Overlaps component on an account record page:
Navigate to Setup, click the Object Manager tab (under Objects and Fields header)
Click on Account
Click on Lightning Record Pages
Click Default Accounts (or the account record layout relevant to you)
Click the Edit button
In the subsequent "Lightning App Builder" page, on the left hand navigation bar, scroll down to the "Custom - Managed" section
Click and drag the Crossbeam Copilot component, placing it in the desired location on your page layout:
Click Activation -> Set as Org Default -> Save
Consider adding visibility filters to the component if you don't want it to appear on the page for certain user roles, for example. More on component visibility here.
Frequently Asked Questions
How can my team run reports on Crossbeam data?
The managed package comes with several standard report types. Ensure that your team has the Crossbeam Report User permission set assigned for the reports to be accessible.
To run reports,
Navigate to Reports -> New Report
In the subsequent "Create Report" screen, make sure you are in the "All" Category on the left and type "Crossbeam Ecosystem" into the search bar:
Select the desired report type and click the Start Report button
Navigate to the "Filters" tab of the report and select
All crossbeam ecosystem overlapsandAll Time:
Continue building out your report with the relevant columns and filters
What are best practices for running reports on Crossbeam data?
Navigate to the Outline tab and add the columns that are most relevant for your team. We recommend adding Partner Name next to Partner Standard Populations. Consider adding your Account Owner field as a row group.
Expand the "Fields" ribbon on the left hand side to see all the fields you can add from your Account object and your Crossbeam Ecosystem Overlap object:
🔎 A best practice is to narrow in on a specific use case and get as granular as possible with your filters.
For a report focused on driving net new pipeline, filter out everything except for where your cold prospects are existing customers of your partners.
Navigate to the Filters tab and apply the following filters:
Standard Populationsequals ProspectsPartner Standard Populations equals Customers
In this example, rows are grouped by Account Owner. We can quickly see Sales reps Brandon and Sara have cold prospects that can be warmed up with help from partners Bozala, Surfzer, and Yaarde.
Add columns Partner Record Owner Name and Partner Record Owner Email to make rep-to-rep collaboration easy.
Save your report and consider adding it to a Public folder. Encourage your team to access the report and play around with it, cloning it and applying their own filters.
Ready-to-Use Salesforce Reports are automatically created when the Crossbeam for Salesforce Package is installed in your Salesforce.
Learn more here.
Click here to build the Crossbeam 360 Dashboard.
What should Crossbeam Ecosystem Overlap record pages look like?
Organize the way data is presented in a Crossbeam Ecosystem Overlap record so it's easy for your team to understand.
In Salesforce Setup, navigate to Object Manager > Crossbeam Ecosystem Overlap. Select "Page Layout" from the left hand navigation bar and click "Crossbeam Ecosystem Overlap Layout" to enter the configuration page.
Consider organizing "your" information on one side and "your partner's" information on the other:
In this example, the left side of the overlap detail will show your Account and/or Opportunity the Crossbeam Overlap is associated with. It will also confirm which of your Standard or Custom Crossbeam populations this record resides in. The right side will tell you which partner it matched with, the partner population, the partner account owner detail (if this information was shared with you), and the name of the account as it appears in the partner's dataset. The bottom shows the timestamp of when the overlap was created, and when it was modified.
What are the custom object fields and what do they mean?
Field Label | Brief Description |
Account | Identifies the Salesforce account record associated with the overlap. |
Created By | Identifies the Salesforce user creating the overlap record - this will usually be your Salesforce Admin or user that installed the integration. |
Crossbeam EID | For Crossbeam housekeeping purposes: this unique identifier is used as part of our process to push records into your Salesforce environment. |
Last Modified By | Identifies the Salesforce user modifying the overlap record - this will usually be your Salesforce Admin or user that installed the integration. |
Lead | Identifies the Salesforce lead record associated with the overlap. |
Opportunity | Identifies the Salesforce opportunity record associated with the overlap. |
Overlap Name | For Salesforce housekeeping purposes: this unique identifier can be clicked by a user (e.g. in a report or related list) to be taken to the full Crossbeam Overlap record. |
Owner | Identifies the Salesforce owner of the overlap record - this will usually be your Salesforce Admin or user that installed the integration. |
Partner Name | The name of the Partner (as it appears in Crossbeam) that the account or lead matched with. |
Partner Populations | The name of the Partner's Custom Population that the account or lead matched with. |
Partner Record Name | Data being shared with you by your partner: the name of the overlapping account or lead as it appears in your partner's Data Source. |
Partner Record Owner Email | Data being shared with you by your partner: the email address of the Account Owner for the account or lead. |
Partner Record Owner Name | Data being shared with you by your partner: the name of the Account Owner for the account or lead. |
Partner Record Owner Phone | Data being shared with you by your partner: the phone number of the Account Owner for the account or lead. |
Partner Standard Populations | The name of the Partner's Standard Population that the account or lead matched with. |
Partner Record Country | Data being shared with you by your partner: the country of the partner's account or lead. |
Partner Record Employees | Data being shared with you by your partner: the number of employees in the partner's account or lead. |
Partner Record Industry | Data being shared with you by your partner: the industry of the partner's account or lead. |
Partner Record Type | Data being shared with you by your partner: the type of the partner's account or lead. |
Partner Record Website | Data being shared with you by your partner: the website of the partner's account or lead. |
Partner Record Owner Title | Data being shared with you by your partner: the job title of the partner's account or lead owner. |
Populations | The name of Your Custom Population (as it appears in Crossbeam) that the account or lead matched with. |
Standard Populations | The name of Your Standard Population (as it appears in Crossbeam) that the account or lead matched with. |