Dropbox Business
The Monday morning that starts with a missing folder
A designer leaves on Friday. On Monday the project folder is gone from everyone's machine, because it was shared from her personal account and her personal account has been closed. This is not a hypothetical failure mode; it is the most common way organizations discover they never actually controlled their own files.
How a file goes missing in four steps
Each step is reasonable on its own. The sequence is what produces the loss.
A quick share, from whatever account was signed in
Somebody needs to send large files to a client. The corporate system is awkward, so they use the personal account already open in their browser. It works, and nobody mentions it.
The folder becomes the way the team works
Colleagues are added. The client is added. Within a quarter it holds the live version of work the business depends on, and no record of that exists anywhere in IT.
The owner leaves
Offboarding covers email, the file server and the line-of-business systems. It does not cover an account nobody knew about, because there was nothing to find.
Access ends everywhere at once
The account closes and the shared folder disappears for everyone. The files were never owned by the business, so the business has no way to recover them and no standing to ask.
Ownership is the control, not storage
A business account changes who the files belong to. Content created in the team space is owned by the organization rather than by the individual who happened to create it, which means a departure transfers it instead of ending it.
That distinction is worth more than capacity. It determines whether an employee leaving is an administrative task or an emergency, and whether the organization can answer a client asking who has access to their material.
The second part of the response is making the sanctioned route genuinely easier than the unsanctioned one. Shadow usage is almost always a verdict on the approved system rather than a discipline problem, and a business account that keeps the familiar behaviour is what stops the pattern repeating.
What an administrator can actually do
| Situation | Personal accounts | Business account |
|---|---|---|
| Employee leaves | Content leaves with them | Content transfers to the team |
| Who has access to a folder | Only the creator knows | Visible to administrators |
| External sharing | Unrestricted | Governed by policy |
| File deleted in error | Limited window | Extended recovery and versions |
| Ransomware encrypts a sync folder | Encrypted copies sync up | Roll back to a prior point |
Where this is the right answer
A strong fit
Organizations where personal accounts are already in use for work, teams exchanging large files with clients routinely, and creative or professional firms whose staff will abandon any system that adds friction. Familiarity is a genuine advantage here, because it is what makes the sanctioned route stick.
Consider alternatives
If the organization is fully committed to Microsoft 365 or Google Workspace and staff are content with the included storage, adding a third platform creates another place for files to live and another thing to govern. The honest question is whether people are actually using what is already paid for.
Ask your team which accounts hold work files
The question is usually answered honestly and the answers are usually surprising. Whatever comes back is the real inventory, and it is the starting point for owning your own content.
Review Your File SharingGet in touch with Your Company
Questions about this solution? Reach us directly.