Skip to main content

Understanding Sharing Settings for Partners

Customize your sharing settings with a specific partner to share more, or less data with your partners.

Written by Joy Rudnick
Updated yesterday

In this article:

Overview

Crossbeam sharing settings allow you to control how much or how little data you share with each of your partners. Since no two partnerships are the same, these tools help you customize access by partner, Population, or preset—all in one place.

The Sharing Hub is the central place to view and manage all of your sharing configurations—by Population, by partner, and across your entire ecosystem—in one consistent experience.


What Are Sharing Settings?

There are four sharing level options in Crossbeam:

Sharing Levels Overview

Sharing Level

What Partners Can See

Best For

All Accounts

All accounts are shared— both overlapping and non-overlapping (Greenfield)

Pipeline generation & discovery

Overlapping Accounts

Only accounts that exist in both you and your partner’s data

Required for account mapping

Account mapping & collaboration

Counts Only

No account details are shared

Only the number of overlapping accounts

High-level visibility

Hidden

Nothing is shared

The Population is completely private

Sensitive or internal-only data

Key Notes

  • All Accounts enables Greenfield sharing, allowing partners to see non-overlapping accounts (not available on the free plan).

    • On Enterprise plans, only admins can configure this setting (others have view-only access)

  • To share a Population externally via Dynamic Shared Lists, the sharing level must be All Accounts or Overlapping Accounts.


The Sharing Hub

✍️ Note

This replaces Default Sharing Settings. Any previous configurations are preserved.


To access the Sharing Hub, Navigate to Data → Sharing Settings

This is your centralized workspace for managing sharing across all Populations.

The main table displays:

  • All Populations

  • Sharing level

  • Field preset applied

  • Using Default count

    • Shows how many partners use the default sharing settings for this Population

Filtering Your View

Use the filter bar to quickly find what you need:

  • Population Type: Customer, Prospect, Open Pipeline, etc.

  • Sharing Level: All Accounts, Overlapping, Counts Only, Hidden

  • Field Presets: Filter by applied presets


Sharing Settings by Populations

Click any Population to open its detail view.

Inside, you’ll see:

  • Partners with Custom Settings (overrides) at the top

  • Partners using Default Settings below

  • Sharing level, field preset, and partner tags per partner

Available Actions

  • ↺ Reset to default: removes partner-specific overrides

  • ↗ Open partner settings: jump to detailed sharing settings

✍️ Note

Bulk updates to default settings do not overwrite partner-specific overrides.


Applying Bulk Changes

Bulk Edit by Population

Navigate to Data → Sharing Settings

(Optional) Use filters to narrow your view:

  • Population type

  • Sharing level

  • Field presets

  • Select the populations you want to update using the checkboxes

  • Click Bulk Edit

  • Choose:

    • Populations

    • Sharing level

    • Field preset

  • Click Save

Recommended:

  • Use All Accounts for pipeline generation

  • Use Overlapping Accounts for account mapping


✍️ Note

Bulk edits update default settings only. Any partner-specific overrides will remain unchanged.


Bulk Edit by Partner

  • Navigate to Data → Sharing Settings

  • Click into a Population to view its associated partners

  • (Optional) Use filters to narrow the partner list:

    • Partner tag

    • Sharing level

    • Field preset

  • Select the partners you want to update using the checkboxes

  • Click Bulk Edit

  • Choose:

    • Sharing level

    • Field preset

  • Click Save


✍️ Note

If you filter by partner tag and make bulk changes, those changes do not apply automatically to new partners added under that tag later. If you add a new partner and tag them, return to the Sharing Hub to apply the appropriate configuration manually.


Sharing Field Presets

Sharing Field Presets let you control which specific fields are shared with your partners. Presets are reusable and especially useful when different partner types require different levels of data access.

Field preset options are only available when the sharing level is set to Overlapping Accounts or All Accounts.

  • To create, apply, or manage a preset:

    • Set the sharing level for the Population to Overlapping Accounts or All Accounts to enable field preset options

    • Click into the Crossbeam Default preset to open

    • From here you can:

      • Apply an existing preset to the Population or partner

      • Create a new preset by selecting the fields you want to share

      • Edit or manage a current preset

    • Click Save

To manage a preset at the partner level:

  • From the main Sharing Settings workspace, click a Population name to open

  • Locate the partner you would like to update and click into their row

  • Click into the Crossbeam Default preset to open the preset manager

  • Apply, create, or edit a preset as needed

  • Click Save


✍️Note

See more detailed information on Sharing Presets in Using Data Sharing Presets in Crossbeam.


Where to See What Your Partner is Sharing with You

From the Partner Detail Page:

  • Click Partners in the left-hand navigation and select a partner to open the Partner Detail Page > Settings

  • Click Shared with You to see all Populations the partner is sharing

  • Hover over Field Presets to see which fields are being shared, if available

  • Click Request Data to ask your partner to share more

Where to See What You Are Sharing with Your Partner

From the Sharing Hub:

  • Navigate to Data > Sharing Settings

  • Click a Population name to open the population detail page

  • Locate the partner you want to review and click the ↗ icon at the end of their row to open their partner sharing settings

  • From here you can apply filters and review what that partner is sharing with you across their Populations


📄 Related Articles

Did this answer your question?