macOS 27.3 makes Full Disk Access granular: a folder, not your whole disk
On November 16 Apple shipped macOS 27.3 beta 2 and with it the first real overhaul of Full Disk Access since Mojave: the permission stops being an all-or-nothing switch and starts having a scope.
What Changes in macOS 27.3
The developer note is titled "Updates to Device Control and Data Access, and Full Disk Access in macOS" and ships with beta 2, build 26C5047e. This is not a release date: Apple has not said when it reaches the public, so what exists today is a developer beta.
One Setting Becomes Two
The old "Device Control and Data Access" splits into System & App Protection Override, which is what lets an app control other apps, and Accessibility, which covers access for assistive technologies. These are new names on a permission that already existed.
A Single Way to Grant, and More Information
Granting is unified into one flow: the user picks the requesting app from a list. And before accepting, the user gets a clearer view of the range of data the app would reach if everything is granted. The note's own line sets the tone: before granting an app such extraordinary access, users should understand that it puts all of the data on their Mac at risk.
Read also
Full Disk Access Is Not Gone, It Is Scoped
This is the easiest misunderstanding to make. The permission still exists for whoever needs it; what changes is the approval process and the ability to narrow the scope. Apple is not removing it, it is adding granularity.
Permission Per Folder Instead of the Whole Disk
The new guidance pushes toward granting access only to the specific apps, in the Override case, or only to the specific folders, in the Full Disk Access case, that the workflow needs. A photo manager that sorts one folder no longer needs the whole disk.
The Ask-Every-Time Switch
An app can be configured to ask for permission every time it needs access instead of staying permanently authorized. That is the difference between a master key and a key handed out per use.
The Menu Bar Indicator
When an app controls another app using System & App Protection Override, a transparency indicator appears in the menu bar. It is the least technical change and the one people will notice most: until today, app-to-app control could happen with no visible signal.
What Apps Have to Do
Apple says it plainly: developers should adjust how they onboard users and make sure their apps gracefully handle having access to only a limited set of folders or apps.
New Onboarding, and Handling the "No"
In practice, the first-run flow gets redone. Asking for everything up front will be harder to justify, and the code has to work when the user grants half. An app that locks up because it is missing a folder it never actually used is badly designed, and now that shows.
Backup and Assistive Apps: The Entitlement Path
Apps that used Full Disk Access for disk backups, or the Accessibility settings for assistive technologies, can request entitlements to offer the same experience as before 27.3 on fresh installs. Apple will publish details soon; until then there are no entitlement names to cite.
What Stays the Same
Permissions already granted stay in force, with no re-approval after updating. Known apps are unaffected and need no entitlement. And the underlying APIs, according to the 9to5Mac report carried by other outlets, do not change either: the redesign is about the approval flow. That last part is press reporting, not Apple's own words in the note.
Why Apple Moves Now
On October 2 Apple had already announced additional controls for Full Disk Access because of the risk posed by AI agents; beta 2 implements that announcement. The permission has existed since macOS Mojave (10.14) and until macOS 27.2.1 it never offered granular control. What drives the change is the rise of local agents and automation tools that ask for the whole disk to be useful. Coverage cites two earlier episodes, always attributed: a journalist's claim that Meta's Muse app read his private messages without consent, and a Wired report about a flaw in the ChatGPT Mac app.
What This Means If You Build for the Web
It is the same jump the web made from "give me your username and password" to OAuth scopes: from trusting the provider to declaring a specific scope and nothing more. For your own app's consent design the lesson is direct: ask when the permission is used, explain what is read and why, and accept the "no" without breaking the experience. The other half of the problem, the websites that receive AI agents, is covered in how to block or allow agents on your site, and the recent case of Apple's grey list on the iPhone keyboard follows the same thread.
Conclusion
Fewer blanket permissions and more explicit contracts. For the user, an indicator in the menu bar and the option to approve per use. For the developer, pending work on onboarding and code that handles partial access from day one. We follow every beta that touches system permissions, because those are the ones that end up defining how the apps we write get installed.

