A Windows share allows folder creation but not file creation or saving: which permission is missing?
This symptom usually comes from mismatched advanced NTFS rights and inheritance scope. Compare file creation, write data, folder creation, deletion, and ownership permissions.

Establish a factual baseline with “create-folder and append-data permissions” and “create-file and write-data permissions”, then move to “this-folder/subfolder inheritance scope”. Use effective access, credentials and real file operations as the evidence chain and avoid changing production before the fault boundary is clear.
Risk boundaries and prerequisites
Start by checking create-folder and append-data permissions, create-file and write-data permissions and this-folder/subfolder inheritance scope independently. A healthy result for one of these checks does not establish the state of the entire service path.
Evidence and safe checks
| Check | Why it matters | Recommended action |
|---|---|---|
| 01 · create-folder and append-data permissions | Checking create-folder and append-data permissions helps establish whether the effective identity, share and file permissions match the intended access; compare it with a known-good baseline and the incident timeline. | Record the actual state of create-folder and append-data permissions. Preserve ACL, group and share configuration and use representative users to test read, write, change and delete operations. |
| 02 · create-file and write-data permissions | Checking create-file and write-data permissions helps establish whether the effective identity, share and file permissions match the intended access; compare it with a known-good baseline and the incident timeline. | Record the actual state of create-file and write-data permissions. Preserve ACL, group and share configuration and use representative users to test read, write, change and delete operations. |
| 03 · this-folder/subfolder inheritance scope | Checking this-folder/subfolder inheritance scope helps establish whether the effective identity, share and file permissions match the intended access; compare it with a known-good baseline and the incident timeline. | Record the actual state of this-folder/subfolder inheritance scope. Preserve ACL, group and share configuration and use representative users to test read, write, change and delete operations. |
| 04 · Creator Owner | Checking Creator Owner helps establish whether the effective identity, share and file permissions match the intended access; compare it with a known-good baseline and the incident timeline. | Record the actual state of Creator Owner. Preserve ACL, group and share configuration and use representative users to test read, write, change and delete operations. |
| 05 · deny permissions and ownership | Checking deny permissions and ownership helps establish whether the effective identity, share and file permissions match the intended access; compare it with a known-good baseline and the incident timeline. | Record the actual state of deny permissions and ownership. Preserve ACL, group and share configuration and use representative users to test read, write, change and delete operations. |
| 06 · combined share and NTFS permissions | Checking combined share and NTFS permissions helps establish whether the effective identity, share and file permissions match the intended access; compare it with a known-good baseline and the incident timeline. | Record the actual state of combined share and NTFS permissions. Preserve ACL, group and share configuration and use representative users to test read, write, change and delete operations. |
Investigation and change sequence
- Capture a baseline for create-folder and append-data permissions and create-file and write-data permissions and compare it with a known-good system.
- Correlate evidence from this-folder/subfolder inheritance scope and Creator Owner to distinguish the direct fault from dependent symptoms.
- Only if evidence points to deny permissions and ownership, plan a controlled change with backups, a change window and rollback triggers.
- Finally check combined share and NTFS permissions and the real business workflow. Confirm the final effective access and application behavior for real file, print or share workflows.
Validation and rollback evidence
- Confirm the final effective access and application behavior for real file, print or share workflows.
- Recheck deny permissions and ownership and combined share and NTFS permissions against the expected business outcome.
- Retain initial configuration, event evidence, validation results and rollback triggers for production changes.
Common actions that increase risk
- Assuming create-folder and append-data permissions is sufficient while overlooking create-file and write-data permissions and dependent checks.
- Changing several settings before preserving the original evidence for this-folder/subfolder inheritance scope.
- An administrator being able to access a file does not prove normal users have the intended rights.
Common questions and acceptance criteria
What should be checked first?
Begin with create-folder and append-data permissions and create-file and write-data permissions. Capture reproducible errors and protect recoverable data before changing production.
What proves the issue is resolved?
Confirm the final effective access and application behavior for real file, print or share workflows.
What evidence should be retained?
Retain original logs, configuration snapshots, the approved change scope, business verification and rollback conditions.
