SoDeep IconSoDeep
·
The way 'user permissions' control access to digital files

The way 'user permissions' control access to digital files

@Nan_Binary · July 5, 2026

Your computer is like a fussy seaside boarding house. Every file is a private room, and 'user permissions' are the brass keys the landlady keeps on her belt. You’re allowed to look at the view, move the furniture, or—heaven forbid—demolish the shed.

It relies on a hidden guest list. When you click a file, the system checks your ID faster than a seagull swipes a chip. Without 'Write' access, you can stare at that photo, but you can't delete it. It’s digital gatekeeping to keep the riff-raff out of the system's cupboards.

Wait, who actually gets to write that guest list in the first place?

That would be the 'Administrator'—or as I like to call her, the Head Housekeeper. She’s the one who decides who sleeps in the attic and who’s strictly banned from the pantry.

When you first set up the computer, you’re usually handed that master apron. You have the power to hand out spare keys to 'Standard Users,' who are basically the guests not allowed to touch the fancy china or move the walls.

It’s a heavy responsibility, though. If the Head Housekeeper leaves the back door unlocked, any old drifter can rewrite the rules and lock the owners out of their own home.

Why would I ever want to be a lowly 'Standard User' myself?

Think of it like wearing your finest silk Sunday dress to scrub the grease off the oven. It’s just asking for a permanent stain!

If you browse the web as the Head Housekeeper, one wrong click lets a sneaky virus use your master key to unlock every door and burn the boarding house down before you’ve even finished your tea.

Using a 'Standard User' account for daily chores is like wearing protective overalls. If you trip over a malicious link, the damage is contained to your apron rather than the entire foundation of the house.

So how does the system actually keep the virus stuck on the apron?

It’s all about the 'Prompt'—that necessary bit of faff that stops everything in its tracks. When a program tries to touch the foundation, the computer pauses and asks for the Head Housekeeper’s secret password. It’s like a heavy iron bolt on the cellar door that won't budge for a guest.

Since you’re in your 'Standard' overalls, you don't have that password. The virus can scream and kick all it wants, but without that code, it’s stuck in the mud room. It might ruin your boots, but it can’t touch the structural beams of the house.

But what if I'm the one who accidentally hands over the password?

Ah, that’s the fly in the ointment! If you type that password into a fake prompt, you’ve essentially walked to the cellar door and slid the iron bolt back yourself. The computer is a loyal guard, but it isn’t a mind reader.

It assumes that if you’re providing the Head Housekeeper’s credentials, you must have a very good reason to let that stranger in. It’s far easier for a digital rogue to trick a human with a fake telegram than it is to break the physical lock.

This is why the most dangerous part of the house isn't the foundation—it’s the person holding the keys. Even the sturdiest boarding house can’t protect itself if the owner invites the burglars in for tea.

Explore in card mode →

Related topics

The way 'edge cases' disrupt a computer's logical instructionsThe way 'state machines' track the progress of a digital taskThe logic of 'unit testing' in a complex knitting patternThe way 'daisy chaining' connects multiple digital devices in a seriesThe way 'idempotency' ensures a digital command only happens oncethe way 'memory leaks' slowly clutter a computer's system