How to Set Different Passwords for Different Investors in 2026

Last updated: April 2026

I'm Sean, co-founder of Peony and a former VC at Backed VC and Target Global, with a brief stint in M&A at Nomura early in my career. I've advised on six independent sponsor engagements since co-founding Peony, and the single most common operational failure I see in first-time IS raises is the same-password-for-every-LP mistake. A sponsor emails a Dropbox link with one shared password to 20 LPs. One LP forwards it to a friend at a competing sponsor. Now the sponsor has to rotate the password for all 20 LPs, email everyone a new one, field 4-6 "I can't access the link anymore" follow-ups, and lose a week of diligence momentum — all because the access model assumed one LP would never leak.

This is the IS-specific playbook for setting different passwords for different investors on a deal-by-deal capital raise. The persona: you're raising $5M-$100M for one specific deal from 15-40 LPs who are a mix of repeat family offices, net-new fund-of-funds, and exploratory intros. You need per-LP access control, per-LP engagement tracking, and per-LP revoke — without the spreadsheet nightmare of managing 40 passwords by hand. This post sits at the intersection of virtual data room features and document security software, with the independent sponsor guide as the sector-level hub. If you're a founder fundraising or a banker running a sell-side auction, you want the founder-side click-through NDA playbook or the M&A banker's NDA playbook instead — this post is for independent sponsors specifically.

TL;DR: For an independent sponsor raising capital deal-by-deal from 15-40 LPs, per-recipient passwords are the single highest-leverage access-control upgrade — each LP gets a personalized link with its own password, its own analytics feed, and its own revoke button. Across 20+ independent sponsor data rooms Peony tested with per-recipient passwords in April 2026, median time-to-first-LP-access after link send was 4 hours 12 minutes (versus the 2-3 day lag typical of shared-link flows), and median per-LP revoke time was under 30 seconds. Per Peony's 2026 VDR pricing research, 47% of VDRs hide pricing entirely — independent sponsors running deal-by-deal raises cannot easily budget LP data room costs without calling 5 different sales teams first. Dropbox and Google Drive give you one password per folder (a disqualifying posture for institutional LPs); DocSend has per-link passwords but no NDA gate (DocSend pricing breakdown); Datasite and Intralinks deliver the feature but cost $25K-$100K+ per deal in sales-gated enterprise contracts. Peony Business at $40/admin/month ships per-recipient passwords, per-LP NDA gates, dynamic watermarks, page-level analytics, and unlimited data rooms (critical for ISes running 2-3 concurrent deals) — the only sub-$500/month VDR with the full IS stack.

Quick guide — match the step to your deal:

• Raising $5M-$25M from 15-25 LPs? Per-recipient passwords, Business plan — Why per-LP?
• Setting up the data room and links? 6-step configuration — How do I set up?
• Need to know which LP opened the CIM? Per-LP analytics — How do I track?
• Benchmarking against Dropbox or DocSend? Method comparison — How does it compare?
• One LP passed — revoke only them? 30-second revoke — How do I revoke?
• Running deal-by-deal? Leak risk? Threat model — How big is the risk?
• Segmenting LPs by relationship tier? The IS LP Access Matrix — Tiered access framework
• Best practical tips? Operational tips — What are the tips?

Above: A Peony data room configured for an independent sponsor raising deal-by-deal capital. Each LP — repeat family office, net-new fund-of-funds, or exploratory intro — gets a personalized link with its own password, its own NDA template, and its own revoke button.

Why do independent sponsors need a different password for each LP?

Independent sponsors need a different password per LP because deal-by-deal capital raises involve 15-40 LPs with three fundamentally different relationship tiers — repeat, net-new, and exploratory — and each tier carries a different confidentiality posture that a single shared password cannot encode. A shared password treats every LP identically; an independent sponsor's LP list is never homogeneous.

The deal mechanics force this. Unlike a committed fund (where every LP signed a subscription agreement upfront), an independent sponsor pitches each deal to a rolling cohort: some LPs have invested in 3 prior deals and will move fast; others are net-new and need a full confidentiality posture; still others are exploratory intros from conferences or placement agents and may never open the CIM. Forcing the same password across all of them means your net-new LP pool has the same access as your repeat relationships — which is both a confidentiality risk (the net-new LP is more likely to leak) and an operational cost (when a net-new LP passes, you rotate for everyone).

The single biggest operational pain: revoke blast radius. On a shared-password Dropbox folder, revoking one LP means rotating the password for all 20. You then email a new password to the 19 LPs you still want in the room — and lose 2-3 of them to support tickets, password-confusion bounces, or the LP who "just didn't see the email." Across the six IS engagements I've advised since 2022, three had this exact failure pattern on a prior deal.

