Google is changing how permissions function within Google Drive. The Limited Access feature launched in February 2025, with full enforcement for all pre-existing files and folders scheduled for 2026.
Permissions now cascade from parent folders to all children. The ability to selectively remove inherited permissions on individual items is being removed. This applies to both User and Shared Drives.
Google Drive Permission Changes
Google is enforcing expansive access in Google Drive, introducing the following technical constraints:
- Access granted to a parent folder automatically applies to all child folders and files.
- The ability to selectively restrict or remove inherited permissions on individual items is being removed.
- The "Update item only" and "Remove from item" options are no longer available.
Limited Access Folders
For scenarios requiring access restrictions on a subfolder, Google provides Limited Access folders. These folders:
- Break permission inheritance from the parent folder.
- Appear greyed out to users who do not have direct access.
- Block access to contents while preserving folder hierarchy visibility.
How This Affects CloudM Archive
Archives created before these changes may lack the metadata flags required to handle inheritance restrictions. Restoring items with restricted permissions from older archives can fail if these flags are missing.
CloudM Archive includes automatic detection and correction during the restore process. When the system identifies older data, it:
- Compares each item's permissions against its parent folder.
- Identifies users removed at the child level or users with downgraded roles.
- Applies the necessary flags automatically so that Google Drive accepts the restore.
This logic is skipped for data that already contains the correct flags, restores with permissions disabled, and items with no permission entries.
Post-Restore Behavior
Most restores complete without structural changes. However, two scenarios may occur based on Google's requirements.
Scenario 1: Files Wrapped in a Folder
| ⚠️ Advisory: Individual files with restricted permissions will be restored inside a new parent folder. |
Google Drive does not allow individual files to block inherited permissions; only folders can perform this action. To preserve original restrictions, CloudM Archive wraps the file inside a folder that enforces the access rules.
| Before Restore | After Restore |
|---|---|
| Budget.xlsx (restricted file) | Budget_restricted.xlsx/ (folder) └─ Budget.xlsx (file inside) |
Scenario 2: Visibility of Previously Hidden Folders
| ℹ️ Advisory: Some users may now see folder names that were previously invisible to them. |
Due to the Limited Access behavior, users with access to a parent folder will see the names of child folders that were previously invisible. The folders appear greyed out.
- Users cannot open the folder.
- Users cannot view files inside the folder.
- Only the folder name (metadata) is visible.
Restore Behavior Summary
| Scenario | Result |
|---|---|
| Older archive with restricted permissions | Success (Automatically transformed) |
| Newer data (flags present) | Success (Analysis skipped) |
| Restore with permissions disabled | Success (Analysis skipped) |
Need Help?
If you experience unexpected behavior during a restore, contact CloudM Support. Provide the archive creation date to assist the investigation.