Short answer. Well-shared files rest on five things. A folder tree by department and by project, never by person. Rights given to groups. Versions and a recycle bin, to go back without calling anyone. Access from outside through a named account, with no device exposed to the internet. An independent backup, because a deleted file synchronises too. Only then comes the place: at the office, on a file server or a NAS, if your files are heavy and your upload rate is low; online, if your files are light and your teams scattered; both, most often. The calculation that decides: the file size in megabytes, multiplied by eight, divided by the upload rate.
This guide is for the manager of a company with ten to two hundred workstations whose documents live on computers, USB keys and messaging apps, for anyone hesitating between a NAS and an online subscription, and for the founder based in France who wants to open the folders of their Algerian company without having them sent. The notions quoted come from public sources: the file server, network-attached storage, synchronisation, and the retention periods published by Microsoft and Google. The numbers in the figures are a constructed example. This guide gives no hardware prices; how long to keep a document and who may read it depend on your obligations and are matters for your legal adviser.
One quotation, seven places, four different contents
The figure follows a single quotation for nine days, then shows it as it would be in a shared space.
What happens. The salesperson creates the quotation on their computer and sends it to the customer. The manager corrects it on their phone and sends it back by WhatsApp. Someone puts it on a key to print it. The accountant redoes the discount and saves it under another name, then drops a copy on the old server. Nine days later there are seven files, five names and four contents, and the version the customer received is in a phone. Nobody worked badly: there was no place where the file was the right one.
What a shared space does. One file, at one address, which everyone opens instead of copying; each save becomes a version, with its author and date. In Microsoft 365, version history is on by default and keeps the last 500 versions of a document; a deleted file can be restored for 93 days on a work account, unless the administrator has changed the setting. Google states thirty days for the Drive trash. On a file server or a NAS, the equivalent has to be set up: the share's recycle bin and snapshots, that is, the state of the folders at a given moment, to which you can return. What it does not do. Versions undo a mistake; they do not replace a backup, which is a copy elsewhere, described in the guide to backups.
«Nobody worked badly: there was no place where the file was the right one.»
The race of a 200 MB file: 2 seconds at the office, 13 minutes online
The figure sends the same file from a workstation to a shared space, on the office network and then to an online space, at five upload rates.
The calculation. The sending time, in seconds, is the file size in megabytes, multiplied by eight, divided by the upload rate in megabits per second. A 200 MB drawing leaves in about two seconds on a one-gigabit office network. To an online space, it takes 32 seconds if the office uploads at 50 Mbit/s, 2 minutes 40 at 10 Mbit/s, and 13 minutes 20 at 2 Mbit/s. These are theoretical times: a line shared between thirty workstations does worse. The rate that counts is the upload rate, often well below the rate printed on the subscription; it is measured at the office, at ten in the morning, as explained in the guide to linking sites.
What follows. Office documents, a few hundred kilobytes, live very well online, even on a small line. Drawings, site photos, videos and models live badly online if the upload rate is low: every save means waiting. They then stay at the office, on a file server or a NAS, and a copy goes online at night. The move itself. Sending 300 GB to an online space takes 13 hours at 50 Mbit/s, 2.8 days at 10 and almost 14 days at 2, without interruption: it is prepared department by department, at night, starting with what is in use.
«The rate that counts is the upload rate, and it is measured at the office, at ten in the morning.»
At the office or online: six criteria
The figure compares the two places on six criteria; many companies end up with both.
At the office. A file server is a computer on the network that provides a shared location; a NAS is a storage server connected to the network, built for that purpose. Workstations reach it through the file and printer sharing protocol that Windows uses. The advantage is speed on large files, and work that carries on when the internet drops. The trade-off: you maintain it, disks, updates, UPS, backup, following the routine in the guide to managed IT. Online. A shared space with a provider, Microsoft 365 or Google Workspace for example: every site and every phone on the same footing, versions and recycle bin included, no machine to maintain. The trade-off: everything depends on the line, and the subscription, often billed in foreign currency, requires an international means of payment or a local reseller, see the guide to paying for online services.
Do not expose the storage. A NAS made reachable from outside by opening a port on the router is a target: in April 2021 and then in January 2022, two ransomware campaigns, Qlocker and DeadBolt, hit NAS devices from a major manufacturer. Access from outside goes through an encrypted tunnel to the office network, or through the online space; the first actions in case of an attack are described in the guide to ransomware. Both together. The most common arrangement: heavy files at the office, everyday documents online, a nightly synchronisation from one to the other, and a backup independent of both.
Well-shared files, in five layers
The accented layer is versions and the recycle bin: it is what undoes the everyday mistake.
Folder tree. One folder per department, then per project, customer or year; never “Karim's folder”. A short naming rule, date, subject, customer, is enough; the words “final” and “ok” are banned, since versions take care of that. Rights. Create one group per department and give rights to the group: edit in your own department, read elsewhere, nothing on management and personnel folders except for those who work there. When someone changes job, change their group; when they leave, close their account, and their files, which were in the department's folders, stay with the company. It is the same principle as in the guide to roles.
Versions and recycle bin. Set up, known to the team, and tried once: everyone should know how to go back to yesterday's version. Access from outside. One account per person, two-step verification, and for customers and suppliers sharing links that expire, rather than attachments. Backup. Synchronisation faithfully copies a deletion or an encryption; a backup is a separate copy, kept elsewhere, whose restore is tried.
Moving your files, in six steps
The third step is accented: the folder tree and the groups are drawn on one page before anything is copied.
Take stock: where the files are, workstations, keys, old servers, mailboxes, and how many gigabytes per department; that figure, with the upload rate, says where they will go. Sort: duplicates, folders nobody has opened for years, personal files; what is dead is not moved. Draw the folder tree and the groups on one page, with an owner per department.
Copy department by department, at night, keeping the file dates. Check: the number of files, a few opened at random, rights tested with an ordinary account. Close the old locations: read-only for a month, then removed; that is the step that stops copies coming back. USB keys and WhatsApp sending fade by themselves once the right file is easier to open than to copy.
Files in order in 2027, in weeks
Four weeks in the example, the first with nothing moved.
- What the manager sees: one place for each folder, who has access to it, the volume per department, and their own folders from their phone.
- What the company no longer does: hunt for the right version, send a file to a colleague by WhatsApp, lose the folders of an employee who leaves, expose a disk to the internet.
- What is measured: volume per department, files still outside the shared space, time to open a large file, restores tried.
- What Symloop does: the stock-take and the measurement, the folder tree and groups with each department, installing the file server, the NAS or the online space, the move, access from outside, backup, then upkeep.
Week 1, stock-take and measurement: where the files are, the volume per department, the size of the heaviest, and the upload rate measured at the office. Week 2, folder tree and rights: folders, groups, the naming rule, and the choice of place, office, online or both, from the first week's figures.
Week 3, move: copy department by department, check, old locations read-only. Week 4, access and backup: access from outside, versions and recycle bin set up and shown to the team, independent backup, restore tried. When files are no longer enough. If the same documents always follow the same route, an invoice to approve, a customer file to complete, the subject is no longer file sharing but an application or document management, as in the guide to document management.
- How do you share files between several computers in a company?
- By giving them one common place: a shared folder on a file server or a NAS at the office, or a shared space online. Everyone opens the file there instead of sending it to each other. Sending files between colleagues by email, USB key or WhatsApp is the sign that no such place exists, or that it is less convenient than copying.
- Do we need a NAS, a server or a cloud?
- It depends on two figures: the weight of your files and your office's upload rate. Heavy files and a weak line argue for a file server or a NAS at the office. Light files, several sites and remote work argue for an online space. Many companies use both, with a nightly copy from one to the other.
- What is a NAS?
- It is a storage server connected to the network, designed for sharing files between several computers. It holds several disks, is configured from a browser, and manages accounts, shared folders and snapshots. It is a ready-made file server; it still needs updates, a UPS and a backup.
- How do I reach the office files from home or from abroad?
- Through an encrypted tunnel to the office network, which gives the same folders as at the office, or through an online space, reachable anywhere with the account and two-step verification. What must not be done is to open a router port to the NAS: that is how ransomware gets in.
- How do we stop everyone seeing everything?
- By giving rights to groups, not to people: one group per department, edit rights in its own folders, read-only or nothing elsewhere. Management and personnel folders have their own group. Rights are checked by signing in with an ordinary account, not the administrator's.
- Can a deleted or overwritten file be recovered?
- Yes, if versions and the recycle bin are in place. In Microsoft 365, history keeps the last 500 versions of a document by default, and a deleted file can be restored for 93 days on a work account; Google states thirty days for the Drive trash. On a NAS, it is the share's recycle bin and snapshots, which have to be turned on. Beyond those periods, only a backup can do it.
- Does synchronisation replace backup?
- No. Synchronisation makes several locations identical: if a file is deleted, overwritten or encrypted by ransomware, the change spreads. A backup is an independent copy, at a given date, kept elsewhere, whose restore has been tried.
- How much space should we plan for?
- Start from the stock-take: the current volume per department, once duplicates and dead folders are removed, then a margin for growth and for versions. Departments that handle drawings, photos or videos weigh more than all the others together; they are the ones to measure first.
- What happens to the files of an employee who leaves?
- If they were in their department's folders, they stay there: the account is closed and nothing is lost. If they were on their computer, on a key or in a personal space, they have to be hunted down. That is why the folder tree is built by department and not by person.
- Are free personal online storage accounts enough?
- For personal use, yes; for a company, no. The files there belong to the person and not to the company, there are no groups and no overall view, and someone leaving takes the folders with them. A company space has an administrator, groups, and files that stay when people change.