Windows File Permissions: A Practical Guide to Viewing and Modifying Access

Why Windows Permissions Feel Different

If you've ever tried to delete a file as an administrator and got slapped with an access denied message, you know the frustration. Windows permissions don't work like Linux, and even admins can hit walls. This guide walks through the GUI tools in Windows for viewing and modifying file permissions, with practical tips for common issues.

Where to Find Permissions in the GUI

Right-click any file or folder, select Properties, then go to the Security tab. This is the main hub for viewing and editing permissions. You'll see a list of users and groups with their allowed permissions. For most folders, you'll see SYSTEM and Administrators with Full control. That's by design—SYSTEM is the operating system's account, and Administrators is the default admin group.

Editing Permissions: The Grayed-Out Checkboxes

Click the Edit button to see if you can modify permissions. If checkboxes are grayed out, it usually means the permissions are inherited from a parent folder. You can't uncheck the Allow boxes, but you can set Deny boxes. Deny overrides Allow, so you can create a situation where a user can't read or write but can still delete the file. That's impossible with only Allow checkboxes.

Advanced Settings for Finer Control

For more granular control, click Advanced in the Security tab. This opens a window where you can view permissions in detail, change the owner, and manage inheritance.

Checking What a Specific User Can Access

Ever wonder exactly what a user can do with a folder? In the Advanced window, go to the Effective Access tab. Type the user's name, click Check name, and Windows will verify the account and show you the effective permissions. This is great for troubleshooting why someone can't access a file.

File Ownership: The Secret Boss

The file owner is the one who can always change permissions, even if they've been stripped away. Usually, the creator is the owner. If you delete all permissions, only the owner can modify them—even an administrator can't, unless they take ownership first. Admins can change the owner through the Advanced window, which is the workaround when a file is locked down.

Permission Inheritance: Why Some Boxes Are Gray

Inheritance is a common source of confusion. If a file's permissions are inherited from its parent folder, you can't change them directly. You have to either disable inheritance (which allows you to set custom permissions) or go to the parent folder and change the inherited settings there. When you disable inheritance, you can choose to copy the existing permissions or remove them entirely.

Note that even when inheritance is enabled, you can still set Deny permissions, and Deny always wins over Allow.

What Each Permission Actually Means

Windows splits permissions into Read, Write, and Execute—similar to Linux, but with a twist. The Execute permission is actually Read & execute, so you can't grant execute without read. If you give only Read, the user can view file contents but not write. Only Write means they can write but can't read what's there.

Folders also have List folder contents, which is separate from Read. On Linux, read permission on a directory lets you list its contents. Windows separates these, likely because of how inheritance works.

The Modify permission includes read, write, execute, and also lets you delete the file. It doesn't necessarily include changing permissions—that's reserved for Full control, which includes everything: reading, writing, executing, moving, renaming, deleting, and changing permissions.

Troubleshooting Common Permission Problems

Why Can't I Delete This File as Admin?

Because being an administrator doesn't automatically give you Full control. If you're denied, you need to explicitly grant yourself permission. This often happens with files owned by other users or system processes.

Why Does 'ls -l' Show Wrong Permissions in MSYS?

MSYS (and Git Bash) doesn't fully translate Windows permissions to the Unix model. So ls -l may show permissions that don't match reality, and chmod won't actually change anything—even though it doesn't error out. It's a known limitation.

Final Thoughts

Windows permissions can be a maze, but once you understand the GUI, ownership, and inheritance, you can manage access with confidence. Next time you're locked out, remember: check the owner, disable inheritance if needed, and don't forget that Deny beats Allow.