Nobody has ever bought software because of its folder structure.
But you can't automate a library nobody can find anything in.
So: shelves.
The file manager looks like the folders on your laptop, on purpose. Nobody should need training to find the bylaws.
Underneath it: uploads, downloads that work out what kind of file they're handing you, move, rename, search that digs through every subfolder, and links that expire on a timer.
And a back room. The machine-generated working files sit in a system area customers never see, so nobody downloads watermark-temp-3-FINAL.pdf and then rings you about it.
Then sharing across communities.
A company with ninety communities used to keep ninety copies of the same template. Ninety slightly different documents, drifting apart on their own schedules, and nobody able to say which one is real.
Now one company-level file sits on the shelf and every community reads from that.
Ninety copies of the truth isn't a backup. It's a rumour.Then color labels. Stick them on files, forms, whatever else. Filter by any of these, all of these, or absolutely not these. Label a whole folder in one go.
They're the same labels behind the packages that update themselves from post 12.
Color for people. Rules for the machine.Then the help layer, because a document business generates questions all day long.
FAQs in plain text, each one public or restricted to specific roles, so guidance written for staff isn't sitting in front of a buyer. Categories. View counts. Helpful or not helpful, with a comment box.
That last bit earns its keep. It's how you find the one answer that has been quietly failing everybody since March.
Longer guides get their own home, with a publish date you can set in the future. Write it Tuesday, it appears Monday.
And a What's New feed, aimed separately at buyers and at staff, so the wrong audience simply never sees it.
Because "I didn't know that existed" is the most expensive support ticket there is.
Next: one application, and everybody's name over the door.