How to Change File Permissions on Windows 10

Understanding File Permissions in Windows 10 (Without the Headache)

Most Windows 10 permissions you change in File Explorer are NTFS permissions. NTFS is the file system used by most internal Windows drives, and it supports detailed rules about who can read, write, delete, and modify files and folders.

Common Permission Levels You’ll See

• Full control: Can read, write, delete, and also change permissions and ownership.
• Modify: Can read, write, and delete, but typically can’t change permissions.
• Read & execute: Can open files and run programs, but not change them.
• Read: Can view files/folder contents, but not edit.
• Write: Can add or edit files (depending on context), but may not be able to delete.

NTFS vs Share Permissions (Yes, There Are Two Bouncers)

If you’re accessing a folder over the network (like a shared folder), Windows may apply both Share permissions (Sharing tab) and NTFS permissions (Security tab). The effective result is usually the more restrictive combination. So if sharing permissions say “Read” but NTFS says “Modify,” the practical outcome is “Read.”

Method 1: Change File Permissions Using File Explorer (Security Tab)

This is the most common method, and it’s perfect when you want to give another user account access to a folder, remove access, or tighten up a sensitive directory.

Step-by-Step: Change Permissions for a File or Folder

1. Find the file or folder in File Explorer.
2. Right-click it, then select Properties.
3. Click the Security tab.
4. Under “Group or user names,” select the user/group you want to edit.
5. Click Edit.
6. Check or uncheck permission boxes under Allow (and avoid Deny unless you really mean it).
7. Click Apply, then OK.

Example: Give Another Local User “Modify” Access to a Project Folder

Let’s say you have a folder: C:\Projects\GroupAssignment, and you want user Alex to edit and delete files but not take control of permissions.

1. Security tab → Edit
2. Click Add
3. Type Alex → click Check Names → OK
4. Select Alex → check Modify (Allow)
5. Apply → OK

How to Add a New User or Group

If you don’t see the account you need in the list, use Add and then type a name like:

• A local user (example: Alex)
• A built-in group (example: Users, Administrators)
• Authenticated Users (usually safer than “Everyone” for many scenarios)

Method 2: Use Advanced Security Settings (Ownership, Inheritance, and “Special Permissions”)

When the simple checkboxes aren’t enoughor Windows tells you “You need permission to perform this action”you’ll end up in Advanced Security Settings. This is where Windows hides the “serious” permission tools.

Open Advanced Security Settings

1. Right-click the file/folder → Properties
2. Security tab → click Advanced

Fix “Access is denied” by Taking Ownership (Safely)

If your account isn’t the owner (or you don’t have rights to change permissions), you may need to change the owner to an administrator account you control.

1. In Advanced Security Settings, find Owner at the top.
2. Click Change.
3. Type your username (or “Administrators”) → Check Names → OK.
4. If it’s a folder, consider checking Replace owner on subcontainers and objects.
5. Click Apply, then OK.

Important: Avoid taking ownership of system folders like C:\Windows or C:\Program Files unless you’re troubleshooting a specific issue and you know how to undo changes. Windows protects many critical files for a reason.

Inheritance: Why Permissions “Spread” (and How to Stop It)

By default, permissions are often inherited from a parent folder. That’s helpful when you want consistency. It’s annoying when you want one folder to be private.

To Disable Inheritance

1. Open Advanced Security Settings.
2. Click Disable inheritance.
3. Choose one:
   • Convert inherited permissions (keeps current entries but makes them explicit)
   • Remove all inherited permissions (starts cleaner, but can lock you out if you’re careless)
4. Apply → OK

To Push One Folder’s Permissions Down to Everything Inside

If child files/folders have messy, inconsistent permissions, you can replace child permissions with the parent’s inheritable permissions. This is useful for “resetting” a folder tree to match the top-level folder.

1. Advanced Security Settings → look for an option like Replace all child object permission entries with inheritable permission entries from this object.
2. Check it carefully.
3. Apply changes.

What Are “Special Permissions”?

“Special permissions” usually means a permission entry isn’t a clean match for the standard sets like Read or Modify. Someone customized the fine-grained permissions, and Windows is politely saying, “It’s complicated.”

Method 3: Change Permissions with Command Line (icacls)

If you manage a lot of folders, need repeatable changes, or want to document exactly what you did, command line tools can be faster and more precise.

Before You Start

• Run Command Prompt as Administrator when changing protected folders.
• Test changes on a small folder first.
• Be careful with recursive operations (anything that affects subfolders/files).

View Current Permissions

Grant Permissions (Common Examples)

Grant user Alex Modify permissions:

Grant a group Read & Execute permissions:

Apply permissions to all subfolders and files:

Tip: (OI) and (CI) typically mean “apply to files” and “apply to subfolders.” The /T switch makes it recursive.

Remove a Permission Entry

