How to map partner accounts without sharing your CRM data
You can find the accounts you share with a partner without sending them your CRM. Here is the sharing model that makes it work, and what to ask any vendor.
You can find the accounts you share with a partner without handing over your CRM. Connect your own CRM to a mapping tool, keep sharing at counts only to begin with, and let the account owner choose each step up: a number, then names, then detail. The partner receives only what you release, never your records.
The short version
"Without sharing your CRM data" does not mean the tool never touches your CRM. A mapping tool has to read your accounts to compare them. It means the partner never receives your CRM, your spreadsheet or a copy of either. They see a result, at a level you set, and nothing more.
That difference is the whole question. The rest of this post is about how to tell whether a tool really draws that line.
Why exporting a list is the wrong tool
The default is to export a list and email it. It fails in three ways.
- It is a copy. Once the file leaves, you cannot recall it, narrow it or see who opened it.
- It is redacted by hand. The person preparing it decides, cell by cell, what is safe. One slip exposes a contact.
- It is all or nothing. You cannot say "tell them how many, not who".
A comparison computed from both CRMs, with sharing rules applied before anything is shown, removes all three.
Six things to look for
1. Sharing enforced on the server
If a tool sends the full comparison to your partner's browser and hides the parts you did not share, the data has already left. Sharing rules must be applied where the answer is built, on every read, for every surface, including any API or AI assistant. Why partner data sharing has to be enforced on the server explains why.
2. A conservative starting point
A new partnership should start at the lowest level, a count, and stay there until someone chooses otherwise. Nothing should be visible just because a partnership exists.
3. Small counts that do not leak
A count of one is as identifying as a name. If a partner suspects a particular account is in the overlap, a count of one confirms it. A sound tool suppresses small counts instead of showing them as exact numbers.
4. Sharing set per partner and per segment
You will want to tell one partner the names of overlapping customers and tell another only a number. The rule should attach to a segment of your accounts, such as customers or open opportunities, for each partner, not to your whole database.
5. A person confirming uncertain matches
Matching on domain is reliable. Matching on name is not, on its own. A wrong match tells a partner two unrelated companies overlap, so uncertain pairs should wait for a person to confirm.
6. A record of every change
When a partner asks why they can suddenly see more, the answer should be a log of who changed which setting and when, not a memory of a settings page.
What a partner sees at each level
| Level | What the other side sees |
|---|---|
| Counts only | A number of overlapping accounts. Below the tool's threshold, no number at all. |
| Overlapping accounts | The names of the accounts you both have. |
| All accounts | Full detail for the overlapping accounts, plus any extra fields you have chosen to include. |
The level is set by the company that owns the accounts, never by the partner viewing them.
Questions to put to any vendor
- Where is the sharing rule applied, on the server or in the browser?
- What does a brand-new partnership see before anyone changes a setting?
- What happens to a count of one or two?
- Can I set a different level for each partner and each segment?
- Who confirms a match that is not an exact domain match?
- Is every sharing change logged, and can I read the log?
How Co-Signal approaches it
Co-Signal is built around these six points. Each side connects its own Salesforce or HubSpot, or imports a CSV, and nothing is shared at that point. Every new partnership starts at counts only, counts below five are never shown as a number, and every sharing change is written to an audit log. The security page lets you try the sharing levels on sample data, and the product page shows how an overlap is computed.
Frequently asked questions
Can I map partner accounts without sharing my CRM?
Yes. The tool reads your own CRM to compare it with a partner's, but the partner receives only a result at the level you set, such as a count or the names of overlapping accounts. They never receive your records or a copy of your CRM.
What should a new partnership be allowed to see?
Only a count, and only until you choose otherwise. Nothing should be visible to a partner just because a partnership exists.
Why do small counts need suppressing?
A count of one is as identifying as a name. If a partner suspects a particular account is in the overlap, a count of one confirms it. Suppressing small counts stops a number from revealing a single company.
Where should sharing rules be enforced?
On the server, where the answer is built, on every read and for every surface. A browser-side filter cannot be trusted, because the data has already been sent.
How do I know a sharing setting changed?
Look for a log of every sharing change, showing who changed which setting and when. If a tool cannot show you one, you cannot answer a partner who asks why they can suddenly see more.
