Confluence was built on a dream. Text flows freely, every idea connects to every other, anything can be referenced, and when you finally need a formal document, you export one. It is a genuinely good vision of collaboration. It also leaves a gap, because no organization runs on text alone. You run on contracts, spreadsheets, HR records, and budgets, and those documents are not going anywhere.
That is where the trouble starts. Confluence handles attachments in a way that quietly puts your most important files at risk, and most teams never notice until something final gets overwritten with something old. Attachment Locker for Confluence exists to close that gap, and the Life in Codes team demonstrated it live at the Work Evolution Summit.

The Dream Is Text. The Reality Is Documents.
Confluence aims squarely at text-based collaboration, and that focus comes with limitations around attachments that most teams never think about until they get burned. Ask yourself a simple question. Does anyone on your team work without documents? Almost nobody can say yes. Contracts, finance spreadsheets, board decks, and HR records all live as files, and files behave differently from the free-flowing text Confluence was designed around.
How Confluence Quietly Overwrites Your Files
Here is the behavior that catches everyone. Drag a file into a space, then drag in another file with the exact same name, and Confluence does not stop to ask. No pop-up warning you that a file already exists. No are you sure. It simply replaces the first one. Tell several people to download a file, edit it, and put it back, and the same rule applies. Whoever uploads last wins. There is a version history underneath, so nothing is truly gone, but you do not see it natively. You have to know to go looking for it. If you do not, you see the latest file, assume it is the only one, and carry on.
Play that out with a real document and the risk becomes obvious. You have a finalized, signed contract attached to a page, and everyone treats it as the source of truth. Someone edits the page and re-uploads the file, except their copy is an older draft. Nothing warns anyone, and the version war begins.
It rarely stays a single skirmish. The same overwrite threatens finance spreadsheets, board decks, investor reports, product specs, agreements, and guidelines. Anything that goes through rounds of revision is a candidate, which is to say almost everything that matters. Picture the HR professional guarding a sensitive salary spreadsheet, or the project lead protecting a critical budget, each one a single careless re-upload away from chaos.
When "Who Changed This, When" Matters

For many teams the hidden version history is an annoyance. For anyone with audit exposure, it is a serious liability. If who changed a file and when actually matters, or if you ever need to prove that a specific document was not tampered with between two dates, hoping people upload carefully is not a control you can show an auditor.
What you need instead is a set of real controls. The ability to lock an attachment so that while you work on it, nobody can quietly change it underneath you. Control over who is allowed to lock and unlock, because if everyone can, it turns messy fast. Timers, reminders, and notifications when someone tries to unlock, so files never get locked once and forgotten forever. And an experience simple and visual enough that people actually understand it, because a security control nobody understands is a security control nobody uses.
What Attachment Locker Does
Attachment Locker for Confluence delivers exactly those controls, and it was built from real customer feedback and real cases rather than a wishlist of features. It lets you lock the files that matter so no one can overwrite them, whether by accident or otherwise. It puts locking and unlocking in the hands of the people who should hold that power, and keeps everyone else out. It adds the timers, reminders, and unlock notifications that stop documents from being locked and forgotten. And it keeps the whole thing visible and simple, so protection is obvious at a glance rather than buried in settings.
The result is what the version wars were costing you all along. Your most important documents stay protected, compliant, and free of version conflicts, and your team keeps moving at full speed. When the Life in Codes team demoed the app at the Work Evolution Summit, that was the whole point. Security that does not slow your evolution down.
Three Rules for Locking Without the Frustration
Locking is easy to get wrong, so a few rules from experience keep it working for your team rather than against it.
Do not overlock. Scatter locks across every page and attachment and people start seeing them everywhere, which turns protection into daily frustration and teaches everyone to resent the feature. Lock what genuinely needs it.
Communicate the why. When you lock the contracts, say plainly that you are doing it because they are final and important, so a lock reads as a reason rather than an obstacle.
Use locking to close things out. At the end of a project, a quarter, or any milestone, declare which files are the final versions, lock those, and leave the rest alone. That gives you a clean, defensible record exactly where audits look for one.

Key Features at a Glance
– One-click locking directly from the Confluence page byline.
– Auto-protection that reverts unauthorized uploads to locked files instantly.
– Smart lock expiration (default 24 hours) to keep things moving even when someone forgets to unlock.
– Enterprise-grade admin controls including force-unlock, custom timeouts, and permission management.
– Visual color-coded badges (Red, Blue, Green) for instant file status recognition.
– Full audit trail with lock history and ownership tracking for compliance teams.

Protect Your Documents Today
The version war is not caused by careless people. It is caused by a tool that silently lets the last upload win and hides the history where nobody looks. You can end it, but only if you decide to treat your critical documents as something to protect rather than something to hope about.
Look at the contracts, budgets, and reports living in your Confluence spaces right now. If someone overwrote the final version with an old draft this afternoon, would anyone even notice?
Attachment Locker makes sure they would.

Available now on the Atlassian Marketplace, paid via Atlassian commercial license. Give it a try and let us know how it helped your compliance team!











