If an App Asks for Full Disk Access or System and App Protection Override
jshier
66 points
42 comments
November 17, 2026
Related Discussions
Found 5 related stories in 190.4ms across 13,334 title embeddings via pgvector HNSW
- Updates to Full Disk Access in macOS notfirstpost · 170 pts · October 02, 2026 · 65% similar
- Apple is tightening macOS 'Full Disk Access' due to new risks from AI agents speckx · 18 pts · October 02, 2026 · 63% similar
- Secure Exclaves and Ambient Sensing interpol_p · 16 pts · November 12, 2026 · 49% similar
- Turn off and restrict access to Apple Intelligence features on Mac alwillis · 273 pts · September 21, 2026 · 48% similar
- Apple won't let me show my app codersfocus · 37 pts · July 24, 2026 · 47% similar
Discussion Highlights (10 comments)
jshier
... on your Mac. New Apple support document about the upcoming full disk access changes.
saagarjha
> Apps that might ask for Full Disk Access or System & App Protection Override include backup apps, disk cleaners, file indexers, security apps, and others. This is not what Full Disk Access was designed for. Not a huge fan of Apple misrepresenting what permissions do so they can pretend like their policies are consistent and not a kneejerk reaction to what’s going on in the world.
vsgherzi
This seems like a fine change? I don’t quite understand what the pushback is could someone spell it out for me?
postalcoder
This is a good thing. There are too many apps that request full disk access despite not needing it. I counted 44* applications on my mac that ask for FDA. I've only granted it to 8. The other apps work just fine without it. (Some apps that ask for full disk access: Anki, a flashcard app and Soulver, a calculator app – cmon now) This change is less about bureaucracy and more requiring developers to be more clear why it needs the permissions it does. *edit: originally said 56
vbezhenar
For me more important would be to exclude specific folders from that full disk access (like ~/.ssh), rather than selecting one directory. For example I've used Daisy Disk app to visualize directory size. It's best used with full disk access. But I know that my `.ssh` is tiny and I'd prefer for this app not to be able to access it at all.
dofm
Freaking finally! This looks really well-implemented, considering the complexity of explaining all of this to users.
dmitrygr
This is great! I loved when iOS let me expose only a subset of my contacts list to whatsapp (and, this is important: banned facebook from retaliating) -- the subset it already knows, and this is another good step in the right direction. I trust precisely 0% of apps with my private data, and apple making it easier to limit exposure is good!
kylehotchkiss
I'm clearing out my "full disk access" list when this lands and re-granting them all!
Elseself
Why isn't this a filesystem-level permission yet? Like being able to set file and folder access for specific apps like we do for user accounts. For example I could set my "Top Secret Ideas" folder to "Deny" for "All Apps" but "Read & Write" for Finder and my Markdown editor. The tricky part would be how to assign IDs or "accounts" for apps and what to do when an app gets updated..
gbdubs
This is a very poorly conceived API. If developers' use cases don't fit cleanly into Apple's (narrow) idea about how a hypothetical app should work, developers will continue to feel like they need to request these expansive permissions. A good filesystem permission API could include any of these which would make users WAY safer and enable developers to request far smaller scopes: - Allow the developer to specify the common location(s) that they need access to. Rather than having to have the user select the folder they want to grant access to, have the developer say "this app uses data in these 5 folders, do you want to grant that access" - so much clearer, and useful in cases where an app has to integrate with other apps through the filesystem. - Readonly access. Allow an app to read your files but prevent writes or deletes. - Time limited access. Allow some kind of access and allow the user to auto-expire it rather than having to remember it exists. - Allow for negative access (i.e. allow labels or tags on directories to mark them as sensitive and prevent access by default - browsers could do this for their cookie stores, `~/.ssh` could ship with it as a default, etc.) Apple could have used this opportunity to think through the question of "why do developers ask for filesystem access, and how can we allow legitimate usage through well scoped access controls", but instead they built a bad API that will (I would guess) not actually allow developers to be more judicious or achieve any of the user-safety benefits. Apple needs to learn to talk to (and listen to) developers.