Google is cleaning up how sharing works in Drive by standardizing everything around a single, clearer control called Limited access, and quietly converting old “restricted” items to this new model without changing who can actually see your files. For most people, this will feel less like a new feature and more like Google finally fixing years of confusing permission edge cases.

Until now, Drive has effectively supported two different ways to lock things down: you could restrict individual files or folders inside a more open shared folder, or you could fence off an entire folder with the newer Limited access setting. In enterprise environments, that “grant broadly, restrict selectively” pattern led to a messy web of broken inheritance—where subfolders and files silently behaved differently from everything around them, making it hard for admins and end users to reason about who had access to what. Google started phasing this out in 2025 by preventing new restricted child items inside shared folders and pushing admins toward Limited access for consistent folder‑level control.

The change rolling out now is the second half of that story: all legacy restricted items are being automatically migrated to Limited access, so Drive uses a single permissions model going forward. Google is explicit that this migration does not alter effective access—if someone could open a file yesterday, they can still open it tomorrow; what changes is the underlying plumbing and how that access is represented in Drive. For migrated content, Drive will label Limited access as having been applied by Google Drive itself, so admins who audit permissions can tell which items came from this system-wide cleanup versus manual configuration.

Practically, Limited access is Google’s answer to “private islands” inside otherwise shared spaces: a folder with Limited access can only be opened by people explicitly added to that folder, even if others have broad access to the parent shared drive or My Drive folder. Everyone with access to the parent can still see that the folder exists—typically as a greyed-out entry—but they can’t open it or see its contents unless they’re on the folder’s access list, which keeps sensitive material discoverable enough for context without leaking the data itself. Folder owners in My Drive and managers in shared drives control whether Limited access is on, and they manage who is allowed in; depending on admin settings, certain editors or content managers may also be allowed to maintain those access lists.

This shift is also closely tied to how migrations and third‑party tools work with Drive going forward. Services that move content from platforms like SharePoint—where “broken inheritance” is common—now map those restrictive patterns into Drive by creating Limited access folders that preserve both the folder hierarchy and the original permission intent, sometimes even wrapping single sensitive files in their own Limited access folder when file‑level restrictions are needed. The key point is that Google no longer wants files to be more locked down than their parent folder through ad‑hoc overrides; if you need tighter control, you put the content into a Limited access folder and treat that folder as the security boundary.

For everyday users, the main visible change is how these items show up and how easy they are to track. If you want to see which of your files fall under the new model, Google has wired Limited access into Drive search, so you can run a query like owner:me is:limitedaccess to get a list of items you own that use this setting. When you open the sharing dialog on these items, you’ll also see the updated sharing experience that clearly calls out that Limited access is applied, which should reduce the “why can’t my colleague see this?” confusion that used to come from subtle per‑file tweaks.

Admins and IT teams get a simpler life as well. There’s no special admin toggle to manage this migration—it’s happening automatically across Workspace domains, Workspace Individual, and personal Google accounts, with rollouts beginning in April 2026 for Rapid Release and a week later for Scheduled Release. Because the model is standardized around Limited access, governance rules, audits, and support workflows can focus on one predictable behavior instead of chasing down weird one‑off restrictions deep in folder trees. University IT departments and large organizations that had previously warned users about upcoming restricted‑sharing changes are already treating Limited access as the default way to protect sensitive Drive content going forward.

Stepping back, this is part of a broader trend in cloud storage: reduce “clever” but opaque permission tricks in favor of fewer, clearer concepts that are harder to misconfigure. For Google Drive, that means: open content broadly when collaboration matters, and when something needs to be locked down, move it into a Limited access folder instead of carving exceptions on individual files scattered throughout a structure. The migration of old restricted items into this new standard is less about adding a headline feature and more about aligning Drive with that philosophy everywhere, so teams can share boldly while still knowing exactly where their boundaries are.