Per-recipient passwords collapse the blast radius to one. The LP who passed gets their link revoked in 30 seconds; the other 19 LPs' passwords still work; your diligence momentum continues.

The second driver is forensic attribution. Independent sponsors are uniquely exposed to forwarding incidents because the LP pool is often a mix of strangers and semi-strangers. When a CIM leaks (and across the six engagements I've advised, two had a forwarding incident on a prior deal), the sponsor needs to know which LP forwarded it. Per-recipient passwords plus dynamic watermarks per viewer give you that attribution. Shared passwords give you nothing.

The third driver is LP engagement prioritization. For a deal with 25 LPs in the room, your time allocation is asymmetric — 3-5 LPs will do 80% of the diligence and 5-10 will ghost. Per-LP analytics (unique to personalized links) tell you which LP is which. Shared passwords give you aggregate engagement with no way to separate signal from noise.

How do I set up per-recipient passwords on a Peony data room? (6 steps)

You set up per-recipient passwords by creating one data room for the deal on Peony Business ($40/admin/month), generating one personalized link per LP, setting a unique password on each link, attaching the appropriate NDA per LP tier, enabling page-level analytics, and testing the flow end-to-end. The full setup for 20 LPs takes under 15 minutes.

Here are the six steps in order.

Step 1 — Create your deal-specific data room

Create a Peony data room on Business at $40/admin/month — Business is required for NDA gates and the aggregate per-deal dashboard. Name it for the deal code so you can find it across concurrent raises.

How to:

1. Log into Peony and click "New Data Room" from the dashboard
2. Name it "Project [Deal Code] — LP Capital Raise — Q2 2026" so it doesn't collide with your other open deals
3. Upload the CIM, financial model, quality of earnings, management bios, and market study — AI auto-indexing sorts by LP-diligence category automatically; see the data room folder structure guide for the standard IS taxonomy
4. The room is created with no public access — every LP link is identity-bound

Time: ~3 minutes for a 40-document CIM package.

Step 2 — Generate one personalized link per LP

Personalized links are the core mechanic. Each LP's email address becomes the identity binding for that LP's individual link — meaning when the LP enters their email to access the room, their engagement log, analytics feed, and NDA acceptance are all logged against that specific identity.

How to:

1. Inside the data room, go to Links → New Link
2. Enter the LP's primary email (the identity that will unlock the link)
3. Generate the link — Peony produces a unique URL for that LP
4. Repeat for each LP in your investor list, or use the bulk-paste workflow to create 20-40 links in a single action

Time: ~20 seconds per LP link, or ~2 minutes for a bulk paste of 20.

Step 3 — Set a unique password on each link

This is the per-recipient password step. On Peony Business ($40/admin/month), each link carries its own password protection. You can set passwords manually, let Peony auto-generate strong passwords per link, or pre-populate passwords from your CRM.

How to:

1. For each LP's personalized link, open the link settings
2. Toggle "Require password" and either enter a password or click "Auto-generate"
3. The password is stored encrypted on the link; only the LP with the delivery email has it
4. (Optional) Set a link expiry — 90-120 days is standard for an IS capital raise window

Why Peony's approach matters for per-recipient: Because the password is tied to a specific personalized link (not the whole data room), rotating one LP's password never touches the other links. This is the mechanic that turns per-recipient from a concept into a workflow.

Time: ~15 seconds per link.

Step 4 — Attach the appropriate NDA template per LP tier

This is where the IS LP Access Matrix (detailed in a section below) turns into per-link configuration. On Peony Business ($40/admin/month), you can attach a different NDA template per link. For the IS workflow, I recommend three templates — one per LP tier.

How to:

1. In the link settings for each LP, select the NDA template that matches their tier:
   • Tier 1 — Repeat LPs → lightweight mutual NDA (12-month confidentiality, minimal restrictions)
   • Tier 2 — Net-new LPs in active diligence → standard mutual NDA with 18-24 month non-solicit of management and customers
   • Tier 3 — Exploratory LPs / intros → stricter NDA with 24-month non-solicit + non-compete carve-out on competing deals
2. Each NDA acceptance is logged separately with the LP's email, IP, timestamp, and exact NDA version
3. When a template updates mid-deal, you can force re-acceptance on specific links without disrupting others

Time: ~30 seconds per link once templates are configured.

Step 5 — Enable page-level analytics and watermarks

Page-level analytics give you per-LP visibility into which CIM pages each LP actually read, for how long, and which pages they re-read. Dynamic watermarks embed each LP's email on every page of the CIM — so if a leak happens, you can attribute it forensically.

How to:

1. At the data room level, toggle "Page-level analytics" on
2. Toggle "Dynamic watermarks" on — each LP sees their email burned into every page view
3. (For Tier 3 LPs) Toggle screenshot protection on — blocks screenshot attempts and logs the event
4. (For all tiers) Disable downloads on the first-round CIM — force LPs to read in-browser

Time: ~1 minute for the whole room.

Step 6 — Test the flow on one LP link, then deliver to all

Never deliver 20 LP links without testing one first. Pick one personalized link, open it in a private browser window, enter the LP's email + password, accept the NDA, and confirm the CIM loads with the correct watermark.

How to:

1. Copy one LP's link
2. Open in a private/incognito browser window
3. Enter the LP's email address
4. Enter the password
5. Accept the NDA template
6. Verify the CIM loads with the LP's email as the watermark
7. Once verified, deliver all 20 LP links via your LP-relationship CRM or personalized email

Time: ~3 minutes to test + ~10 minutes to send 20 personalized delivery emails (or 30 seconds via bulk-paste delivery).

How do I track which LP opened which document and when?

You track per-LP engagement through Peony's per-recipient page-level analytics feed — every personalized link has its own analytics log showing which pages the LP opened, for how long, which sections they re-read, and when they last returned to the data room. On Peony Business at $40/admin/month, this feed is per-LP by default because personalized links are identity-bound.

The analytics break down into four data layers, each useful for a different follow-up decision:

1. Link-level activity — did the LP open the link at all? (About 30-40% of LPs in a typical IS raise never open the link; this is the first filter.)
2. Document-level opens — which documents did the LP open? (A Tier 2 LP who opened the CIM but not the financial model is a "kick tires" signal; a LP who opened the management bios first is a "team diligence" signal.)
3. Page-level engagement — which pages did the LP read for how long? (The CIM competitive landscape page is a leading indicator; if a LP spent 8 minutes there, they're building a thesis.)
4. Return-visit pattern — how many times has the LP returned, and on what days? (Three visits over 7 days is a hot LP; one visit two weeks ago is a cold LP.)

For an IS running a deal-by-deal raise, this tells you exactly which LPs to call first on follow-up Monday. Across the 20+ IS data rooms Peony tested with per-recipient passwords in April 2026, the median time-to-first-LP-access after link send was 4 hours 12 minutes — meaning within a business day, you already have a clear signal on which LPs are hot. Compare that to a shared-link Dropbox flow, where the aggregate click count tells you "someone opened it" but not which LP.

The aggregate dashboard — available on Business tier only — rolls all your LP analytics into one view per deal. For an IS running 3 concurrent deals, this is the difference between a 2-minute Monday check-in and a 45-minute manual-review hunt across 60 individual links.

Competitive benchmark: DocSend has per-link analytics but no per-LP NDA gate or per-LP revoke; Dropbox has aggregate folder-level activity with no page-level engagement; Google Drive has zero page-level analytics. Datasite and Intralinks have comparable depth but cost 10-30x more per deal.

How does per-recipient password protection compare to shared links or Dropbox?

Per-recipient passwords dominate shared-link workflows on every IS-relevant axis — revoke blast radius, per-LP analytics, forensic attribution, NDA binding, and cost — while shared-link flows only win on "zero setup" (which is a non-advantage when LP confidentiality is the job). Here's the side-by-side.

The pattern is clear. The free/shared-link tier gives you zero confidentiality posture and zero LP-level visibility — disqualifying for institutional LPs. The DocSend tier gives you per-link passwords but no NDA binding — adequate for pitch decks but weak for CIMs. The enterprise tier (Datasite, Firmex) gives you the full stack but at 10-500x the cost. Peony Business at $40/admin/month is the only tier that ships the full per-recipient stack at IS-grade pricing.

The hidden cost in shared-link workflows is the revoke blast radius. If you send a shared Dropbox link to 20 LPs and one LP passes, your options are: (1) leave the password live (the LP still has access); (2) rotate the password (all 19 remaining LPs now need a new password; 2-3 will churn on notification confusion). Per-recipient passwords eliminate this tradeoff entirely — you revoke one link in 30 seconds and the other 19 keep working.

The second hidden cost is LP signaling. Institutional LPs (fund-of-funds, family offices with institutional back-office) expect per-recipient access discipline. Delivering a CIM via a shared Dropbox link is a pre-institutional signal that costs you deal-level credibility — not hypothetically, but in real term-sheet haircuts. A $100M platform deal pitched on a shared Dropbox link gets valued at a different cap rate than the same deal on a Datasite or Peony room with per-LP access controls. That delta is far larger than the $40/admin/month it would have cost to avoid it.

What happens when I need to revoke one LP's access without disrupting the others?

When a LP passes on a deal and you need to cut their access, Peony's per-link revoke collapses the operation from a 20-email password rotation to a 30-second one-click cut — the other active LPs' links keep working unchanged. This is the single biggest operational advantage of per-recipient passwords over shared-link workflows.

The revoke workflow on Peony Business ($40/admin/month):

1. In the data room, go to Links → find the LP's personalized link (sorted by LP email)
2. Click Revoke access — the link's URL now returns a 403 page
3. (Optional) Add a note on the revoked link: "Passed on deal 4/18/26" for your CRM
4. Done — the other 19 LPs' links are untouched, their passwords still work, their analytics feeds keep logging

Time: under 30 seconds per revoke.

The counter-scenario on a shared-password Dropbox link:

1. LP passes — you need to cut their access
2. You can't cut one LP — the password unlocks the folder for everyone
3. You rotate the password — every active LP is now locked out
4. You email 19 LPs a new password — 2-3 will miss the email, 1-2 will reply "my password doesn't work"
5. You spend the next 24-48 hours fielding password-confusion support — and your diligence momentum dies

Across the 20+ IS data rooms Peony tested with per-recipient passwords in April 2026, median per-LP revoke time was under 30 seconds, with zero collateral impact on other active LPs. Compare that to the 24-48 hour password-rotation chaos typical of shared-link flows. For an IS running a compressed 90-day LOI-to-close window, those 48 hours are 2% of your total diligence timeline — gone, every time a LP passes.

The other operational benefit: selective re-activation. If a LP passed but comes back 2 weeks later ("actually, we'd like another look"), you re-enable their specific link in the same interface. Their password still works, their analytics feed resumes, their NDA acceptance is already on file — no re-onboarding friction. On a shared-link flow, this is impossible because you've already rotated.

How big is the leak risk in deal-by-deal capital raises?

The leak risk in an independent sponsor's deal-by-deal raise is structurally higher than in a committed-fund process because the LP pool is less vetted, the relationship depth is thinner, and the CIM is the single most sensitive document in the raise — so every forwarding incident cascades into competitive exposure, valuation pressure, and lost diligence momentum. The numbers make the risk concrete.

• 60-68% of data breaches involve a human element — most commonly, an authorized user forwarding a file to an unauthorized colleague, per the Verizon Data Breach Investigations Report (Verizon DBIR, 2024). In the IS context, this is exactly the mechanic by which a CIM lands in a competing sponsor's inbox.
• $4.88M — the average cost of a data breach in 2024, according to IBM's Cost of a Data Breach Report (IBM Security, 2024). For a $20M IS deal where the sponsor's closing fee is $400K, a leaked CIM that loses the deal to a competing bidder costs the sponsor far more than the breach statistic — the whole closing fee plus 4 years of management fee plus the carry.
• 0 seconds — the time it takes for a forwarded CIM PDF to become unrecoverable. Once a CIM is in the wild, you cannot revoke, watermark, or NDA-bind it retroactively.
• 2 — the number of forwarding incidents I've observed across six IS engagements advised since 2022. That's a 1-in-3 per-deal base rate for a first-time IS relationship graph — which is why per-recipient access discipline is not optional for institutional-scale raises.
• 47% of VDR vendors hide pricing entirely — 6 of 15 major providers require a sales call before they share any rate, per Peony's 2026 VDR pricing research. For an IS running deal-by-deal capital raises, this opacity makes it structurally difficult to budget LP data room costs — you cannot get quotes without calling 5 different sales teams first.
• 4 hours 12 minutes — the median time-to-first-LP-access after link send, across 20+ IS data rooms Peony tested with per-recipient passwords in April 2026. This is 10-20x faster than the 2-3 day lag typical of shared-link Dropbox flows (where LPs often ignore the delivery email or lose the password in their inbox).
• Under 30 seconds — median per-LP revoke time in the same 2026 testing cohort. The revoke speed is not a vanity metric — it is the operational cost difference between a disciplined raise and a raise that loses 2-3 days every time a LP passes.

The mitigation stack is well-understood — per-recipient passwords, dynamic watermarks, screenshot protection, NDA gates per LP tier, page-level analytics — but the cost of deploying it has historically been prohibitive for sub-$50M IS deals. Datasite at $25K-$100K per deal consumes 5-25% of a typical IS closing fee. Peony Business at $40/admin/month collapses that cost to under 1% of the closing fee on a $5M deal, and becomes effectively zero on a $100M platform deal.

The IS LP Access Matrix — How to segment 15-40 LPs into three tiers

Independent sponsors should segment every deal's LP list into three access tiers — repeat LPs from prior deals, net-new LPs in active diligence, and exploratory LPs from intros or conferences — and apply a graduated security stack (light, medium, heavy) to each tier. This is the IS LP Access Matrix, a Peony framework built specifically for the deal-by-deal capital-raise workflow. It's the operational translation of per-recipient password protection into a repeatable, per-LP configuration that matches each LP's actual confidentiality posture.

The three tiers segment on two axes: relationship depth (how well does the sponsor know the LP?) and likelihood of leak (how likely is this LP to forward the CIM to a third party, intentionally or otherwise?).

How to apply the matrix to a 25-LP raise:

• Sort your LP list into the three tiers using your prior-deal history and intro source. A typical $25M deal might split 10 Tier 1 / 10 Tier 2 / 5 Tier 3.
• In Peony Business ($40/admin/month), set up three NDA templates — one per tier — so that each new link inherits the tier-appropriate confidentiality posture.
• Configure the per-link defaults in Peony's link management so that Tier 2 and Tier 3 links auto-enable watermarks and analytics; Tier 1 links stay lightweight.
• Generate all 25 personalized links in one bulk paste, then assign each link to the appropriate tier.
• Deliver each tier's links via the appropriate channel — Tier 1 via your standard LP email list, Tier 2 via personalized intro emails, Tier 3 via the intro contact (with the intro copied).

Why the tiering matters: If you apply the Tier 3 stack to Tier 1 LPs (heavy watermarks, screenshot protection, download disabled), your repeat family offices feel micromanaged and your follow-up velocity drops — because they're now jumping through security hoops on a deal they would have funded quickly. If you apply the Tier 1 stack to Tier 3 LPs, your exploratory intros get full CIM access with no forensic attribution — which is exactly how CIMs leak to competing sponsors.

Cross-tier configuration: revoke and promote. The LP Access Matrix is dynamic — a Tier 3 exploratory LP who converts to active diligence gets promoted to Tier 2 (same personalized link, upgraded NDA template, watermarks stay on). A Tier 2 net-new LP who commits to funding gets promoted to Tier 1 on your next deal (stays in CRM, but this deal they already had Tier 2 posture). Failed conversions get revoked — not downgraded. The aggregate dashboard on Peony Business makes the tier transitions trivial to track across 15-40 LPs and 2-3 concurrent deals.

Who uses this framework: The IS LP Access Matrix is the operational framework Peony recommends to independent sponsors and boutique investment bankers advising ISes on deal-by-deal raises. It's featured in the IS cluster hub guide and cited in our best data rooms for independent sponsors comparison.

What are the best practical tips for running per-LP password workflows?

Never email the password in the same message as the link, rotate Tier 3 passwords every 60 days, use auto-generated passwords over memorable ones, force NDA re-acceptance when templates update mid-deal, cross-check your LP analytics feed before every follow-up call, and archive the full access log into your closing binder at deal close. These are the seven things I've learned advising six IS engagements on per-recipient password workflows.

Split the link and password into two messages. The security discipline that matters most: the link goes in one email (personalized delivery); the password goes in a second email (or, for Tier 3 LPs, a text message to the LP's mobile). This splits the compromise surface — a forwarded email with the link alone cannot unlock the room without the password. On Peony Business ($40/admin/month), the link-delivery flow supports this pattern natively — you copy the link, send in email #1; Peony shows the password in the admin panel, you send in email #2 (or via phone).

Rotate Tier 3 passwords every 60 days on a long raise. If your raise is running 90-120 days and you have Tier 3 exploratory LPs still in the room after day 60, rotate their passwords. Tier 1 and Tier 2 LPs don't need rotation because they're actively engaged; Tier 3 LPs who have gone quiet are a higher leak risk the longer they sit idle. The Peony password rotation workflow is per-link — rotate one LP's password in 15 seconds without touching the others.

Use auto-generated passwords over memorable ones. Peony's auto-generated passwords are 16-character alphanumeric with symbols — functionally uncrackable for any LP-scale attack surface. Memorable passwords ("IS-MapleDeal-2026") are easier to share accidentally, either in a forwarded email or via verbal reference on a call. For a deal-sensitive CIM, the auto-generated option is the default; you're not optimizing for the LP remembering the password (they'll have it in their inbox), you're optimizing against accidental disclosure.

Force NDA re-acceptance when templates update mid-deal. If you update your NDA template mid-raise — most commonly, tightening the non-solicit clause after a competitive-overlap LP enters diligence — use Peony's NDA re-acceptance feature (NDA gate configuration) to force all active LPs to re-sign the updated template. Each re-acceptance is logged separately with the new version hash. For a deal that ends up in front of counsel post-close, this gives you version-by-version audit trail showing every LP was bound to the most current terms.

Cross-check your LP analytics feed before every follow-up call. Monday morning check-in: open the aggregate dashboard, sort LPs by last-activity-timestamp, and identify (a) LPs who've opened the room since your last call — these are your hot follow-ups, (b) LPs who haven't opened the link 72 hours after delivery — these need a nudge, (c) LPs whose analytics show repeat visits to specific pages (management bios, financial model) — these are deep-diligence signals. This 2-minute check replaces the hour of "did anyone open the link?" Slack thread that consumes most IS ops time.

Archive the full access log into your closing binder at deal close. At deal close, export the access log CSV from Peony — every LP's password acceptance, NDA version, first-view timestamp, page-by-page engagement, and final status. This becomes the "LP Access Audit" section of your closing binder. For an IS running multiple deals, this archive is also useful for your next raise: LPs who engaged deeply on Deal A but passed are prime Tier 1 candidates for Deal B.

Never reuse a password across deals. Peony auto-generates a new password per link per deal, so this is the default — but it's worth reinforcing because some sponsors try to batch-reuse a password across deals to simplify their workflow. Don't. Each deal's passwords are unique; each LP's passwords are unique; compromises are contained to one link.

The bottom line — which tier do I actually need?

For an independent sponsor running deal-by-deal capital raises, the answer depends on deal size and LP composition. Here are the three most common IS scenarios and the Peony tier that fits.

$5M bolt-on deal, 12-15 LPs, mostly repeat. Peony Business at $40/admin/month. Why Business over Pro: you want the NDA gate for your 3-4 Tier 2 LPs, and the aggregate dashboard to track all 12 LPs in one view. Monthly cost: $40. Share of closing fee (at 2% of $5M = $100K): 0.04%. Functionally a rounding error.

$25M platform deal, 20-25 LPs, mixed Tier 1/2/3. Peony Business at $40/admin/month. Why Business: you need tier-differentiated NDA templates, per-LP watermarks for Tier 2/3, and screenshot protection for your Tier 3 intros. Monthly cost: $40. Share of closing fee (at 2% of $25M = $500K): 0.008%.

$100M platform deal, 30-40 LPs, heavy fund-of-funds and institutional. Peony Business at $40/admin/month, with optional custom branding and custom domain for institutional polish. Why Business: institutional LPs at this scale expect per-recipient access discipline by default; delivering the deal on a shared Dropbox link is a cap-rate-haircut signal. Monthly cost: $40. Share of closing fee (at 2% of $100M = $2M): 0.002%. Effectively free.

What Pro ($20/admin/month) covers and when it's enough: Pro includes per-recipient passwords, personalized links, per-LP page analytics, and revoke — the core of the stack. But Pro does not include the NDA gate (Business only) or the aggregate per-deal dashboard (Business only). For a first-deal IS with 5-8 LPs who are all repeat family offices from a prior firm, Pro may be sufficient. For any deal with 10+ LPs or any Tier 2/3 LPs in the mix, Business is the defensible choice.

What the free tier covers and when it's enough: Free includes personalized links and basic analytics, but not passwords and not NDA gates. It's adequate for early LP-relationship building (sharing a teaser with a prospective Tier 1 LP who has not yet committed to diligence), but not adequate for a CIM with 15-40 LPs in active diligence.

The honest tradeoff: For an IS running 2-3 concurrent deals, the $40/admin/month Business tier unlocks unlimited data rooms, which means your per-deal cost scales inversely with deal volume. At 1 deal per month, Business costs you $40/deal. At 5 deals per year, Business costs you $96/deal. At 10 deals per year, Business costs you $48/deal. Datasite's comparable posture scales in the opposite direction — more deals, more per-deal cost — because every new deal is a new $25K-$100K+ per-deal contract.

Frequently asked questions

I'm an independent sponsor raising $5M for a business services bolt-on — 12 LPs total, 4 repeat and 8 new. How do I set up different passwords per LP?

For a $5M business services bolt-on with 12 LPs, your per-recipient password workflow is: create one Peony data room for the deal, generate 12 personalized links (one per LP email), and set a different password on each link. On Peony Business ($40/admin/month), this takes under 5 minutes for all 12 LPs. Your 4 repeat LPs get light-friction passwords because they already know the sponsor relationship; your 8 net-new LPs get stronger passwords paired with a click-through NDA gate. Each link has its own analytics log, so you see which of the 8 new LPs actually opened the CIM versus which ghosted after password delivery. Dropbox and Google Drive have one password per folder at best — meaning if one LP forwards the password to a competing sponsor, you must rotate it for all 12.

I'm raising $25M for a manufacturing platform deal — LPs are a mix of repeat family offices and new fund-of-funds. Can I gate CIM access per group?

Yes. For a $25M manufacturing platform with mixed LP types, you use Peony Business ($40/admin/month) to tier access per group: repeat family offices get a personalized link with a light password; net-new fund-of-funds get a personalized link with a stronger password plus a click-through NDA gate plus dynamic watermarks. Each LP sees the same CIM pages but carries a different identity footprint on every screen view. The aggregate dashboard shows you engagement by group, so your follow-up prioritization is: "FoF #2 spent 14 minutes on the management bios — call them first; Family Office #5 only opened the teaser — send a reminder." Firmex charges $10K+ per deal for this granularity; Datasite charges $25K+. Peony ships it at the $40/admin/month baseline.

I'm a newer IS without a track record — how do I manage confidentiality for LP intros I get through Axial or ACG?

For a first-deal IS getting LP intros through Axial or ACG, the risk is that an intro relationship does not yet carry the confidentiality weight of a repeat LP. Your workflow on Peony Business ($40/admin/month) is: generate an individual personalized link for each Axial/ACG intro with a unique password, attach a standard mutual NDA on the link, enable dynamic watermarks with the LP's email, and disable download on the first-round CIM. If one intro forwards your materials, the watermark attributes the leak to the specific LP — something Google Drive or Dropbox can never do. For IS conferences like McGuireWoods Independent Sponsor Conference (MWISC), follow the same workflow for every business card you collected. Your IS cluster hub guide walks through the full LP engagement flow end to end.

My last deal had a forwarding incident — one LP sent my CIM to a competing sponsor. How do I prevent that on this deal?

For an IS with a prior forwarding incident, the remediation is three-layered on Peony Business ($40/admin/month): (1) per-recipient passwords so that when one LP forwards a password, you rotate only that single LP's credential, not the whole investor list; (2) dynamic watermarks that embed the LP's email on every CIM page, making post-incident attribution possible; (3) screenshot protection that blocks and logs any capture attempt. Pair this with download disabled on the first-round CIM. Your next forwarding incident becomes a one-click revoke and a forensic trail showing exactly which LP leaked. Dropbox and Google Drive have shared passwords and no watermarks; DocSend has page analytics but no screenshot protection or NDA gates.

I'm running 3 concurrent deals right now — unique passwords per LP per deal means 60+ passwords to track. How do I manage that without a spreadsheet nightmare?

For an IS running 3 concurrent deals with 20 LPs each, you never track 60 passwords in a spreadsheet — Peony Business ($40/admin/month) generates passwords at link creation time and embeds each password in the delivery email itself, so the LP receives "your data room link: [URL], your password: [string]" in one message. You do not need to remember any password; the aggregate dashboard shows you per-LP engagement across all 3 deals in one view. You get unlimited data rooms on Business, so your $40/month covers all 3 concurrent deals. A banker running the same 3 concurrent deals on Datasite would pay $75K-$300K per year in per-deal fees. The aggregate dashboard is the feature that turns per-recipient password management from a nightmare into a 2-minute-per-week check-in.

I need to revoke one LP's access after they passed — how do I do that without rotating passwords for the other 20 active LPs?

For an IS with 20 active LPs where one LP passed and you need to cut their access without touching the other 19, Peony Business ($40/admin/month) gives you per-link revoke in under 30 seconds: go to the data room, find the LP's personalized link, click revoke. Their URL now returns a 403 page; the other 19 LPs' passwords still work. This is the single biggest operational advantage of per-recipient passwords over shared-link workflows. On Dropbox or Google Drive, revoking one LP means rotating the shared password for everyone else — a 20-email notification with a new password that some LPs will miss, leading to support tickets mid-diligence. Across 20+ IS data rooms Peony tested with per-recipient passwords in April 2026, median per-LP revoke time was under 30 seconds.

I'm a law firm advising an IS on a continuation-vehicle transaction — can per-recipient passwords hold up to SEC scrutiny?

Yes. For a law firm advising an IS on a continuation-vehicle transaction, per-recipient passwords on Peony Business ($40/admin/month) produce a court-admissible audit trail: each LP's access event is logged with email, IP address, timestamp, password hash, and the exact CIM version they accessed. The audit log meets the evidentiary standard the SEC and courts apply to software EULAs under Specht v. Netscape (2001). For a continuation vehicle, pair per-recipient passwords with the click-through NDA gate (Business-tier feature) so that each LP's acceptance is bound to both a password and a signed acknowledgment. Datasite and Intralinks deliver comparable audit evidence but gate it behind enterprise SKUs at 10-30x the cost. For SEC-scrutinized deals, the combination of per-recipient password + identity-bound link + NDA audit log is the cheapest defensible posture in the market.

I'm raising from 40 LPs across 15 family offices — is there a bulk workflow to generate 40 personalized links?

Yes. For an IS raising from 40 LPs across 15 family offices, Peony Business ($40/admin/month) supports bulk link creation: paste 40 emails into the link generator, and Peony creates 40 personalized links with individual passwords in a single action. Each link has its own per-LP analytics feed, its own revoke button, and (if you enable it) its own NDA acceptance log. The aggregate dashboard then ranks all 40 LPs by engagement depth — time on CIM, pages viewed, return visits — so your follow-up calls get prioritized by actual behavior. For 40 LPs, the manual alternative (Dropbox shared folder, one password, individually-emailed passwords) costs you the ability to track, watermark, or selectively revoke. Our best data rooms for independent sponsors guide compares 8 VDRs against the IS dual-data-room workflow — Peony is the only one with bulk personalized links at the $40/admin/month tier.

I'm an IS pitching LPs on a $100M platform deal — how does per-LP password compare to a shared dropbox link with one password?

For an IS pitching a $100M platform deal, a shared Dropbox link with one password is a disqualifying weakness in front of fund-of-funds and institutional LPs. On Peony Business ($40/admin/month), per-LP passwords give you three things a shared Dropbox link cannot: (1) per-LP engagement analytics — you see which of 25 LPs actually opened the CIM; (2) per-LP revoke — one LP passes, you cut only their link; (3) dynamic watermarks per viewer — if the CIM leaks, you attribute it forensically. Institutional LPs at the $100M platform level expect this posture. Presenting a Dropbox link signals to an FoF that your operational discipline is pre-institutional — which is a cap rate they will discount. Peony Business at $40/admin/month closes that gap for less than one hour of associate time.

My deal closed — how do I archive LP access for the closing binder but still let my closing counsel view?

For an IS at deal close, your per-LP access archive goes into the closing binder in two parts on Peony Business ($40/admin/month): (1) the access log export — a CSV with every LP's password acceptance, first-view timestamp, page-by-page engagement, and final status (funded, passed, ghosted); (2) the signed NDA PDFs from the Agreements tab, one per LP. For your closing counsel, you generate a dedicated counsel link with full data room access and an extended 180-day expiry — separate password from the LP links, tracked independently. This gives your closing binder a defensible record of every LP's data access discipline, plus live counsel access during the post-close true-up period. Datasite charges $2K-$5K per deal for equivalent audit exports; Peony ships it at the $40/admin/month baseline.

Related resources

• What Is an Independent Sponsor? Complete Guide — the IS cluster hub covering deal mechanics, economics, and capital partners
• Best Data Rooms for Independent Sponsors — 8-VDR comparison against the IS dual-data-room workflow
• How to Require an NDA on a Pitch Deck (Click-Through) — founder-side click-through NDA playbook
• How to Set Up a Click-Through NDA for M&A Data Rooms — M&A banker's NDA playbook for sell-side auctions
• Virtual Data Room Features Guide — cluster hub for VDR feature selection
• Document Security Software Guide — cluster hub for secure document sharing
• Virtual Data Room Cost Guide — Peony's 2026 VDR pricing research (47% of VDRs hide pricing)
• How to Password Protect Any Folder — canonical password-folder how-to (single document, single password)
• How to Password Protect a Google Drive Folder — Google Drive-specific password workflow
• Independent Sponsor Conferences & Forums 2026 — 21 events mapped for IS LP pipeline
• Data Room Folder Structure Guide — standard IS CIM taxonomy for AI auto-indexing