# Referral CRM attachments: a boundary review | SourceX

Canonical: https://refer.sourcex.si/guides/how-to-avoid-building-a-shadow-data-room-in-your-crm
Last updated: 2026-11-05

A referral CRM becomes a shadow data room by accumulation, not by decision. An email log files a CEO's attachment on the account, a call notetaker stores a transcript of the company describing its business, a colleague drops in a deck "for context", and the CRM shows all of it to everyone who can open the record. Prevent it with a standing review that asks one question of every file, whose material is this, keeps only the evidence of the introduction and removes the company's material under your own retention policy.

A real data room is built on purpose. SourceX's own explainer describes a virtual data room as a permissioned workspace where access is granted in stages and the platform logs who opened which file ([what a virtual data room is](/questions/what-is-a-virtual-data-room)). A shadow one has the documents without the permission, the staging or the log. This page is for the operations lead at a consultancy, accounting firm, managed service provider or fund whose main CRM also holds referral records. Building a separate queue that never accepts files is covered in [the no-upload referral queue](/guides/how-to-build-a-referral-queue-without-uploading-client-data); this page deals with the CRM you already have.

## How company files reach a CRM nobody meant to fill

Each route below is a convenience someone switched on for other work. None of them asks whether the file belongs in a referral record.

| Route in | How a file arrives | Who tends not to notice |
|---|---|---|
| Email logging | A CEO's reply, with its attachment, is filed against the account automatically | The person who logged the email |
| Call and meeting notes | A recording or transcript of a call in which the company described its systems lands on the record | Whoever invited the notetaker |
| Drag and drop | A colleague attaches a deck, an org chart or an export "so the context is there" | The colleague, who meant well |
| Forwarded threads | A long thread carries attachments from three replies back | The forwarder |
| Pasted links | A link to the client's shared drive sits in a note and opens the file by another route | Anyone who later clicks it |
| Engagement spillover | Work papers from a separate paid engagement get filed under the same account | The engagement team |

If your firm logs email or meetings to the CRM, check whether attachments and transcripts travel with them; that one setting usually explains most of what a review finds.

Then check who can see the result. Salesforce's help page on file sharing, as its search excerpt describes it, offers an admin setting under which files attached to a record inherit the record's sharing, so anyone with read and write access to the record can collaborate on its files and read-only users can view them; with the setting off, attached files default to viewer access (our paraphrase). Either way, a file attached to a client account is readable by the people who can read the account. In a firm where the whole client team can open every account, the shadow room has as many visitors as the firm has staff.

## Whose material is it? Four kinds of attachment

Every file in a referral record belongs to one of four kinds, and the kind decides what happens to it.

| Kind | Examples | Verdict |
|---|---|---|
| A. Evidence of the introduction | The CEO's written yes, the introduction email, the portal submission confirmation | Keep, as the record's purpose |
| B. Your firm's own engagement work | Work papers, reports, invoices for a separate paid engagement | Move to that engagement's own system |
| C. The company's material | Exports, samples, screenshots, contracts, decks, org charts, financials, recordings or transcripts of the company describing its business | Remove from the CRM |
| D. Somebody else's material | The company's customers' files, another adviser's documents | Remove, and never forward |

Kind C is where good intentions do the damage. Under section 4.2 of SourceX's partner agreement, an introducer holds no right to pass along a company's inventory, records, raw data or personal information, and section 4.4 forbids collecting or keeping dataset copies through the referral program without a separate written authorization. SourceX's referral overview adds that the partner never needs to export, upload or describe confidential records, and the company's own application asks for no files at all. A file in the CRM helps nobody's introduction. Kind D is worse: SourceX's screening page names material that belongs to a company's clients among the usual poor fits, so a customer file is not even the company's to offer.

## The attachment boundary review checklist

Run it once now across every referral record, then on the schedule in the next section. It has three parts.

**Find**

1. List every attachment on accounts and contacts that carry a referral record, with its date and the route that filed it.
2. List every link in referral notes that points somewhere other than a public website.
3. List transcripts and recordings filed by meeting or call integrations on those records.
4. Note who can open each record: the team, the office, the whole firm.

The Federal Trade Commission's guide to protecting personal information starts the same way. Its first principle, take stock, says that effective security begins with knowing what information you hold and who has access to it, and that an inventory is not complete until every place sensitive data might sit has been checked (our paraphrase of the search excerpt). A CRM's attachment tab is one of those places that rarely gets checked.

**Sort**

5. Who created the file: the CEO, your colleague, an integration or a third party?
6. Whose business does it describe?
7. Is it evidence that the introduction happened or was permitted?
8. Would the referral note still make sense without it? If yes, it is not evidence.
9. Did the CEO send it deliberately, or did a sync file it?

**Act**

10. Kind A: keep it, and name it in the referral note so it can be found.
11. Kind B: move it to the engagement's own system and remove it from the referral record.
12. Kinds C and D: open nothing further, forward nothing, delete under your firm's retention policy, and add a note line saying an attachment from the company was removed on a stated date, without describing it. If the CEO sent it deliberately, tell the CEO once that any material reaches SourceX only through SourceX's own process.

