The one idea
"The cloud" is someone else's computer, with your files on it, reachable from anywhere.
That gives you two things — access from any device, and a copy that survives your laptop dying. It also creates one new risk that did not exist before: a file can be shared with people you never chose.
Your files sit on a company's computers instead of only on yours, so you can reach them anywhere — and so can anyone you give a link to.
Share with named people by default. Use link sharing only when you have decided that anyone holding that link may see the contents.
Sync replicates state, including deletions. Backup retains history. They solve different problems and one does not substitute for the other.
Sync is not backup
This is the most expensive misunderstanding in the lesson.
Sync keeps two places identical. Delete a file on your laptop and sync faithfully deletes it everywhere. Corrupt a file and the corrupted version is now everywhere too. Sync is very good at making sure everything matches, including your mistakes.
Backup keeps a history you can go back to.
Fact Most major cloud services keep deleted files in a trash for a limited period —
commonly around 30 days — and offer version history for documents. That is
real protection, but it is time-limited, and it is not the same as a backup
you control.
Recommendation For anything you genuinely cannot lose, keep a copy in a second place that does
not sync with the first. An external drive, or a different service. If deleting
it in one place deletes it everywhere, you have one copy, not two.
The sharing settings, in plain language
Every service words these differently. They come down to the same three choices.
| Setting | Who can open it | Use it when |
|---|---|---|
| Specific people | Only the accounts you list | Almost always. This is the correct default. |
| Anyone with the link | Anyone who has, is sent, or finds the link | Genuinely public content only |
| Anyone in your organisation | Every employee | Internal documents that are not sensitive |
And separately, what they can do:
- Viewer — read only
- Commenter — read and comment, cannot change content
- Editor — can change and delete it
A colleague asks for a document. You click share, hit a permissions error, see "anyone with the link" and choose it because it works immediately.
That link now lives in your chat history, their chat history, possibly a forwarded email, and any group either of you pasted it into. Nothing revoked it. Two years later it still opens.
Sharing a file properly
1 of 5Decide who should see it before you click anything.
One person, a team, or genuinely anyone. This decision takes two seconds and determines everything else.
Try this
Open your own cloud storage and find the list of files you have shared.
Ask three questions: How many are shared with "anyone with the link"? Do any contain personal information, salary details, or client material? Are any shared with people who have since left?
Your challenge
Level 3 · IndependentSet up a genuine two-place backup for the work you cannot afford to lose.
- Identify what actually matters. It is usually a smaller set than you think.
- Ensure it exists in two places where deleting from one does not delete from the other.
- Test the restore. Delete a test file from one place and recover it.
You have succeeded when you have actually recovered a file, not when you have set something up that you assume works. Untested backups fail at exactly the moment they are needed.
What people usually get wrong
- Assuming sync is backup. It is not. It replicates deletions.
- Using "anyone with the link" as the default. It is the option that always works, which is why it is the option that leaks.
- Giving edit access when view would do.
- Never reviewing old shares. Access does not expire on its own.
- Keeping the only copy in one cloud account. Lose the account and lose everything.
- Not knowing where files actually live. If you cannot say whether a file is on your laptop or in the cloud, you do not know what happens when either one fails.
How someone experienced does it
Experienced people share with named individuals by default, and treat link sharing as a deliberate decision with a reason.
They also assume anything shared by link is effectively permanent and public, and they never put anything in one that they would mind being read by a stranger. That assumption costs nothing when it is wrong and saves you completely when it is right.
For backup, they follow a simple rule: at least two copies, on different systems, one of which is not automatically synced to the other. And they have restored a file at least once, so they know it works.
Version history, the feature that saves you
Most cloud document services keep previous versions automatically. Google Docs has version history; Microsoft 365 has version history; Dropbox keeps file versions for a period.
This means "I overwrote it and saved" is usually recoverable. Most people never learn this and rewrite the work instead.
Find it once, now, before you need it. In Google Docs it is under File then Version history. In Microsoft 365 it is in the file menu or by right-clicking the file in OneDrive.
Ten minutes of exploring today saves an afternoon of rewriting later.
Prove it
Do the annual share review described above, and fix anything that is wrong. Write down how many files were shared more widely than you intended.
Then set a reminder to do it again in a year. That reminder is the actual deliverable.
Keep learning this
Paste this into any AI assistant. It turns the assistant into a tutor that tests you instead of just answering you.
Act as an experienced practitioner who is good at teaching. I have just learned cloud storage, file sharing permissions and backup. Assume I am intelligent but relatively new to this — treat me as beginner level. Work through this in order, and wait for my reply at each step: 1. Ask me 5 questions that test whether I actually understood cloud storage, file sharing permissions and backup. Do not reveal the answers yet. 2. After I answer, tell me which parts I got right, which I got wrong, and which I only half-understand. Explain only what I misunderstood — do not re-teach what I already know. 3. Give me one practical challenge based on something I could genuinely encounter at work or in daily life. Do not solve it for me. 4. Evaluate my solution the way an experienced person would judge it, including what a professional would have done differently. 5. Tell me what to learn next, and why that comes next. 6. Give me trustworthy sources for deeper study — prefer official documentation, primary research or standards bodies over blogs and videos. Rules for you: no buzzwords. No motivational filler. Say "I'm not certain" when you are not certain, and tell me which parts of your answer I should verify myself. Clearly separate facts from your recommendations and your opinions.
Become independent at this
Use this when you want a path from where you are to actually good, with checkpoints you can test yourself against.
I want to become independently capable at managing cloud storage and sharing safely — not permanently dependent on AI, tutorials or step-by-step guides. Design a progression for me with five stages: Beginner, Guided practice, Independent practice, Real-world application, Professional level. For each stage tell me: - what I must know - what I must be able to do without help - the mistakes people make at this stage - one practical challenge - one real project that would prove I reached this stage - one way I can test myself honestly Then tell me the signals that I am ready to move to the next stage, and the signals that I have skipped ahead too early. Keep the theory to the minimum I actually need. Focus on ability I can transfer to situations you and I have not discussed.