The client could finally run its transaction rooms on the product, and the contract closed before its renewal with its existing data room vendor.
Turning file sharing into
a confidential deal room
I led the design of three connected controls that let Diligent’s Secure File Sharing run confidential, high-stakes transactions, and helped win an enterprise client.
Data-room controls the product can now package as a standalone proposition for future enterprise clients.
A legal access gate, update notifications and concealed identities, designed to work together under a hard deadline.
A file-sharing tool
pushed into data-room territory
An enterprise prospect wanted to run confidential transactions on Secure File Sharing. We had about three months, before its renewal with its current data room vendor. I led the design end to end.
Six weeks for discovery, requirements and prototypes, shifting priorities, slow access to users, and no internal plan for VDR expansion. That forced fast decisions and scope cuts, and made a cohesive system matter more than three quick fixes.
Where the data room sits in a high-stakes deal
I mapped the lifecycle of an aircraft-leasing deal, from initiation to close. All three controls act in the setup and opening stages, where confidentiality, awareness and identity matter most.
Three roles, one shared need: control over who sees what
Each deal puts legal, financial and technical teams in one room, reviewing sensitive files under strict confidentiality and audit requirements. Three roles shaped the work.
Board admins & legal
“Two bidders, one room. Before anyone opens a file I need their agreement on record, and I need to show who accepted which version. Without that, legal won’t let the deal run here.”
Collaborators
“I’m reviewing four hundred documents against a deadline. Tell me when something changes so I’m not working from last week’s version, and please don’t send me forty emails a day.”
IT administrators
“I don’t want a new exception to explain to the auditor. Whatever the deal team switches on has to fit our policies and leave a trail I can pull on request.”
Everyone accepts the terms before they enter
The client required a confidentiality agreement that every user accepts before opening a room. The goal: legal consent that stays quick and clear.
Managers set consent up once in Policies. They upload the client’s agreement as a PDF instead of pasting text, and preview the screen as users will see it before publishing. They can update or switch it off at any time.
A minimal consent screen on first access, with confirmation when the user agrees and a link to the full document. Collaborators can return any time to view or download the version they accepted.
Keeping the deal aligned without flooding inboxes
Once a room opens, hundreds of collaborators work in it at the same time. They need to know when files change, every change must reach the audit log, and no notification can reveal a masked identity.
Change emails are switched on at group level, so each party hears only what it should.
Uploads and updates in one summary, deletions excluded. Every change still lands in the activity report.
Competing bidders in one room, identities hidden
The hardest challenge. Competing buyers, investors and advisers often share a room, and some groups must not identify each other. Admins keep full visibility, and every action stays auditable.
My first instinct was wrong
I first considered hiding members by default, but that would change the core behaviour for every customer. Instead, a VDR mode switch hides all members and turns off external sharing, and a new “Allow member visibility” permission sits on the existing model. Customers who never turn it on see no change.
Visibility gates the rest
Member visibility has to be granted before the permissions that depend on it, so no one manages people they cannot see.
States you can read at a glance
People sit in several groups, some masked. Member details show only in groups where the viewer has “view” permission, and status icons in the member and group tables show notification and visibility state. Admins can preview masking before applying it.
Admins see who did what, and when.
Identifiers are removed from file activity, version history, content views and notification emails, yet every action stays traceable.
Demo sessions with the client
I presented interactive Figma prototypes across several sessions with the client, the Product Manager, the Account Manager and the Solution Engineer. With no direct line to end users, this was the fastest way to align on requirements and avoid rework. It is stakeholder validation, not usability testing.
Closed, won
The three controls were built as one coherent proof of concept inside the roughly three-month window, and the deal closed with the client. Secure File Sharing now has data-room controls Sales can package for new enterprise engagements, not a one-off accommodation.
What this project taught me
Being proactive in client communication
Client co-creation drove clarity, but communication was fragmented, with limited access to key users and slow feedback cycles. Once we began demoing the first concepts in Figma, alignment improved, but some key stakeholders often missed sessions, slowing validation.
When time is short, early and continuous alignment is a must have not a nice to have
Next time, I'd organize more workshops, especially early in discovery. Not doing so this time led to on-the-fly adjustments during design and implementation. Structured early sessions would have helped map flows, catch dependencies, address design conflicts, and collect questions more efficiently for client calls.