**Method note.** The four kinds and the twelve checks were built for this page from SourceX's program terms (Version 2026-10-22.2, since replaced by version 2026-11-04), sections 4.2 and 4.4 of the unsigned partner agreement sample, SourceX's referral overview, application and screening pages, Salesforce's file sharing help and the FTC's guide, all read on 2026-10-27. They test what sits in a partner's own CRM. They say nothing about how SourceX handles data, which only SourceX's published pages can describe.

## Who runs the review, and when

| Moment | Who reviews | What they do |
|---|---|---|
| An email or meeting integration is set up or changed | Operations lead | Decides whether attachments and transcripts may be filed against records that carry a referral |
| A new referral record is opened | The introducer | Confirms the record holds no attachments beyond kind A |
| The CEO sends a file | Whoever receives it | Applies checks 5 to 12 the same day |
| Each quarter | Operations lead | Runs the full checklist across open and recently closed records |
| A referral closes | Operations lead | Keeps kind A, confirms nothing else remains |
| Someone leaves the firm | Operations lead with IT | Reviews the referral records that person owned |

When a removed file contained personal data or a customer's records, the operations lead brings in the firm's own privacy lead or counsel; the review does not decide what notice, if any, the firm owes anyone. And never reassure a CEO about what SourceX will do with anything. SourceX speaks for its own handling of data on its own pages.

## One firm's quarterly sweep (Illustrative)

Illustrative. An invented 40-person advisory firm with 26 open referral records; no real client or system.

| Kind | Files found | What they were | Action |
|---|---|---|---|
| A. Evidence of the introduction | 7 | Five CEO emails saying yes, two portal confirmations | Kept and named in the notes |
| B. Engagement work | 4 | Tax work papers filed under the client account | Moved to the engagement file |
| C. Company material | 17 | Nine email attachments filed by the log, five call transcripts, three decks | Deleted; a dated line added to each note |
| D. Third-party material | 3 | Two customer contracts and one supplier price list | Deleted; never forwarded |
| Total | 31 | Found across 26 records | 7 kept, 24 out of the referral CRM |

The pattern is typical of a first sweep: most of kind C arrived through the email log and the notetaker, not through anyone's decision. The fix that mattered was the integration setting, not the deletions. The [route-only note format](/guides/the-referral-note-format-that-preserves-context) shows how to record the removal without describing what was removed.

## Closing a referral and keeping only what survives

When a referral ends, whether by the CEO's decision, the window passing, a SourceX outcome or a recorded payout, close the record with kind A intact and nothing else. The partner agreement excepts records needed for reward accounting and dispute evidence from its return-or-delete clause, and kind A is that record. SourceX's terms decide attribution from dated records, including written introduction evidence, so the CEO's yes and the submission confirmation are worth keeping for as long as your retention policy allows.

Nothing else earns a place "in case it is useful later". SourceX's terms note that partners never receive other partners' records or applicant documents from SourceX itself, and a partner holding the company's files would be holding more than the program ever gives it. The difference between data leaving a company with no agreement and a deliberate, scoped license is the subject of [shadow AI in portfolio companies](/guides/shadow-ai-portfolio-companies-risk); when a client asks about exporting at all, the live guide on [whether exporting CRM data is safe](/guides/is-exporting-crm-data-safe) explains why an introducer never runs or keeps the export.

## What an attachment review cannot catch

- **Other places.** Personal inboxes, phones and desktop downloads sit outside the CRM, so the review needs a matching rule for them.
- **Deleted is not always gone.** Check where your own system sends deleted files, and for how long.
- **Settings drift.** Integrations get updated and re-enabled; one quarterly sweep does not fix a sync that refiles attachments every day.
- **Support tickets and other systems.** Notes in a help desk or billing tool follow their own visibility rules, covered in [keeping referral notes out of support tickets](/guides/how-to-keep-referral-notes-out-of-client-support-tickets).
- **The CEO keeps sending.** Some will. Each file gets the same answer, politely, every time.
- **No outcome data.** How much a first sweep typically finds has not been measured. Count kinds A to D in your own first two sweeps; no figures are published.

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

Once your referral records hold nothing but evidence of each introduction, [register as a partner](/register) if your firm has not, sign the Channel Partner Agreement before anything is submitted, check each company against [who qualifies](/who-qualifies) from what its CEO tells you, and keep the [program terms](/terms) version you rely on beside the review. More operations guides are in the [guides library](/guides).

## Sources

- https://refer.sourcex.si/terms
- https://sourcex.si/documents/partner/SourceX_Channel_Partner_Agreement_Sample.pdf
- https://refer.sourcex.si/how-it-works
- https://sourcex.si/apply
- https://refer.sourcex.si/who-qualifies
- https://help.salesforce.com/s/articleView?language=en_US&id=sf.admin_files_on_record_sharing_setting.htm&type=5
- https://www.ftc.gov/business-guidance/resources/protecting-personal-information-guide-business
