# Limit access to referral notes inside a fund | SourceX

Canonical: https://refer.sourcex.si/guides/how-to-limit-access-to-referral-notes-inside-a-fund
Last updated: 2026-11-05

Treat referral notes as five layers rather than one file: the introduction record, the internal approval, SourceX's updates, counsel's file and the payment file. Give each role in the fund the one or two layers its next decision needs, and nobody any layer by default. SourceX's sample partner agreement lets confidential information go only to people who need it for the referral and are bound to keep it confidential, and what the fund learned through a board seat belongs in no layer at all.

This brief is for the general counsel liaison asked, once the first introductions sit in the fund's CRM, who can see them. If the honest answer is "everyone with a login," the design below replaces it with one you can write down.

## What a referral note is for, and who needs to read it

A referral note serves four decisions, and the investment decision is not one of them: whether the fund approved asking the CEO; what SourceX received and when, since section 2 of the program terms decides credit "from dated records"; whether a conflict or duty stopped anything; and whether a reward was paid and reconciles. Each has a small audience, and none needs a portfolio company's numbers.

The partner may be the fund itself. SourceX's unsigned sample Channel Partner Agreement names the Partner as "an individual, or entity type and jurisdiction," so a fund can sign as the partner in its own name. The sample counts "introduced contact identities, introduction records" as confidential information (section 1.6). Section 4.1 says each side will use the other's confidential information only for the referral relationship and protect it "with reasonable care." Section 4.2 allows disclosure to "employees, professional advisers and service providers who need the information for the permitted purpose and are bound by confidentiality duties at least as protective as this Agreement," and adds: "A Receiving Party is responsible for its representatives' compliance." Section 8 of the terms says the signed agreement governs confidentiality, so counsel reads the fund's signed text, not the sample.

What flows back from SourceX is thin by design. The sample says the partner receives what it needs to track its own referral and reward, "using generic stages or reference codes" (section 4.6), and section 7 of the terms says partners never receive other partners' records, applicant documents or confidential buyer information. A fund's notes should stay that thin. Nobody at the fund collects company data for SourceX: the company applies on its own, and its CEO decides what the company tells SourceX.

NIST's glossary calls the principle least privilege: each entity gets only the authorizations its function needs, and users only the access their assigned tasks require (a paraphrase). For referral notes, access follows decisions, not seniority.

## The role-based access design brief

The brief has two parts: the layers, and who may touch each. Write both into the fund's referral policy before the next introduction is logged.

**The five layers.** Each holds one kind of information and has one owner.

| Layer | What it holds | Owned by | Kept because |
|---|---|---|---|
| 1. Introduction record | Company, domain, partner of record, a one-line opportunity, the CEO's work contact, the method and timestamp | The referral administrator | It is what SourceX receives, and dispute evidence if credit is questioned |
| 2. Approval record | The CEO's own email agreeing to the introduction, who in the fund approved sending it, and the conflict outcome (pass, unknown or escalated) with a date | The relationship owner | It shows the CEO knew and agreed before anything was sent |
| 3. SourceX updates | Stage labels, reference codes and the reward status the dashboard shows (Estimated, Eligible, Approved, Paid) | The referral administrator | It tracks the fund's own referral |
| 4. Counsel file | The facts behind any escalation and counsel's view | Fund counsel or compliance | Duties and conflicts are counsel's to weigh |
| 5. Payment file | Amounts actually paid, the fund's payment and tax details and cap usage | Finance | Payment requires those details, and accounting must reconcile |

Layer 1 follows section 3.3 of the sample, which lists what an introduction record must identify, plus the CEO's work contact so SourceX can reach the person who decides. Layer 2 replaces what many funds keep as free-text "deal notes," which is where board material tends to leak in.

**Who may touch each layer.** Edit means the role writes the layer; read means it may open it; none means the layer does not appear for that role at all.