Reset Permissions to Inherited Defaults

If you’ve changed things and want to revert files to inherited permissions from their parent, you can reset:

The /C switch continues on errors (helpful in big folder trees).

Take Ownership (When You Truly Need It)

If permissions are so broken you can’t even adjust them, ownership may be required first.

After ownership, you can grant yourself control:

Use this responsiblyespecially outside your personal folders.

Method 4: PowerShell Option (Great for Admins, Still Friendly)

PowerShell can read and write permissions using ACL objects. This is useful when you want scripted control without memorizing every icacls switch.

View an ACL

High-Level Approach to Setting Permissions

Many people use PowerShell for reporting and auditing permissions, then apply changes using GUI or icacls. If you’re new to ACL scripting, start by learning to read and interpret ACLs firstthen automate carefully.

Common Problems (and the Fix That Usually Works)

Problem: “Security” Tab Is Missing

If the Security tab isn’t there, one common reason is that the drive isn’t using NTFS (for example, some external drives use exFAT). NTFS permissions won’t apply the same way on non-NTFS file systems.

Problem: “You need permission to perform this action”

This usually means either:

• You’re not an administrator (or not running with admin rights), or
• You don’t own the file/folder, or
• The folder is protected by system ownership (like TrustedInstaller for system files)

Try: Advanced Security Settings → Change Owner → grant yourself Modify/Full control as needed.

Problem: Permissions Keep “Coming Back”

Inheritance is often the culprit. If the parent folder keeps reapplying rules, disable inheritance on the target folder and make permissions explicit.

Problem: Sharing Works Locally but Not Over the Network

Remember the “two bouncers” rule: Share permissions and NTFS permissions can both apply over the network. Check both the Sharing tab and the Security tab for the shared folder.

Best Practices for Changing File Permissions (So Future-You Doesn’t Suffer)

• Use least privilege: Give “Modify” instead of “Full control” when possible.
• Prefer groups over individuals: It scales better and is easier to audit later.
• Avoid “Deny” unless necessary: Deny overrides Allow in many situations and can create confusing results.
• Document changes: Even a quick note like “Granted Alex Modify on 2026-02-03 for project collaboration” can save headaches.
• Test with the target account: Log in as the user (or use a quick test) to confirm access is exactly what you intended.

Quick FAQ

What permissions should I give someone I trust, but not that much?

Usually Modify for shared work folders. It allows editing and deleting files without handing them the keys to the permission kingdom.

Is it safe to change permissions on system folders?

Generally, no. System folders are protected to keep Windows stable and secure. If you’re troubleshooting a specific problem, change as little as possible, and consider reversing changes afterward.

Why does Windows say “Special permissions”?

Because the permissions don’t match a standard set like Read or Modify. Someone customized the fine-grained permission bits.

Real-World Experiences With Windows 10 Permissions ( of “Oh, So That’s Why”)

Most people don’t think about file permissions until Windows hits them with an “Access is denied” message that feels personal. And honestly, the first time you see a folder refuse to cooperate on your own PC, it’s natural to wonder if your computer has joined a union.

One common experience happens in shared-home setups: a family laptop has multiple accounts, and someone saves important files in a folder that “just works” for thembut not for anyone else. The fix is usually simple: instead of tossing everything into random corners of C:\, create a shared folder (like C:\Shared) and give the right people “Modify” access. That way, homework, photos, and shared documents can be edited without accidentally giving everyone the ability to change permissions or delete protected system files. The lesson: a little structure beats a lot of frustration.

Another classic scenario: group projects. You’re collaborating locally (maybe passing files via USB or syncing through a shared folder), and one person can edit everything while another can only open files read-only. The twist? It’s not always the filesometimes it’s the folder. If the folder grants Read & Execute but the file grants Modify, you still might have trouble, especially when apps need to create temp files. In practice, setting the folder permissions cleanly (and letting inheritance do its job) prevents “why can’t I save?” panic five minutes before a deadline.

Then there’s the “TrustedInstaller trap,” where someone tries to modify a Windows system file because a tutorial told them to. They change ownership, grant Full control, and suddenly a future update fails or the system behaves oddly. The experience teaches a valuable rule: Windows protects system files for stability and security. If you must troubleshoot, change only the specific file or folder you need, document what you did, and avoid applying changes recursively to huge system directories.

Finally, external drives create their own permission drama. People plug in a drive, expect Windows permissions to behave like normal, and get confused when the Security tab doesn’t help the way they expect. Often the drive is exFAT, which doesn’t support NTFS permissions in the same way. The real-world takeaway is simple: file permissions are strongest and most predictable on NTFS drives. If you need Windows-style security on a drive you use mostly with Windows, NTFS is usually the better fit.

In other words: file permissions aren’t just a technical feature. They’re the difference between smooth collaboration and a chaotic folder that behaves like it has free will.