NTFS permissions explained: a practical guide

Key takeaways

  • Network access must pass both NTFS and SMB share permissions, so Modify on the folder cannot enable editing through a share allowing only Read.
  • Effective access combines user and group entries, so removing a direct permission does not remove group-granted access, and Deny always wins is incomplete.
  • Google Drive shared drives use their own roles, Viewer, Contributor, Content manager, and Manager, so NTFS permissions must be translated by intent rather than copied.
  • Judge a migration by access tests for readers, editors, excluded staff, group members, unmapped identities, and administrators, not by a successful transfer report.

NTFS permissions control who can read, change, delete, or administer files and folders on Windows storage. This practical guide explains how those permissions work, how to investigate access problems, and what to check when translating them into Google Drive access. The central distinction is between a permission entry and the access a person actually receives through all applicable rules. (learn.microsoft.com)

What are NTFS permissions, and what do they control?

NTFS permissions are file system permissions attached to files and folders on an NTFS volume. Windows uses access control entries, or ACEs, in a discretionary access control list, or DACL, to evaluate requested actions. Entries identify users or groups and specify allowed or denied rights; their order matters during evaluation. (learn.microsoft.com)

Windows presents common combinations of rights as familiar permission levels. Use these as a starting point, then examine advanced permissions when a task needs tighter control. (learn.microsoft.com)

Permission Typical capabilities Practical implication
Read Read file data and attributes Suitable for reference material
Read & execute Read content and execute programs Appropriate where running files is required
List folder contents List items within a folder Helps users browse folder structures
Write Write data and create applicable content Does not independently grant deletion rights
Modify Read, write, execute, and delete Includes deletion, not just editing
Full control Modify content, change permissions, and take ownership Grants administrative capabilities

These are permission bundles, not a substitute for checking the underlying rights. Windows distinguishes writing data, deleting an object, changing its DACL, and changing its owner. Consequently, “can edit” and “can administer access” are different requirements. (learn.microsoft.com)

How do inheritance, Allow, and Deny affect access?

Inheritance passes applicable permissions from a parent folder to its children, while explicit permissions are assigned directly to an item. Effective access depends on the applicable entries for the user and their groups, including the ordering of explicit and inherited rules. Avoid treating any single checkbox as the complete answer. (learn.microsoft.com)

For example, suppose an employee belongs to a readers group and an editors group. With applicable Allow entries and no conflicting restrictions, those memberships can combine to provide broader access than the readers group alone. Removing the employee’s direct permission would not remove access still granted through a group. (learn.microsoft.com)

“Deny always wins” is an incomplete troubleshooting rule. Microsoft documents a preferred ordering in which explicit entries precede inherited entries, with Deny before Allow within the explicit group and within each inheritance level. Examine the actual ACL rather than assuming every Deny defeats every Allow regardless of its origin. (learn.microsoft.com)

For a maintainable design, prefer clear group-based grants and record why exceptions exist. Before disabling inheritance, identify which inherited entries must remain and who will maintain the separate permissions afterward. Treat the change as a new access boundary, not merely a way to remove an inconvenient entry.

Share permissions add a separate checkpoint

NTFS permissions and SMB share permissions are separate controls. For access through a network share, the requested action must be permitted by both layers. An NTFS Modify grant cannot enable editing through a share that permits only Read. (download.microsoft.com)

This distinction matters when someone can work with a file locally but cannot perform the same action through its network path. Investigate the share configuration alongside the file’s Security settings instead of repeatedly expanding NTFS access. Microsoft’s configuration guidance treats share access and physical-folder access as separate tasks. (learn.microsoft.com)

During an audit, record both layers. Otherwise, you may mistake a restrictive share permission for the intended folder policy and carry the wrong assumptions into a migration plan.

Inspect permissions before changing them

Start with the exact file or folder and the exact action that fails. “Cannot access Finance” is less useful than “can open the workbook but cannot save changes through the departmental share.” Keep the investigation narrow before considering a recursive change.

Use this inspection sequence:

  1. Inspect the item. Open Properties, then Security, and examine Advanced settings for detailed entries and inheritance information. (learn.microsoft.com)
  2. Trace the access path. Record relevant user and group entries, their Allow or Deny status, and whether they are inherited. (learn.microsoft.com)
  3. Check the network layer. If the user connects through SMB, inspect the share permissions too. (download.microsoft.com)
  4. Preserve the starting point. Microsoft’s icacls utility can display DACLs and save them for later restoration; this is not a backup of file contents. (learn.microsoft.com)
  5. Test a narrow change. Confirm both the intended action and an action that should remain prohibited before extending the change.