| Role | 1. Record | 2. Approval | 3. SourceX updates | 4. Counsel file | 5. Payment file |
|---|---|---|---|---|---|
| Relationship owner (who asked the CEO) | Edit | Edit | Read, own introductions only | None | None |
| Referral administrator (who submits under the fund's account) | Edit | Read | Edit | None | None |
| Fund counsel or compliance | Read | Read | Read | Edit | Read, on request |
| Finance | None | None | Read | None | Edit |
| Investment team and committee | None | None | None | None | None |
| Other platform staff | None | None | None | None | None; a count of introductions only |
| Investor relations and LP reporting | None | None | None | None | None |
| CRM administrator or other outside provider | System access only, under confidentiality duties at least as protective as the agreement | Same | Same | None | None |

Material that belongs in no layer, for any role:

- board packs, management reports and anything received through information rights;
- investment memos, valuations and the fund's views on the founder;
- company records, exports, screenshots, samples or system descriptions;
- reward estimates or forecasts of what the company might receive;
- anything about another partner's introductions.

The first item has a published basis on SourceX's own screening page, which says what a fund knows from board packs or information rights is "a reason to ask the CEO, never material to pass along." The how-it-works page adds that a partner never needs to export, upload or describe confidential records, so a note that holds them serves no step in the process.

**Method note.** The brief was built on 28 October 2026 from sections 1.6, 3.3, 4.1, 4.2, 4.4 and 4.6 of the unsigned sample agreement (version 2026-10-19), sections 2, 5, 7, 8 and 9 of the program terms (version 2026-10-22.2, since replaced by version 2026-11-04), SourceX's screening and process pages and NIST's least-privilege definition. Each cell was set to the least access with which that role's decision still works. Nothing here measures outcomes, and it is not a reading of any fund's documents or of the agreement a fund actually signed.

## Cut each layer down to what the next decision requires

Most access problems start as content problems: a note that mixes the CEO's agreement with a board-meeting revenue figure cannot reach finance without the figure. Split the note first, and the access rules become enforceable.

Illustrative. A generic fund and an invented CRM entry. A platform associate logs an introduction as one free-text note with eight items. The counsel liaison sorts each into a layer or out of the system:

| Item in the original note | Where it goes | Why |
|---|---|---|
| Company name, domain and the CEO's work email | Layer 1 | SourceX needs them to identify and reach the company |
| "CEO agreed on the 14th, email attached" | Layer 2 | Proof of agreement, kept by the relationship owner |
| "Conflict check: pass, 15th" | Layer 2 | Outcome only; the facts stay with counsel |
| Headcount from the latest board pack | Deleted | Information-rights material; the company states its own size when it applies |
| ARR band from the investment memo | Deleted | No referral decision uses it |
| "Founder frustrated with the board" | Deleted | An opinion about a person, serving no decision |
| Reward estimate | Deleted | No layer holds forecasts; the terms call portal and calculator estimates projections, not promises |
| SourceX reference code and current stage | Layer 3 | The fund's own tracking |

Five items survive in layers, three are gone, and each role can now open its layer safely. For the advisory-firm version of the same discipline, see [the professional referral audit trail](/guides/the-professional-referral-audit-trail-without-excess-client-detail), which records decisions without copying client facts.

## Retention, withdrawal, departure and publication

Four events change who should hold a layer, and each needs its own rule.

**Retention.** The sample agreement's section 4.4 asks each side to return or delete the other's confidential information on written request or at termination, while allowing records kept for legal obligations, reward accounting, dispute evidence and routine inaccessible backups. Section 9 of the terms says confidentiality obligations run for three years after the agreement ends. In layer terms: keep layers 1 and 2 as dispute evidence, keep layer 5 for accounting, keep layer 3 while the referral is open, and let counsel set the life of layer 4. Delete anything that strayed outside the layers.

**Withdrawal.** If the CEO withdraws, layer 2 records the date and the CEO's words, layer 1 stays only as evidence, and nobody contacts the company about it again.

**Departure.** When a person leaves, access ends the same day and their layer 2 entries pass to a named successor. [When a partner leaves the fund with an active introduction](/guides/when-a-partner-leaves-the-fund-with-an-active-introduction) covers the handoff of contacts and open introductions.

**Publication and escalation.** An LP letter or newsletter that names an introduced company is a new disclosure, not a new reader of an old note. Section 4.5 of the sample bars either side from publicly identifying the other as a partner or disclosing non-public deal details without written authorization, and the company's own written yes comes first. Questions about the company's records never travel through the notes at all: SourceX's trust page says "The supplier decides which systems, records and date ranges are in scope," so that conversation belongs to the company and SourceX.

## Where an access design breaks down

- **One person, three roles.** At a small fund the relationship owner may also submit and approve. Separation then rests on layers, not people: log each time one person acts in a second role, and keep layer 4 with counsel regardless.
- **Search and summary tools.** A tool that reads the whole CRM hands every user every layer. Check what it can see before switching it on.
- **Copies outside the system.** An email forward or a spreadsheet export carries a layer past its access rules. [How to correct a referral email sent with too much detail](/guides/how-to-correct-a-referral-email-sent-with-too-much-detail) covers the moment that happens.
- **The signed text differs.** The sample is a starting point; the fund's signed agreement and its own fund documents may be stricter, and counsel reads both.
- **Personal and fund accounts.** If some people refer through personal accounts, their notes may sit outside the fund's system entirely; [personal versus firm-owned referral links](/guides/how-to-handle-personal-versus-firm-owned-referral-links) sets out that choice, and the published terms do not settle how a fund's account relates to its people's personal ones, which SourceX decides.
- **No outcome data.** Nobody has published whether tighter access changes how companies respond to introductions. The case for it rests on duty and on [keeping rewards out of investment selection](/guides/how-to-keep-referral-rewards-out-of-investment-selection), not on measured results.

**A measurable check.** List every person who can open the fund's referral notes today. Beside each name, write the decision they need the notes for and the layer that decision uses. Anyone without a decision loses access this week; anyone with a decision keeps only that layer. Privileged material needs a stricter rule still, set out in [keeping privileged material out of referral discussions](/guides/how-to-keep-privileged-material-out-of-data-referral-discussions). More guides sit in the [guides hub](/guides), and the step-by-step process is on [how it works](/how-it-works).

## 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 the five layers and the role table are written into policy, the fund can [register its partner account](/register), check each company against [SourceX's published fit criteria](/who-qualifies) and confirm in the [program terms](/terms) that the records it keeps match what credit and payment depend on.

Setting access rules for referral notes is fund housekeeping; deciding whether SourceX is a sound investment is a separate question, and investor materials for it are available through the [SourceX investor overview](https://sourcex.si/investors).

This article is for information only and is not an offer to sell or a solicitation of an offer to buy securities. Any offering by SourceX is made only to verified accredited investors through its offering documents.

## Sources

- https://sourcex.si/documents/partner/SourceX_Channel_Partner_Agreement_Sample.pdf
- https://refer.sourcex.si/terms
- https://csrc.nist.gov/glossary/term/least_privilege
- https://refer.sourcex.si/who-qualifies
- https://refer.sourcex.si/how-it-works
- https://sourcex.si/trust
- https://sourcex.si/investors
