Everyone Should See Everything? Mamma Mia. That Is Not Collaboration.
Giving everyone access to everything is not teamwork. Build role-based Deal Room access that protects decisions, trust, and client sign-off.
Friday, 3:47 PM. The Wrong Person Has the Right File.
The CFO calls.
Not to approve the recommendation.
Not to compliment the financial model.
To ask why a junior external reviewer can see the confidential negotiation assumptions.
Fantastic.
We are thirty minutes from the investment committee call, and instead of discussing EBITDA, we are discussing access permissions.
The Engagement Manager says, “We thought it would be easier if everyone could see everything.”
Mamma mia.
Easier for whom?
Certainly not for the CFO.
The file was not ready for that audience. The numbers were preliminary. Now the client wants to know who else has opened it.
And our beautiful Deck?
Completely irrelevant until we answer that question.
This is what happens when we confuse transparency with unrestricted access.
Collaboration needs visibility. But visibility needs structure.
The fix is simple: organize the Deal Room around roles, tasks, and decisions.
Not around the fantasy that everyone needs every file.
The Old Way
I have heard this sentence in more project meetings than I care to remember.
“We’re all one team. Everyone should have access.”
Sounds inclusive.
Sounds modern.
Sounds like something someone says five minutes before sharing the entire project directory with forty external stakeholders.
No grazie.
A client engagement is not one conversation.
It is several conversations happening at different levels of maturity, sensitivity, and accountability.
The analysts need working assumptions.
The Workstream Lead needs the latest analysis and comments.
The Executive Sponsor needs a recommendation, supporting evidence, and a clear decision.
The external advisor may need only a narrow set of approved exhibits.
These are different jobs.
Why are we giving everyone the same interface?
Imagine walking into a restaurant and being handed the kitchen’s purchasing invoices, staff schedules, and supplier negotiations instead of the menu.
More information does not mean a better experience.
It means more questions.
The same principle applies to a Deal Room.
When every stakeholder sees every draft, three things happen.
First, preliminary data starts circulating as though it were final.
Second, sensitive information reaches people who have no business using it.
Third, the team spends valuable time explaining documents that were never intended for that audience.
Suddenly, the delivery team is not delivering.
It is managing the consequences of overexposure.
Total visibility creates noise. Structured visibility creates decisions.
The Deliverable
Forget the giant permissions spreadsheet that nobody updates.
We need a simple access model that reflects how the engagement actually works.
Start with four practical roles.
1. Executive Sponsor: The Decision View
The sponsor sees approved recommendations, executive summaries, key graphs, decision logs, and materials awaiting sign-off.
No cluttered working folders.
No fifteen versions of the financial model.
One obvious route to the decision.
2. Workstream Lead: The Review View
The Workstream Lead sees relevant working analyses, review-ready deliverables, open comments, and assigned decisions.
They can review, comment, and approve within their authority.
They should not automatically see unrelated confidential workstreams.
3. Delivery Team: The Working View
Analysts and consultants access the files required to produce their assigned deliverables.
Models. Source data. Draft graphs. Supporting evidence.
Access is determined by assignment, not by the fact that their email address ends with the correct company domain.
4. External Reviewer: The Approved View
External reviewers see precisely the approved documents relevant to their task.
They can review or comment where authorized.
They do not get a backstage pass to internal debates, negotiation strategies, or unfinished recommendations.
Assolutamente.
Design Permissions Around the User Journey
Now comes the important part.
Do not make permissions feel like obstacles.
A reviewer should not need to request access four times before reaching the approved Deck.
The permissions should already match the expected workflow.
I use a straightforward sequence:
Draft → Review → Approved → Client Decision
Each stage has a defined audience.
Drafts remain within the authorized working team.
Review-ready materials go to the designated reviewers.
Approved deliverables become visible to the intended client audience.
Decision documents reach the people accountable for sign-off.
The transition between stages is deliberate.
Nobody should assume that uploading a file means publishing it to the entire engagement.
This is also why I prefer one well-structured Deal Room over uncontrolled copies scattered across different systems.
The client gets one destination.
The permission model determines what they can see.
One link does not mean one permission level.
Speed Is Not an Excuse for Lazy Access
“But Paolo, we are moving fast. We cannot wait three days for IT to configure permissions.”
Agreed.
We need fast execution.
Use approved role templates. Assign an access owner. Give that owner a backup. Define how urgent requests are handled.
If someone needs additional access, ask what task requires it, verify approval, and grant only the necessary scope.
Do it quickly. Record the change.
Do not solve a twenty-minute access problem by granting permanent visibility to everything.
That is not speed.
That is a future incident waiting for a calendar invitation.
And please test the experience using the actual intended roles before sending the invitations.
The internal administrator’s view is not the client’s view.
A room that looks perfect to the administrator may look completely different to the CFO.
The Real Test: Does the Right Person See the Right Decision?
Before publishing, I ask three questions.
Can the Executive Sponsor find the approved recommendation immediately?
Can the Workstream Lead review the supporting analysis without requesting unnecessary permissions?
Can an external reviewer complete their assigned task without discovering unrelated sensitive material?
If yes, the room is doing its job.
If not, the access model needs work.
This is not about becoming obsessed with security settings.
It is about professionalism.
Clients do not pay premium fees to browse our internal working mess.
They pay for clear analysis, controlled delivery, and confident decisions.
Give them the information they need.
Give them the right context.
Give them a clean path to approve.
We are not trying to maximize the number of documents someone can open.
We are trying to minimize the time between understanding the recommendation and signing off.
That is collaboration.
The rest?
Mamma mia. That is just oversharing with a login screen.
FAQs
Should everyone on a client project have access to every document?
No. Access should reflect each person's role and responsibilities. Broad visibility can expose sensitive drafts, confuse reviewers, and slow decisions. Give people what they need to do their job.
How do I organize permissions for external clients and internal teams?
Define a small set of roles, map each role to approved folders and actions, and test the experience before inviting users. Keep internal working material separate from client-approved deliverables.
Does restricting file access make collaboration slower?
Not when the room is designed correctly. Clear roles, predictable approval rules, and a simple access-request process reduce confusion. The goal is fast access for the right people, not unlimited access for everyone.