Insights /Windows Server and file permissions

How can staff edit files in a shared folder without being allowed to delete other users’ files?

The Modify right includes deletion. Limiting deletion while allowing edits requires a design using Creator Owner, ownership, delete-child rights, working folders, versioning, and auditing—not a single checkbox.

How can staff edit files in a shared folder without being allowed to delete other users’ files?
Key assessment

Establish a factual baseline with “delete rights included in Modify permission” and “Delete and Delete subfolders and files permissions”, then move to “Creator Owner”. 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 delete rights included in Modify permission, Delete and Delete subfolders and files permissions and Creator Owner independently. A healthy result for one of these checks does not establish the state of the entire service path.

Evidence and safe checks

CheckWhy it mattersRecommended action
01 · delete rights included in Modify permissionChecking delete rights included in Modify permission 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 delete rights included in Modify permission. Preserve ACL, group and share configuration and use representative users to test read, write, change and delete operations.
02 · Delete and Delete subfolders and files permissionsChecking Delete and Delete subfolders and files 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 Delete and Delete subfolders and files permissions. Preserve ACL, group and share configuration and use representative users to test read, write, change and delete operations.
03 · Creator OwnerChecking 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.
04 · file-ownership boundariesChecking file-ownership boundaries 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 file-ownership boundaries. Preserve ACL, group and share configuration and use representative users to test read, write, change and delete operations.
05 · Office temporary-file behaviorChecking Office temporary-file behavior 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 Office temporary-file behavior. Preserve ACL, group and share configuration and use representative users to test read, write, change and delete operations.
06 · versioning and audit alternativesChecking versioning and audit alternatives 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 versioning and audit alternatives. Preserve ACL, group and share configuration and use representative users to test read, write, change and delete operations.

Investigation and change sequence

  1. Capture a baseline for delete rights included in Modify permission and Delete and Delete subfolders and files permissions and compare it with a known-good system.
  2. Correlate evidence from Creator Owner and file-ownership boundaries to distinguish the direct fault from dependent symptoms.
  3. Only if evidence points to Office temporary-file behavior, plan a controlled change with backups, a change window and rollback triggers.
  4. Finally check versioning and audit alternatives 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 Office temporary-file behavior and versioning and audit alternatives against the expected business outcome.
  • Retain initial configuration, event evidence, validation results and rollback triggers for production changes.

Common actions that increase risk

  • Assuming delete rights included in Modify permission is sufficient while overlooking Delete and Delete subfolders and files permissions and dependent checks.
  • Changing several settings before preserving the original evidence for Creator Owner.
  • 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 delete rights included in Modify permission and Delete and Delete subfolders and files 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.

PreviousRemote access connects successfully but internal servers are unreachable: should you check routing, DNS, or the firewall first?Nextsecure remote access is connected but a file share will not open: DNS, SMB, credentials, or permissions?

Need an assessment based on your actual environment?