Avoid using Full control as a diagnostic shortcut. It grants capabilities beyond ordinary editing, including permission and ownership changes, so a successful test could conceal which right was actually missing. (learn.microsoft.com)

Can NTFS permissions transfer directly to Google Drive?

Not as an identical set of Windows permission entries. Google Drive uses its own roles and sharing model, so migration requires translating identities and access intent into destination-supported permissions. Shared drives distinguish roles such as Viewer, Contributor, Content manager, and Manager rather than reproducing NTFS permission bundles. (support.google.com)

Treat the following as design questions, not automatic equivalences:

Source requirement Destination decision
Reference-only access Evaluate Viewer access
Create and edit documents Compare Contributor and Content manager capabilities
Delete or reorganize content Check the specific destination role’s capabilities
Administer membership Reserve appropriate Manager responsibilities
Restrict a child folder Evaluate limited access and its management requirements

Google’s shared-drive role table separates these capabilities; even client behavior can differ. Contributor access, for example, has limitations in Drive for desktop compared with browser-based workflows. Validate the interface employees actually use. (support.google.com)

Limited-access folders introduce another consideration: people without access may sometimes see a greyed-out folder but cannot open it. Google also documents circumstances where automatically limited folders are not visible to excluded users. Test visibility as well as content access, especially when folder names themselves are sensitive. (support.google.com)

Evaluate migration tools against your permission exceptions

Start vendor discussions with a permission inventory, not just a file count. Ask each provider to demonstrate your difficult cases: nested groups, direct grants, disabled inheritance, denied access, and unmapped accounts. Require an explanation of any destination redesign before approving it.

For DryvIQ mapping of NTFS permissions to Google Drive and Google Groups, distinguish identity mapping from permission translation. DryvIQ documents user and group mapping policies and permission-preservation settings. Ask how each source security group maps to its intended Google Group, then validate membership and resulting access in a pilot. (dryviq.atlassian.net)

If you are researching SkySync Google Drive migration and NTFS permissions mapping, note that SkySync became DryvIQ in 2022. Use documentation applicable to the deployed product rather than assuming an older configuration example remains suitable. (dryviq.com)

For CloudM Migrate file-server-to-Google-Drive NTFS permissions, CloudM’s setup guidance points administrators to ACL mapping and address replacement configuration. Its permission watchpoints also describe limited-access handling and wrapper folders for certain restricted files. Include those structural and visibility outcomes in acceptance testing. (support.cloudm.io)

For a Cloudiway file-server-to-Google-Drive migration involving NTFS permissions, first request confirmation of the supported source-to-destination route. When evaluating Cloudiway file-server-to-Google-Drive NTFS permissions mapping, request a documented mapping matrix and a representative demonstration. The reviewed sources did not establish that specific workflow, so its support should not be assumed.

Make access validation your acceptance test

Build a small pilot containing ordinary departmental folders and the hardest exceptions. Define expected outcomes before migration so the test does not merely confirm whatever the tool produces.

Include these checks:

  • Reader: Can open approved content but cannot change it.
  • Editor: Can complete required work without gaining unnecessary sharing authority.
  • Excluded employee: Cannot open restricted content through navigation or a direct link.
  • Group member: Receives the expected access through the mapped destination group.
  • Unmapped identity: Appears in an exception report for review, rather than being silently ignored.
  • Administrator: Can maintain membership and restrictions without relying on the migration account.

Record results, resolve exceptions with the content owner, and repeat the same tests after the final migration pass. Approve access outcomes—not simply a successful transfer report.

The practical takeaway

Document who needs access, what actions they require, and where exceptions belong. Keep that intent separate from the mechanism implementing it. Whether maintaining Windows folders or moving to Google Drive, make a representative access test the final checkpoint before declaring the work complete.

Sources

  1. Share and NTFS Permissions | Microsoft Learn
  2. Order of ACEs in a DACL - Win32 apps | Microsoft Learn
  3. File and Directory Access Rights Constants (Winnt.h) - Win32 apps | Microsoft Learn
  4. Permissions when you copy and move files - Windows Client | Microsoft Learn
  5. download.microsoft.com: Samplechapters
  6. icacls | Microsoft Learn
  7. How file access works in shared drives - Google Workspace Learning Center
  8. Learn about limited access to files and folders in Google Drive - Computer - Google Drive Help
  9. dryviq.atlassian.net
  10. dryviq.com: Dryviq launches platform to safeguard enterprise content
  11. support.cloudm.io: Migrating File System Users To Google Workspace Users