DEV Community

Cover image for They Needed to See It. They Didn't Need a Copy.
Ella Brooks
Ella Brooks

Posted on

They Needed to See It. They Didn't Need a Copy.

A client asks to review a contract.

A lawyer needs to check one clause.

A partner wants to see the numbers before a meeting.

The usual answer is simple.

Send the file.

And just like that, a review becomes a copy.

The file lands in a downloads folder.

It gets attached to another email.

It sits on a laptop that does not belong to you.

The person only needed to read it.

They now have it.

Seeing it and keeping it are not the same

One is a look.

The other is a transfer.

Most sharing tools treat them as the same action.

Open the link.

Download the file.

Save it.

Forward it.

The original purpose was a review.

The result is another copy you cannot call back.

A review should stay a review

View-only access is meant to keep that line in place.

The recipient can open the information.

They can read what they were asked to read.

Where the control is supported, download, forwarding, and capture stay limited, so the review does not quietly become a second file.

The owner still sets the level.

A client might only view.

A lawyer might receive a narrower permission than a full handoff.

A teammate might get a different level entirely.

Same information.

Not the same rights.

The look can end

When the review is finished, access can expire.

If it was shared with the wrong person, it can be revoked.

The look ends.

The copy was never handed over.

People still need to see sensitive work.

Contracts. Financials. Project files. Client details.

The answer is not to hide the document.

It is to stop treating every review as a reason to give the file away.

They needed to see it.

They did not need a copy.

Vaultrix — Control After Sharing.

Top comments (0)