Sharing Settings for Partners
Customize your sharing settings with a specific partner to share more, or less, data than your population sharing default allows.
Lindsey O'Niell avatar
Written by Lindsey O'Niell
Updated over a week ago

Heads up! Make sure you understand how Sharing Defaults for Populations work before diving into sharing settings for partners.

After setting up sharing defaults for your populations, you may want to customize these sharing settings for a specific partner.

This starts with the partner detail page. On the top of this page, you'll see two tabs that have to do with data sharing for your partner: Shared with You and Sharing Settings.

Shared with You

This tab shows you what data your partner is sharing with you. In the example below, we can see three of our partner's populations (Bozala will act as our partner for this tutorial).

  • For their Prospects population, they are sharing overlap counts, meaning just the number of accounts you have in common.

  • For their Open Opportunities population, they are sharing 7 fields with you whenever their population overlaps with any of your populations.

  • For their Customers population, you can only see overlap counts whenever their population overlaps with any of your populations but they have a per-population override in place that shares 4 fields with you when their Customers population overlaps with your Customers population.

Sharing Settings

This tab shows you how all of your populations are being shared (or not shared!) with your partner.

  • For your Prospects and Open Opportunities populations, your partner can see 5 fields with any of your partner's populations.

  • Customers population is only showing overlap counts with your partner's populations.

  • Your All Accounts population is Hidden from Bozala, which means they don't know this population exists.

  • Your custom New Pipeline population is sharing 14 fields when it overlaps with any of your partner's populations.

Note: The (default) next to the sharing status means that it is the sharing default for that population.

Editing Sharing Settings

Now that we know how to view what is being shared with us, and what we are sharing- we can custom tailor our sharing settings within this specific partnership. To edit your sharing settings with a partner, click on the pencil within the population on the Sharing Settings tab.

The modal that pops will look very similar to the modal you used to initially set your population sharing default. From here, you are given the option to Customize this setting.

Note: once you customize the default setting, you are essentially "disconnected" from the population default. In the example above, any changes to the Open Opportunity population at the default level would not apply to Bozala once you save these custom sharing settings.

Once you click Customize, you can change the sharing setting with this partner to any of the three available options. In the example below, we've changed the sharing settings with Bozala to Sharing Data and selected two fields to share (account type and country) when an overlap occurs.

Don't forget to click "Save"! You can double check what data is being shared by hovering over "Sharing 2 fields"- account type and country appear below, meaning we've successfully customized our sharing settings with Bozala!

Change your mind? No problem- once you've customized your sharing setting with a partner, you can always revert back to the population default setting by clicking Set to Default. When you're connected to the default again, any changes to the population's sharing default will resume affecting this partner (Bozala, in this example).

When you customize sharing settings at the partner level, those changes will apply when your population overlaps with any of your partner's populations.

Need even more specification? If there is particular data you would like to share when your population overlaps with a specific one of your partner's populations, you can customize even further by creating per-population overrides.

Did this answer your question?