Most data rooms send their own system invitation, a short automated message with a sign-in link. That message is necessary, but it is not enough. It says nothing about the deal, the rules or who to call when the link fails at 11pm the night before a bid deadline.
So send two things: the platform’s automated invite, and a personal cover email from the deal lead that arrives at the same time. This guide gives you that cover email in four versions, explains each part, and covers what to do when people do not log in.
What is a data room invitation email?
A data room invitation email is the message that grants an outside party access to a virtual data room and sets the terms of that access. It usually pairs an automated sign-in link from the platform with a cover note from the seller, company or adviser that names the project, restates the confidentiality obligations and explains how the room works.
Treat it as part of the deal record. If there is ever a dispute about what a bidder was told, the invitation is where the rules were first stated.
What should every invitation contain?
Here is the shape of a good cover email, element by element.
Anatomy of a data room invitation email
Not every element applies to every audience. A fundraise invitation to friendly investors can be lighter than a sell-side invitation to competing bidders, and your own advisers need operational detail rather than warnings.
| Element | Bidders in a sale | Investors in a raise | Outside advisers | Late joiner on an existing team |
|---|---|---|---|---|
| Project code name in subject | Yes | Optional | Yes | Yes |
| NDA reminder | Yes, explicit | Yes, brief | Engagement letter instead | Yes, confirm they are covered |
| Sign-in and two-factor steps | Yes | Yes | Yes | Yes |
| Rules of the room | Full set | Short version | Full set | Point to the original rules |
| Q&A process | Yes | Usually calls instead | Yes, with their routing role | Yes |
| Key dates | Bid deadlines | Target close | Internal deadlines | Current round dates |
| Support contact | Yes | Yes | Yes | Yes |
| Which folders they can see | No, never list | No | Yes, if they will answer questions | No |
The last row matters. Never describe the permission structure to bidders, and never name other parties in the room. Both reveal more about your process than you intend.
Template 1: inviting bidders in a sale process
Use this for first-round bidders after their NDA is signed. Swap the bracketed fields.
Subject: Project [Code Name]: data room access
Dear [First name],
Thank you for signing the confidentiality agreement
for Project [Code Name]. You will shortly receive an
automated invitation from [Provider] to the data room.
Access
- Follow the link in that email to set your password.
- Two-factor sign-in is required on first login.
- Access is personal. Please do not share credentials;
ask us to add colleagues instead.
Rules of the room
- Everything in the room is covered by the
confidentiality agreement dated [date].
- Documents carry a watermark with your name and the
time of viewing.
- Please send all questions through the Q&A module,
not by email or phone, so every bidder gets a
consistent process.
- Downloads are disabled for some folders.
Timetable
- Indicative offers are due by [date and time zone],
as set out in the process letter.
Support
For access problems, contact [Name], [phone],
[email]. For questions about the process, contact
me directly.
Kind regards,
[Name], [Title], [Firm]
Two things to notice. The email does not include the room link itself; the platform sends that separately, so a forwarded cover note does not grant access. And it points to the process letter for the timetable rather than restating every deadline, which keeps one source of truth.
Template 2: inviting investors to a fundraising room
Investor rooms are friendlier and less formal. The NDA may be a light confidentiality clause or none at all; many institutional investors decline to sign NDAs at the early stage, so check what applies before you write the reminder.
Subject: [Company] Series [A] data room
Hi [First name],
Great to talk on [day]. As promised, you'll get an
invite from [Provider] in the next few minutes to our
data room.
Inside you'll find the financial model, cap table,
customer metrics, key contracts and the team's
details. The index on the first page shows where
everything sits.
A few notes:
- Please treat everything as confidential under
[our NDA / the confidentiality terms we discussed].
- Files are watermarked; the model is view-only.
- Two-factor sign-in is switched on.
We're aiming to close the round by [month]. Happy to
walk you through the numbers on a call; just reply
with a couple of times that suit.
If the link doesn't arrive, check spam or ask
[Name] at [email].
Best,
[Name]
Template 3: adding outside advisers
Advisers, such as your lawyers, accountants or the investment bank’s analysts, need operational detail. They will often be answering questions as well as reading.
Subject: Project [Code Name]: your data room access
and Q&A role
Hi [First name],
You've been added to the Project [Code Name] data room
as a [contributor / Q&A responder] for [workstream,
e.g. tax].
What you can do
- View and upload in [folder numbers].
- Draft answers to questions routed to the [category]
queue. All answers are approved by [Name] before
release to bidders.
House rules
- Use the agreed file naming pattern:
[section number]_[document name]_[YYYY-MM-DD].
- Do not delete or renumber files once bidders have
seen them; upload a new version instead.
- Target response time for questions: [48 hours].
Shout if anything looks wrong in your folders.
Thanks,
[Name]
Template 4: the reminder for people who have not logged in
Send this about 24 hours after the original invitation to anyone the activity log shows has not signed in.
Subject: Re: Project [Code Name]: data room access
Hi [First name],
Our records show you haven't signed in to the
Project [Code Name] data room yet. The invitation
came from [provider's sending address] and is
sometimes caught by spam filters.
If you can't find it, reply and we'll resend it, or
ask your IT team to allow emails from [domain].
Kind regards,
[Name]
When should invitations go out, and how do you follow up?
Timing affects how many people actually get in on day one. A practical rhythm for a sell-side process:
| When | What to do | Why |
|---|---|---|
| A week before | Ask each bidder’s lead for a full list of names and email addresses | Avoids drip-feed additions on launch day |
| Day before | Send lead contacts a heads-up to allow the provider’s domain | Bank and fund spam filters are strict |
| Day 0, morning | Send platform invitations and cover emails together, in the recipients’ working hours | People act on emails that arrive while they are at their desks |
| Day 0, end of day | Check the activity log for sign-ins | Catch bounced or filtered invitations early |
| Day 1 | Send the reminder template to anyone who has not signed in | Most problems are spam or a typo in the address |
| Day 2 | Call the lead contact for any team still missing | A bidder that has not logged in by now may be losing interest, or may have an IT block |
| Ongoing | Add new users only on request from the lead contact | Keeps the list controlled and auditable |
Across time zones, send in batches: Asian bidders at the start of their day, European and American teams at the start of theirs. A single send at midnight in someone’s time zone sits under fifty other emails by morning.
How do you write the rules of the room?
Rules work when they are few and specific. Five is plenty for most processes:
- Confidentiality. Everything in the room is covered by the signed NDA, including information learned from Q&A.
- Watermarks and tracking. Files are watermarked with the viewer’s name, and activity is logged. Saying so plainly deters casual screenshots.
- Questions through Q&A only. No side emails to management. This protects fairness between bidders and keeps answers approved.
- No credential sharing. Each person gets their own login; leads request additions.
- No contact with staff, customers or suppliers. Unless the process letter allows it.
Put them in the cover email for the first invitation and in a “Read me first” document at the top of the room. Later joiners then get the same rules without a fresh email from you.
What should you check before you press send?
- Every recipient has signed the NDA or is covered by their firm’s NDA.
- Email addresses match the firm’s domain; check for look-alike domains and personal addresses.
- Each user is in the right permission group, previewed as that group.
- Watermarks and two-factor sign-in are switched on for outside groups.
- The “Read me first” document and index are at the top of the room.
- The cover email names a support contact who is actually available that week.
- No other party is named in the email, in the CC line or in a group distribution list.
- Invitations are sent individually or by BCC per firm, never one email to all bidders.
The CC mistake is more common than you would think. One email to all bidders with every address visible tells each of them exactly who they are competing against.
Picking a room for your process? Our quiz suggests providers that fit your deal type, number of outside users and budget.
Take the quizWhat changes for a second round or a late joiner?
Second round. Shortlisted bidders already have access, so you are expanding permissions, not inviting. A short note does the job: which new folders are open, the new deadlines, any change in Q&A limits. Bidders who did not progress need a separate, courteous email and immediate removal of access; check the activity log afterwards to confirm they cannot sign in.
Late joiners. A new member of a bidder’s team, such as a specialist adviser brought in for round two, needs the platform invite and a one-paragraph cover email that confirms they are covered by their firm’s NDA and points to the “Read me first” document.
Removal. When someone leaves a team, disable the account the same day. A short confirmation to the lead contact (“We have removed [Name]‘s access as requested”) keeps the record clean. If you are still building the room, our guide to setting up a data room covers the permission groups these emails depend on.
Frequently asked questions
Should the data room invitation come from the platform or from me?
Both. The platform sends the secure sign-in link; your cover email explains the project, the rules and who to contact. Sending only the automated invite leads to confused recipients and missed logins.
What should the subject line of a data room invitation say?
Use the project code name and the word access, for example 'Project Falcon: data room access'. Avoid the company's real name in a sale process, because subject lines are visible in previews and logs.
Do I need to attach the NDA to the invitation?
No. Refer to it by date and parties. Attaching it adds clutter and another copy of a sensitive document in inboxes.
What if invitations go to spam?
Ask lead contacts to allow the provider's sending domain before launch, check the activity log at the end of day one, and resend or call anyone who has not signed in within 24 hours.
Can I invite everyone in one email?
Not in a sale. Send individually or by firm with BCC, so no bidder learns who else is in the process. For a fundraise, separate emails per investor are still the safer habit.
