Folder permissions,
without the guesswork.
The Security tab is six checkboxes, an Advanced button almost nobody opens, and a set of rules that are not intuitive — including one where adding a permission can remove access. Here is what each entry grants, how inheritance and ownership interact, and what «You do not have permission» is actually reporting.
Before you click Apply.
Permissions are a layered calculation, and the tab shows you one layer of it.
A folder on a Windows machine has NTFS permissions, and if it is shared it also has share permissions, and the access you actually get is the most restrictive answer of the two. Then group membership adds allowances you cannot see from the folder, and inheritance adds entries copied from every parent above it. The list you are looking at is the result, not the input.
That is why the two most common disasters happen in exactly this tab: someone removes Administrators: Full control from a folder on the system drive, and someone else adds Everyone: Modify to a folder they meant to make readable.
- Never remove the Administrators or SYSTEM entries from a system path. You can lock yourself out of a folder you own, and the repair needs an elevated console, not this tab.
- Deny beats Allow, always. Not «wins on ties» — it is evaluated first, at every level. One stray Deny line explains most «nobody can open this» cases.
- Check the Effective access tab before you change anything. It answers the real question — what can this user actually do — instead of the one the list implies.
- Ownership is not permission. Being the owner grants you the right to change the permissions; it does not by itself let you read a single file.
The permissions.
The first six are the basic tab. The rest are the rules that decide what those checkboxes really mean once inheritance, ownership and sharing are involved.
Full control
- What it is
- Everything else on this list, plus two powers that are not on the basic tab: the right to change the permissions of the folder, and the right to take ownership of it. It is the only entry that lets the holder lock other people out.
- What changes
- Granting it to a user or group hands them the ability to rewrite the access list of that folder and everything under it that inherits. On a shared drive that is the difference between «they can put files here» and «they can decide who else can».
- Risk
- Careful Reversible if you still have another account with Full control or the Take Ownership privilege. The mistake is granting it to Everyone or Users on a folder that holds things you did not intend to hand over.
Modify
- What it is
- Read, write, execute and delete. The normal permission for a working folder: you can change the contents and remove them, but you cannot change who else can.
- What changes
- Deletion is the difference that matters against Write. With Modify, a person can remove files you did not ask them to remove, including files they did not create — the delete right applies to the folder's children, not only to their own.
- Risk
- Careful Undoable in the tab. The irreversible part is the deleted file, which is why Modify on a shared team folder is the permission people most often regret granting.
Read & execute
- What it is
- For a folder, it is List folder contents plus Read. For a file, it is the right to run it. The two are combined into one checkbox, which is why the entry looks redundant when you only want people to see the names.
- What changes
- Nothing about writing. A user with Read & execute can open, copy out, and run programs from the folder, and can walk through it to reach something deeper if the traverse right is present.
- Risk
- Reversible The safe default for a folder people need to use but should not change. The one surprise is that it allows executing programs from the location, which matters on a download folder.
List folder contents — the one that is not just Read
- What it is
- Applies to folders only: the right to see the names of the children. Without it, a user can open a file if they already know its exact path, but cannot browse to find out what is there.
- What changes
- Removing it while leaving Read is a legitimate way to make a tree unlistable but still reachable by direct path — the trick behind «users can reach their own share but cannot see the list of shares». It is also the setting that makes Explorer appear to show an empty folder with no error at all.
- Risk
- Reversible Confusing to debug, harmless to change. If a folder suddenly shows nothing, check this before checking anything else.
Write
- What it is
- Create files and folders, add data to existing files, change attributes and set times. Notably it does not include reading what is already there, and it does not include deleting.
- What changes
- A drop-box: people can put things in, and can overwrite a file whose name they guess, but cannot list the folder or remove anything. This is the correct shape for a submission folder and a bad shape for anything with content you care about, because Write alone allows overwriting by name.
- Risk
- Careful The under-appreciated one. Write without Read still lets someone destroy a file by saving over it, and they will not be able to explain what they hit because they cannot see the folder.
Special permissions — the Advanced view
- What it is
- The underlying rights the six basic boxes are built from: create files, create subfolders, delete subfolders and files, write permissions, take ownership, traverse folder. Tick «Show advanced permissions» at the bottom of the tab and the six expand into fourteen.
- What changes
- Whatever you select, precisely. The useful one is «Apply onto» / the scope selector: «This folder only», «This folder, subfolders and files», «Subfolders and files only». Most half-broken share trees are one inheritance scope set on the wrong object type.
- Risk
- Careful Reversible, but the combinations are many and the tab gives no preview of the result. Use the Effective access tab as the check, not your reading of the list.
Deny — the rule that breaks the intuition
- What it is
- An explicit refusal. Windows evaluates Deny entries before Allow entries, at every level, so a Deny anywhere in the chain wins over any Allow anywhere else — including Full control granted two lines above it.
- What changes
- Access, and the whole shape of the problem. The most common «I added myself and now nobody can open it» story is a Deny on Everyone that also catches the administrators, because Everyone includes you.
- Risk
- Expensive Not because it is hard to remove — it is one click — but because people who cannot see the Advanced tab cannot find it either, and the folder then looks broken to everyone else. Prefer removing Allow entries over adding Deny entries.
Share permissions versus Security
- What it is
- Two independent gates on the same folder. The Sharing tab's permissions apply only to people arriving over the network; the Security tab's NTFS permissions apply to everyone, local or remote. Your effective access across the share is the more restrictive of the two.
- What changes
- The share list has only three entries — Full control, Change, Read — and its default is usually Everyone: Read with Administrators: Full control. This is why «it works locally and fails from the other machine» is nearly always the Sharing tab, and why the standard advice to leave share permissions at Full control and do all the real work in NTFS is sound.
- Risk
- Careful Reversible. The trap is diagnostic: tightening one gate while the other stays open gives a result that looks random unless you know the two-layer rule.
Inherited from — the column that explains everything
- What it is
- Every entry in the list carries a note about where it came from: this folder, or one of its parents. Inherited entries arrive automatically when a folder is created inside another, which is why a new subfolder is accessible to people you never granted.
- What changes
- Disabling inheritance — «Remove inherited permissions» or «Convert inherited permissions into explicit ones» in the Advanced dialog — cuts the folder off from its parents. Convert keeps the current list as a snapshot; Remove empties it, and on a system folder an empty list means only the owner and SYSTEM can get in.
- Risk
- Expensive The single most damaging click in this tab. On a user profile or a program directory, «Remove inherited permissions» can make the folder unreachable to the software that owns it, and the repair is a take-ownership session from an elevated prompt.
Owner — and why owning it does not let you read it
- What it is
- A separate property on the Advanced dialog: who has the standing right to change this object's permissions. It grants no access to the data at all. Administrators hold the Take Ownership privilege, which is how you can claim a folder you currently cannot open.
- What changes
- Changing the owner, optionally with «Replace owner on subcontainers and objects», rewrites the owner of the whole tree. That is the standard repair after a machine move, a reinstalled Windows, or a drive from another PC — the case where the folder says «you have been denied permission» and the owner is a security identifier that no longer exists.
- Risk
- Careful Reversible if you remember who the previous owner was; not easily if you did not look. Take ownership first, then add yourself an explicit Allow — the two steps are separate and people expect the first to do the second.
Effective access — the tab you should open first
- What it is
- Inside Advanced Security: pick a user or group and Windows computes the answer instead of you reading the list. It walks the allow and deny entries, including the inherited ones, and prints the resulting rights.
- What changes
- Nothing. It is a read-only calculation, which is exactly why it belongs at the start of any permission investigation. Its limitation is worth knowing: it evaluates the NTFS layer only, so a share restriction or an encryption attribute can still deny the user afterwards.
- Risk
- Reversible No risk at all. If you have touched this tab without using this button, you have been guessing.
Encrypt contents to secure data — the Advanced attributes page
- What it is
- Encrypting File System: the file is encrypted with a key bound to your user certificate on this machine. It is not a password, and it is not cloud backup — it is a certificate that lives in your Windows profile.
- What changes
- The files become unreadable to anyone else on the machine, and unreadable to you after a reinstall, a lost profile, or a dead disk moved to another PC, unless you exported the certificate. This is the permission-adjacent setting with the highest permanent cost on the whole tab.
- Risk
- Expensive If the certificate is gone, the data is gone: there is no recovery path and no vendor support that can open it. If you ever tick this box, export the certificate the same day, and treat the folder as one you must not format.
Adjacent screens.
The other references in the library cover the places where the same problem appears in a different window.
File Explorer options, explained
Before you conclude a folder is locked, check that what you cannot see is not simply a hidden or protected item.
Read the reference every appWhat this dialog box is asking
The elevation prompt that appears the moment you press OK on a permission change, and the «Continue» that means you have the right to make it.
Read the reference sharingNetwork problems, decoded
A share that is unreachable over the network is a different failure from a share that is reachable and refuses you, and the two are fixed on different tabs.
Read the reference the libraryAll guides
One hundred and fifty-six entries across thirteen families of screen, each with the same three fields.
Back to the indexYour Security tab is not this page.
Those twelve entries are the shape a stock NTFS folder shows. Yours may carry entries for accounts from a domain you no longer belong to, a template applied by a management agent, or a denial inherited from a parent you have never opened. That is the case a reference cannot cover — and the case the application reads.
Get ToolTip AI on Microsoft Store