Understanding File Permissions in Linux

Linux permissions look like cryptic runes — strings like rwxr-xr-- that seem designed to confuse. But the model behind them is genuinely simple: it's just who is allowed to do what to a file.

Three actions

Every file and folder controls three actions: read (view contents), write (change it), and execute (run it, or for a folder, enter it). That's the entire vocabulary — read, write, execute.

Three audiences

Those three actions are set separately for three groups: the file's owner (usually you), the group it belongs to, and everyone else. So a file's permissions answer nine small questions — can the owner read/write/execute, can the group, can others.

Reading the letters

That's why you see permissions in three chunks of three: owner, group, others, each showing r, w, x, or a dash for "not allowed." Once you know it's three audiences × three actions, the string stops being noise and starts being a table you can read at a glance.

"Permission denied" almost always means: the action you tried isn't allowed for the audience you fall into. The fix is to grant the right action to the right group — not to reach for full access on everything.

Why this exists

On a system that may have many users and services, permissions keep things safe and separate: your files stay yours, system files resist accidental changes, and a script only runs when explicitly allowed to. It's a quiet, constant security layer.

The practical payoff

You don't need to memorise number codes to start. Hold the model — three actions, three audiences — and most permission errors become obvious: figure out which audience you are and which action you need, then grant exactly that. Understanding beats memorising here.