When Crossbeam syncs your Salesforce data, we pull in records linked to your Account and Lead tables. This article details what we pull in by default, but you can manage your Salesforce connection, including adding additional fields to the sync, as long as it's connected to an Account or Lead.
Since Crossbeam only supports building a population off of Accounts or Leads, let's talk about how to use filtering to create your "Opportunities" population. The filtering works by looking at the opportunities for the account. If at least one of the opportunities matches the filter condition, the account is included in the population. In the below example, we are filtering for Accounts in the Sports Industry, but only with an opportunity close date after 2020-08-01.
This does not affect sharing at all. If your population filtering pulls in one opportunity, the account is included in the population. If that account matches with a partner (see: How does Crossbeam do matching?), your partner would have visibility into the account name. If you were to share opportunity data, such as sales stage, or close date, your partner would then have visibility into ALL opportunities associated with the account, not just the one that matches the filter condition.
The account 'Modell's Sporting Goods' exists in Salesforce under the 'Sports' industry with two opportunities associated with it:
Opportunity #1: 'Close Date' of '2020-07-31'
Opportunity #2: 'Close Date' of '2020-08-30'
Using the filtering above, 'Industry' is 'Sports' and 'Close Data' is on or after '2020-08-01', only Opportunity #2 meets the population criteria. However, all opportunities will be visible in Crossbeam. (Note: you'd have to be sharing opportunity level data for the different opportunities to be shown to partners.) If 'Modell's Sporting Goods' only had Opportunity #1 associated with it, with a 'Close Data' of '2020-07-31', 'Modell's Sporting Goods' would NOT get pulled into the population.