Secure file access is about who can open it, and for how long

    · 7 min read

    Secure file access is the part of file security that happens after you've shared something. Who can open it, how long that stays true, whether you can take it back, and whether you'd even know if someone else got in.

    Most advice stops at where the file is stored. That's a different question, and there's a separate piece on document storage security if you want it. This one is about the moment the file leaves your hands, because that's where I've seen things go wrong.

    Access is four decisions, not one setting

    When people say they want secure file access, they usually mean a password. A password is one control, and not a great one on its own. I think about access as four separate decisions, and a file is only properly controlled when you've made all of them on purpose.

    1. Who can open it.
    2. When it stops working.
    3. Whether you can shut it off early.
    4. What you can see once it's open.

    Skip any one and there's a gap. A named recipient with no expiry still has the file in two years. An expiry with no revoke means you wait for the clock when you've just realised you sent it to the wrong person. Tracking with no limit on who opens it tells you about a leak after the fact.

    Who can open it matters more than how it's locked

    The weakest setup is "anyone with the link". The link becomes the credential, and links get forwarded, pasted into chats and left in old email threads. I covered the mechanics in the piece on direct link file sharing, but the short version is that possession of a URL isn't proof of anything.

    The better default is to limit access to the people you meant to send it to. On LiveDocument you can restrict a link to specific email addresses, so a forwarded copy doesn't quietly work for a stranger. It's a simple idea, and it's the one control I'd set on almost everything.

    It isn't identity verification in the enterprise sense, and I'd rather say that plainly. It's a sensible gate for a proposal, a report or a one-pager. If your process needs recipients to sign an NDA before they see anything, or you need watermarks on every page, LiveDocument doesn't do either, and you want a data room instead.

    Expiry stops a good decision going stale

    Sending someone a file made sense on the day you sent it. It might not make sense in three months, when the deal is dead, the contractor has moved on or the pricing has changed.

    When I was running growth at a data company I sent a lot of decks and proposals, and I almost never thought about when they should stop working. Old pricing sitting reachable long after the numbers changed isn't a leak, exactly. It's a file that outlived its reason, and that's how most access problems start.

    An expiry date fixes that without any effort from you. You pick a date when you share, and the link stops opening after it. For a proposal I'd set it a bit beyond the decision date. For a contractor, I'd set it to the end of the engagement.

    Think of expiry as the default and permanent access as the exception you justify.

    Revoking is for the mistake you've just made

    Expiry handles the slow case. Revoke handles the fast one: the wrong address, the wrong version, the recipient who left the company, the file you shouldn't have sent at all.

    This is the clearest difference between a link and an attachment. An attachment is a copy. Once it's in someone's inbox, you can't reach into it. A link is a pointer, so you can cut it. That's the whole argument for sending a PDF as a link rather than attaching it, and it's the reason I keep going on about it when people ask whether sending documents over email is safe.

    Two caveats worth knowing. Revoking stops the link opening. It can't un-send something a person already saved or screenshotted, so for anything where that's the real threat, you're managing trust as much as technology. And it only works if you remember it exists, so know where the control lives before you need it in a panic.

    Tracking tells you whether the control is working

    The fourth decision is visibility. Once a link is out, I want to know whether it's being opened, by whom, and which pages they spent time on.

    That's partly a sales question, and PDF tracking on LiveDocument shows page-level activity for exactly that. It's also a security signal. A proposal opened ten times by people you never mentioned it to is a reason to look at who has the link, and to revoke it if the answer is unclear.

    Be honest about what it is, though. Page-level analytics tell you what happened on a shared document. They aren't a formal audit trail for a regulated environment. If you have compliance obligations, the questions to ask a tool are in the guide to security compliance requirements, and you should ask them before you rely on any vendor.

    A routine that takes a minute

    This is roughly what I do with anything that isn't public.

    • Restrict the link to the named recipients.
    • Set an expiry that matches how long the file is useful.
    • Check I can find the revoke control before I send.
    • Turn on tracking so I'd notice something odd.
    • Open the link myself in a private window, to see exactly what a recipient sees.

    None of that is clever. The value is doing it every time, not just for the files that feel sensitive. The ones that bite you are the ones that didn't feel sensitive when you sent them.

    Where this fits with the rest of your setup

    Access control doesn't replace the layers around it. How a transfer is protected in transit, and which protocols sit underneath, is covered in the guide to secure file exchange. For a quick comparison of methods by what's in the file, there's the piece on the best way to share confidential documents.

    LiveDocument itself is not file storage and it isn't a data room. It takes a PDF or an image, turns it into one link with an optional video walkthrough, and lets you expire or revoke that link and see how it's read. If you want a quick look at the basics, the file sharing software page sets out what it covers and what it doesn't.

    FAQ

    What does secure file access mean?

    Secure file access means controlling who can open a file, for how long, and whether you can cut that access off. It's separate from where the file is stored or how it's encrypted. It's about the sharing step, after the file leaves your control.

    How do I control who can open a file I've shared?

    Don't share it as an open link. Limit it to named recipients, such as specific email addresses, and set an expiry date. Avoid attachments for anything sensitive, because you can't take an attachment back.

    Can I revoke access to a file after sending it?

    Yes, if you sent it as a link rather than an attachment. Revoking stops the link opening for everyone. It can't remove a copy someone already downloaded or captured, so choose your recipients carefully.

    Is a password enough for secure file access?

    Rarely on its own. A password can be shared, forwarded or guessed, and it never expires. Pair it with named recipients and an expiry date so access ends when the reason for sharing does.

    One last thing

    I built LiveDocument because I was tired of sending things into the void and having no say over them afterwards. If that feeling is familiar, it's at livedocument.com.

    About the Author

    Cameron James

    Cameron is the founder of LiveDocument. He writes about sharing documents, PDFs, decks and contracts, and why pairing a video walkthrough with a document beats sending it cold.