Skip to main content
Installation Guide: Crossbeam for Salesforce

Installation details for our Salesforce Integration: Crossbeam Copilot and Crossbeam Overlaps custom object.

Gdaly Berlin avatar
Written by Gdaly Berlin
Updated over a week ago


To ensure clarity and easy of use, we have updated this article.

Please click here to access the current version.

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 Overlaps" (a custom object).

In this article:

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:

✍️ Note

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:

  • - getting Crossbeam data

  • - authenticating your Crossbeam users

  • - reporting on errors

  • - authenticating your Salesforce access for data

  • - sandbox testing

For more details on managed packages, including required user permissions and installation types, review Salesforce's documentation "Install a Package."

Connecting to your Crossbeam account

Salesforce User Requirements

Users completing the Crossbeam Setup steps detailed below must have specific permissions and object access:

  • Users validating the Lightning Web Component (Crossbeam Copilot for Salesforce) need:

    • the Crossbeam Setup User permission assigned to their user profile

  • Users authorizing the Custom Object ("Salesforce push") need:

    • the Crossbeam Setup User permission assigned to their user profile

    • Visualforce Page Access enabled

    • Read access to the Account and Lead objects

✍️ Note

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 3 Crossbeam Setup Steps

The steps detailed below establish a connection between your Crossbeam account and your Salesforce instance.

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 for Salesforce. Have your Crossbeam login credentials handy.

The Crossbeam user you are logging-in as must have the "Admin" role for Crossbeam Core and the "Manager" role for Crossbeam for Sales.

  • 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 authorize Crossbeam to push data to the "Crossbeam Overlaps" custom object.

✍️ Note

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 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."

  • Click the Finish button.

You should see a successful System Connections screen:

You are now ready to view Crossbeam data in the Lightning Web Component (Crossbeam Copilot for Salesforce) and can enable data to push from your Crossbeam account to the "Crossbeam Overlaps" custom object in your Salesforce instance.

Be sure to assign the appropriate Permission Sets to individual users or user groups in order for them to be able to see and interact with Crossbeam data.

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:

    • Complete the CSP Settings section with the following:

      • CSP Context: Lightning Experience Pages

      • CSP Directives: frame-src (iframe content)

    • Click Save

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 see Crossbeam data in the Crossbeam Copilot for Salesforce, and build Salesforce reports and dashboards featuring Crossbeam data.

Administrative Permissions:

  • Crossbeam Setup User: full access for an administrator

    • must be assigned to the user installing or reauthorizing the integration

    • grants access to the Lightning Web Component (Crossbeam Copilot)

    • grants write access to the "Crossbeam Overlaps" custom object

Lightning Web Component (Crossbeam Copilot) Permissions:

  • Crossbeam Account User: enables access to the Crossbeam Copilot

    • Full 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 object

    • grants access to the "Crossbeam Overlaps" 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.

Did this answer your question?