View-only access
Permission to read a document on screen without the ability to download, print, or copy it.
View-only access is a permission state in which a data room lets a person open and read a document on screen, yet strips away every action that would let them keep a copy. There is no download button, no print option, no text selection to copy, and often no save-as. The file is streamed to the browser as protected output rather than handed over as a portable copy, so it never lands intact in the reader’s downloads folder, email, or local drive. It is the difference between letting someone look at a document across a desk and letting them walk out with it. In a virtual data room this single setting is the workhorse of confidentiality: it keeps sensitive material readable by the people who need to review it while ensuring the file itself stays inside the room where every action is logged.
How does view-only access work in a data room?
At the technical level, view-only access is enforced at the rendering and permission layer, not by trusting the reader to behave. When a permitted user opens a file, the room renders each page as an image or a protected stream and withholds the underlying source file, then disables the browser and interface controls that would export it. Administrators normally set it as one option on a permission profile, alongside download, print, and edit, and apply it at the level of a folder, a single file, or a user group.
That granularity matters. Through granular permissions an administrator can grant the seller’s own advisers full download rights while holding every outside bidder to view-only on the same folder, so one document library serves several audiences at once. For a fuller picture of how these tiers stack up, our guide on data room permissions explained walks through the common profiles and when to use each.
Why does view-only access matter for M&A and due diligence?
In a sell-side deal or a fundraise, you invite competing bidders, their lawyers, and their advisers to page through your most sensitive material: financial models, customer contracts, cap tables, and employee data. Most of those people should never be able to retain a copy once the process ends or once they drop out of the running. View-only access is what makes that possible. It lets a bidder evaluate the business thoroughly without ever holding a downloadable version they could keep, forward, or feed into a competing product.
The control is also reversible in a way a download never is. If you grant download rights and a party later exits the deal, the file is already gone; with view-only access you simply revoke their entry and the material stays contained. Our guide on how to grant and revoke data room access covers that lifecycle in detail. View-only access is rarely used alone, though. Serious rooms layer it with dynamic watermarking, which stamps each page with the viewer’s identity, and fence view, which degrades what a phone camera can capture, so the same file can be neither exported nor cleanly photographed.
A concrete example
A founder raising a Series B opens a data room to five venture funds. The financial model and the customer contract folder are set to view-only for every fund, watermarked with each partner’s name and email. Three funds pass. Because nobody outside the founder’s own advisers ever had download rights, there is no copy of the model sitting in a declining fund’s shared drive, and no follow-up cleanup to chase. The founder revokes the three funds’ access and the material stays inside the room. Had those folders been downloadable, the sensitive model would already be beyond recall.
How should you evaluate view-only access?
Treat view-only as a strong but not absolute control, and test how each vendor implements it rather than trusting the feature checkbox. The weak point is always the screen itself: a viewer can still read the page, so a determined person can photograph it or retype figures. That residual gap is exactly why watermarking and fence view exist as companions.
| What to check | Good sign | Warning sign |
|---|---|---|
| Scope | Set per file, folder, and user group | One global switch only |
| Print handling | Print is blocked or produces a watermarked, logged copy | Print quietly yields a clean PDF |
| Rendering | Streamed as protected pages, nothing cached | Original file reachable in the browser cache |
| Pairing | Combines with watermarking and fence view | Sold as a standalone anti-leak fix |
When you compare providers, look at how these permission controls are packaged and priced. Our side-by-side comparison shows which vendors include granular view-only controls in their standard tier, and individual provider reviews note how each held up in hands-on testing. Pricing across the site is indicative; confirm the current figure with the provider.
FAQ
Does view-only access stop someone from copying a document completely? No. It removes the download, print, and copy actions, so no intact file leaves the room, but the reader can still see the page on screen. That means a determined person could photograph the monitor or retype figures. To close that gap, view-only access is normally paired with dynamic watermarking, which ties any captured image back to the viewer, and fence view, which breaks up what a camera can record.
What is the difference between view-only access and granular permissions? View-only access is one specific permission state: read on screen, no export. Granular permissions is the wider system that lets an administrator assign different rights, including view-only, download, print, or edit, to different people on different folders. View-only access is one setting you apply through a granular permissions model.
Can view-only access be revoked after someone has read a file? Yes, and that is one of its main advantages. Because no copy ever left the room, revoking a person’s access removes their ability to see the document entirely. There is no downloaded file to chase, which is why view-only is the default for outside parties in a competitive process.
