Final FINAL v2 Must Die
Let me paint the scene, because you have lived it. Somebody needs the current version of a quote, a drawing, or a signed agreement. They open the shared drive and find four versions in two folders, one of them on a former employee's desktop folder named Stuff. The newest one is called final FINAL v2, created by Dave, modified by nobody knows who. So they do what everybody does. They call the person most likely to know, that person guesses, and the business runs on a guess.
That is not a filing problem. That is a trust problem. When nobody trusts the drive, they keep private copies, and when everybody keeps private copies, the drive gets even less trustworthy. It is a spiral, and I have watched good teams lose hours a week to it, plus the occasional ugly moment where the wrong version went out to a customer and somebody had to make the apology call.
The way out is not organizing harder inside the same maze. The way out is giving files a home that is connected to the work itself. A vendor bill's attachment lives with the bill. A signed contract lives with the customer and the project. When the document sits next to the record it belongs to, the question of which folder did we put that in mostly just goes away.
One Home, Organized by the Work
Here is the plain practice I set up with small teams. Decide that business documents live in one place, inside the system your people already open every day, and let the structure follow the work instead of somebody's personal filing taste. Customer documents with customers. Supplier documents with suppliers. Employee documents with the employee record. Project files with the project. Nobody has to memorize a folder tree, because they find the file the same way they find everything else, by finding the job it belongs to.
Workspaces still have their place for the loose stuff, the shared references, templates, and team resources that do not belong to one record. Keep those few and keep them shallow. The moment your workspace structure needs a training session to explain, it has failed. A new hire should be able to guess where something goes and be right most of the time. If they cannot, the structure is serving the person who built it, not the team using it.
Naming Habits a Tired Human Can Follow
A good system reduces how much naming matters, but it does not eliminate it, so keep the habit dead simple. My rule for teams is this. The name should say what it is and whose it is, in plain words, and the system can carry the dates and versions so humans do not have to encode them in the filename like it is a secret message.
That means the end of the version-number arms race. No more v2, v3, final, final real, final real use this one. When a document gets updated, it gets updated in place, in its home, so the newest one is simply the one that is there. If you genuinely need to keep a signed or submitted snapshot frozen, that is what a clearly labeled copy is for, marked with what it is, like the signed copy or the as-submitted copy. Frozen on purpose is fine. Frozen by confusion is the disease.
Permissions Without the Paranoia
The other maze nobody talks about is permissions. Shared drives tend to swing between two bad settings. Everything open to everyone, which makes people nervous about putting anything sensitive in there, or a locked-down tangle where half the team cannot open what they need and one departed employee somehow still can. Both settings push people back to private copies and email attachments, and the maze rebuilds itself.
Handle it in plain groups that match how your business actually works. Most documents, most of the team can see. A small set, payroll, personnel matters, sensitive financials, sits in a tighter group with named owners. Every group has a living owner who reviews it once in a while, especially when somebody leaves or changes roles. That review is the whole trick. Permissions do not rot because people are careless. They rot because nobody's job includes looking at them.
Start Ugly, Start This Week
You do not need a document summit. Pick one category that causes weekly pain, usually customer-facing files, and move that one into its new home with the habits above. Tell the team the old spot is read-only for that category from Monday. Expect two weeks of grumbling and one person who keeps saving to the old drive out of muscle memory. Be kind, be firm, and fix the stragglers by moving the file with them watching once.
Within a month something quiet happens. People stop asking where things are in meetings. Search starts working. The apology calls stop. Nobody will throw you a parade for killing the shared drive maze, but you will feel it every single day, in minutes that come back and in the deep calm of opening a file and knowing, for once, that it is the right one.
Frequently Asked Questions
Should I move my entire old shared drive into Odoo Documents?
No, and I say that as somebody who would earn more if you did. Move the living documents, current customers, open projects, and recent records, and leave the deep archive read-only where it sits. Most old files are never opened again. A focused move finishes and sticks. A heroic total migration stalls for months and the team gives up and goes back to the maze.
How do I get my team to actually follow naming habits?
Keep the habit so simple a tired person can follow it on a Friday afternoon. Plain words for what it is and whose it is, no version codes in filenames, and updates made in place so the file that is there is the current one. Then make the right way the easy way, with documents living one click from the work. People follow systems that save them effort, not lectures.
Who should be able to see sensitive documents like payroll files?
A small, named group with a living owner, not the whole company and not one person's private folder. Most business documents can be broadly visible to the team, while personnel and sensitive financial files sit in the tighter group. The owner reviews access whenever somebody joins, leaves, or changes roles. Permissions stay sane when reviewing them is somebody's actual job, rather than everybody's good intention.
What do I do about files that live in email attachments right now?
Treat email as delivery, not storage. When a document matters, a signed agreement, a supplier quote you accepted, a customer approval, save it to its home with the related record as part of closing that task. If it only lives in somebody's inbox, it effectively belongs to that person, and it walks out the door with them. One small habit at the end of the task fixes it permanently.
